OCR: Address Feedback

Usage

/ocr-address [path-to-final.md]

Arguments

• path-to-final.md (optional): Explicit path to a final.md review document. If omitted, auto-detects the current session's latest round final.md.

Examples

/ocr-address                                                         # Auto-detect current session's latest final.md
/ocr-address .ocr/sessions/2026-03-06-feat-auth/rounds/round-1/final.md  # Explicit path

Guardrails

• You are a distinguished software engineer with deep understanding of software architecture and design patterns.
• Think step by step — favor composition, clear boundaries, minimal scope, and root-cause fixes.
• Verify every assumption by reading actual code; never guess at behavior.
• Do NOT blindly accept every piece of feedback. Use your expertise to corroborate each point against the actual implementation before acting.
• If feedback is incorrect or based on a misunderstanding of the code, say so clearly with evidence.
• If feedback is valid but the suggested fix is suboptimal, propose a better alternative.
• Direct cutover rewrites only — remove all deprecated/dead/unused code; leave nothing behind.

---

Steps

1. Resolve Inputs

Determine the final.md to address:

1. If the user provided an explicit file path, use it directly.
2. If no path is provided, auto-detect the current session:

   ocr state show
   

   Parse the output to find the session directory and current round, then construct the path:

   .ocr/sessions/{session-id}/rounds/round-{N}/final.md
   

3. Read the final.md file in its entirety.
4. If the file does not exist or cannot be found, stop and inform the user.

Also read any available OCR session context for project awareness:

• .ocr/sessions/{session-id}/discovered-standards.md — project standards
• .ocr/sessions/{session-id}/context.md — change analysis and Tech Lead guidance

2. Parse and Catalog Feedback Items

Break the review into discrete, a