What problem does it solve? Teams often lack clear, non-technical records of why each existing capability exists, what problem it solves, and where its boundaries lie. This Skill maintains a codestable/requirements/ directory of user-story-based requirement documents that describe current capabilities in plain language, keeping them synchronized with the actual implementation. ## Core Features & Use Cases - Backfill mode: Creates a requirement document for a capability that already exists in code but was never documented, using user stories, pain points, solution overview, and boundaries. - Update mode: Refreshes an existing requirement document when the capability's user story, pitch, or boundaries have evolved, with a changelog entry for structural changes. - Quality self-check: Enforces a review checklist that rejects PRD-style field dumps, implementation details, vague user stories, and missing boundaries before user review. - Use Case: After a feature acceptance phase adds a new user-facing capability, trigger backfill to produce a one-page requirement doc with a pitch usable as marketing copy, linked to the architecture doc via implemented_by. ## Quick Start Ask the assistant to backfill a requirement document for the data monitoring capability that was just accepted, describing why it exists and its boundaries in plain language.
