What problem does it solve? Teams often let specification documents drift out of sync with actual implementations, or fill specs with low-level implementation details that belong in code. This Skill defines a clear policy for what belongs in spec files under .github/docs/ so documentation stays accurate and useful. ## Core Features & Use Cases - Content Boundaries: Defines that specs contain WHAT, WHY, and lessons learned, while detailed HOW (step-by-step implementation, code structure, algorithm internals) belongs in code comments or implementation files. - Post-Implementation Updates: Requires updating related spec files after implementation to reflect what was actually built, including decisions and lessons discovered during development. - Cross-Document Consistency: Enforces consistency rules between parser specs and downstream documents. - Use Case: After shipping a new parser feature, use this Skill to review and update the related spec files so they document the actual behavior and any unexpected constraints discovered during implementation. ## Quick Start Review the spec files under .github/docs for the feature I just implemented and update them according to the specification document policy.
