What problem does it solve? When multiple skills generate requirement-related documents (design docs, data flow diagrams, review reports, verification reports), they often end up scattered in inconsistent locations. This Skill enforces a unified storage convention so every document lands in the correct subdirectory of the requirement management system and stays traceable via meta.json. ## Core Features & Use Cases - Type-based path routing: Automatically maps document types (requirement, design, data_flow, review, demo, test, report) to their canonical storage paths under the requirement directory. - Lifecycle management via req CLI: Creates, updates, and deletes requirement entries with req create, req update, and req delete, managing status, tags, dependencies, commits, and document associations without manual meta.json edits. - Mandatory persistence verification: After every create or update, runs req list --id to confirm the entry exists and fields match, with retry-on-failure rules. - Use Case: After a design skill produces DESIGN.md, invoke this Skill to register it under design/DESIGN.md, update the requirement status to 设计中, and verify the association was recorded. ## Quick Start Store the generated design document for the user authentication requirement into the requirement management system and verify it was registered.
