What problem does it solve? Keeping requirement documents consistent is hard: REQ numbers must never collide or reuse gaps, requirement line IDs must follow a strict format, and teams need clear rules for deciding whether a change means creating a new requirement file, appending a line, or updating an existing section. This Skill codifies those rules and provides deterministic scripts so numbering and file operations stay correct. ## Core Features & Use Cases - Deterministic ID allocation: TypeScript scripts allocate the next REQ number (max+1, no gap filling) and requirement line IDs (REQ-NNNN-MMM) as pure functions with JSON output. - CREATE/APPEND/UPDATE operation modes: Clear decision flow and five-axis evaluation criteria for matching user intent against existing REQ files before writing. - Validation and consistency rules: Frontmatter conventions (id, title, created, updated), filename-to-ID matching, date validation, classification gates, and merge-conflict resolution patterns. - Use Case: While defining requirements in a wall-bashing session, the agent matches the intent against existing REQ files, decides APPEND is appropriate, allocates the next requirement line ID via script, and updates the file and index consistently. ## Quick Start Ask the agent to create or update a requirement file for your feature, and it will match existing REQs, allocate the correct REQ number, and save the file under docs/requirements.
