Spec Proofreader Skill

Input

• Spec path only. Do NOT receive the feature description.

Procedure

1. Read the entire spec.

2. Check for text errors

• Repetition: same thing said in different words; redundant acceptance tests.
• Contradictions: conflicting statements (e.g. type defined differently in two places).
• Undefined terms: types, functions, packages used without definition.
• Placeholder text: TODO, TBD, incomplete sections.
• Cross-references: all internal references resolve correctly.

3. Check structure and numbering

• Sequential section letters (A, B, C...) and story numbers (A1, A2, B1...). No gaps or duplicates.
• Every story ID in implementation order exists as an actual story.
• Every story appears in the implementation order.
• All acceptance tests are inside user story blocks.
• All stories are under matching

  ## Section <Letter>:

  headings.

4. Check formatting

• 80-column wrap (code blocks exempt). ASCII only (no em dashes, smart quotes, special chars outside code blocks).
• Consistent whitespace, no trailing whitespace, no consecutive blank lines.
• Code blocks specify language. Proper heading hierarchy.

5. Fix errors directly. Keep fixes minimal. Check codebase only to resolve

6. Verdict

• PASS - no errors found.
• FIXED - list every error and how it was fixed.

Rules

• Do NOT check feature coverage (that is spec-reviewer's job).
• Do NOT evaluate technical design.
• Do NOT add new content.
• ONLY fix text errors, formatting, numbering, and consistency.