Living Documentation

When Triggered

• Modifying code that implements behavior defined in

  requirements.md

• Changing architecture/interfaces described in

  design.md

• Discovering edge cases or patterns not yet documented

Lifecycle

Sync Protocol

1. Identify Affected Specs
   • Check task's

     _writes:

     manifest
   • Map to spec sections: which requirements/design does this touch?
2. Update Spec Content
   • Remove obsolete descriptions
   • Document actual implementation approach
   • Add discovered edge cases as new ACs
   • Keep spec readable without code
3. Add Traceability
   markdown

   <!-- impl: path/to/file.ts#FunctionName -->

4. Commit Together
   • Spec changes in same commit as code changes

What to Update

design.md#Components

requirements.md

design.md

Quality Check

• Spec describes current reality, not original plan
• No stale sections left
• New reader understands system from spec alone
• Traceability links added