Skip to content

[plan] Fix inconsistencies in partial-review-prompt.md between rules and template #620

@Tonny-Gu

Description

@Tonny-Gu

Now I understand. The user selected Option 1B in the previous resolve (replacing the quote-based citation format with an Agent Perspectives table reference), but now they're refining that decision: instead of adding a new table definition in Rule 1, just reference the existing Agent Perspectives table that's already defined in the output format template.

Let me produce the updated unified plan:


Implementation Plan: Fix Inconsistencies in partial-review-prompt.md

Table of Contents


Goal

Fix terminology inconsistencies in partial-review-prompt.md where the rules section and template section use different naming conventions, and replace Rule 1's quote-based citation format with a simple reference to the Agent Perspectives table (already defined in the output format template).

Out of scope:

  • Adding conditional HTML comments or mode-specific markers
  • Creating new test files
  • Adding mode-specific guidance tables
  • Restructuring the entire file architecture

Codebase Analysis

File changes:

File Level Purpose
.claude-plugin/skills/partial-consensus/partial-review-prompt.md minor Fix terminology: "Consensus Assessment" → "Consensus Status" at line 56; fix wording at line 154; simplify Rule 1 to reference existing table format (lines 88-99)
.claude-plugin/skills/partial-consensus/SKILL.md minor Fix terminology: "Consensus Assessment" → "Consensus Status" at line 66
tests/lint/test-partial-review-prompt.sh minor Update anchor test: #consensus-assessment#consensus-status at line 24

Implementation Steps

Step 1: Update test file anchor expectation

  • File: tests/lint/test-partial-review-prompt.sh
  • Changes: Change #consensus-assessment to #consensus-status at line 24
Code Draft
 # Test 2: TOC contains core anchors
 REQUIRED_ANCHORS=(
     "#agent-perspectives-summary"
-    "#consensus-assessment"
+    "#consensus-status"
     "#goal"
     "#implementation-steps"
 )

Step 2: Fix terminology in rules section

  • File: .claude-plugin/skills/partial-consensus/partial-review-prompt.md
  • Changes: Change "Consensus Assessment" to "Consensus Status" at line 56
Code Draft
   - Include code drafts from the selected options
   - **Skip Disagreement Summary section** (already resolved)
-  - **Skip Consensus Assessment section** (consensus already determined in previous iteration)
+  - **Skip Consensus Status section** (consensus already determined in previous iteration)
   - Include Validation section at the end (see output format below)

Step 3: Fix wording at line 154

  • File: .claude-plugin/skills/partial-consensus/partial-review-prompt.md
  • Changes: Change "consensus or partial consensus" to "consensus or disagreement" to align with the Consensus Definition section
Code Draft
 ### Unified Output Format

-Use this format for ALL outputs (consensus or partial consensus):
+Use this format for ALL outputs (consensus or disagreement):

Step 4: Simplify Rule 1 to reference existing Agent Perspectives table

  • File: .claude-plugin/skills/partial-consensus/partial-review-prompt.md
  • Changes: Replace the quote-based code block (lines 88-99) with a simple reference to the Agent Perspectives table already defined in the Disagreement template section of the output format
Code Draft
 ### Rule 1: Cite Both Sides

-When proposals disagree, document both positions before deciding:
-
-```
-### Disagreement: [Topic]
-
-**Bold claims**: [Quote from bold proposal]
-**Paranoia claims**: [Quote from paranoia proposal]
-**Critique says**: [What critique agent found]
-**Resolution**: [Which side is adopted and why, with evidence]
-```
+When proposals disagree, document both positions in the **Agent Perspectives** table
+under each Disagreement section (see output format template below for table structure).

Step 5: Fix SKILL.md terminology

  • File: .claude-plugin/skills/partial-consensus/SKILL.md
  • Changes: Change "Consensus Assessment" to "Consensus Status" at line 66
Code Draft
 | Section | Description |
 |---------|-------------|
 | Agent Perspectives Summary | 5-agent position table |
-| Consensus Assessment | 3-condition evaluation with PASS/FAIL verdict |
+| Consensus Status | 3-condition evaluation with CONSENSUS/DISAGREEMENT verdict |
 | Goal / Codebase Analysis | Problem statement and file changes |

Step 6: Run lint test to verify changes

  • File: tests/lint/test-partial-review-prompt.sh
  • Changes: Execute test to confirm all anchors pass
Code Draft
bash tests/lint/test-partial-review-prompt.sh

Success Criteria

  • Test tests/lint/test-partial-review-prompt.sh passes
  • All instances of "Consensus Assessment" replaced with "Consensus Status"
  • Line 154 uses "consensus or disagreement" instead of "consensus or partial consensus"
  • Rule 1 simplified to reference existing Agent Perspectives table (no duplicate table definition)

Risks and Mitigations

Risk Likelihood Impact Mitigation
Test fails after changes L M Run test immediately after changes
Missed occurrences of "Consensus Assessment" L L Grep for "Assessment" to verify no other occurrences
Loss of "Resolution" field guidance from Rule 1 M L Resolution is implicit in option selection; AI Recommendation field in each Disagreement section serves this purpose

Selection History

Timestamp Disagreement Options Summary Selected Option User Comments
2026-01-25 22:42 1: Rule 1 Citation Format 1A (Reducers): Keep as-is; 1B (Bold+Paranoia): Replace with table reference 1B

Refine History

Timestamp Summary
2026-01-25 22:45 Step 4: Remove duplicate table definition, just reference existing Agent Perspectives table in output format

Option Compatibility Check

Status: VALIDATED

All selected options are architecturally compatible. The refinement to Step 4 (removing the duplicate table definition and using a simple reference instead) is consistent with the original Option 1B intent while reducing redundancy.

Applied Selections:

  • Option 1B applied: Rule 1's quote-based citation format replaced with reference to Agent Perspectives table

Applied Refinements:

  • Step 4 simplified: Instead of defining a new table in Rule 1, reference the existing Agent Perspectives table already defined in the output format template

Plan Completeness:

  • All selected options merged into Implementation Steps
  • Code drafts from selected options included
  • Refinement applied to Step 4
  • No orphaned disagreement references remain

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions