What problem does it solve? SRS work spans four distinct phases — deriving requirements from a technical protocol, writing the document, reviewing quality, and performing large-scale revisions — and choosing the wrong workflow or mixing conventions across phases produces inconsistent, untraceable requirements documents. ## Core Features & Use Cases - Phase Routing: Diagnoses the current SRS stage from user intent and routes to the correct sub-skill (ada-tp-to-srs-derivation, ada-srs-writing, ada-srs-review, ada-srs-revision, ada-requirements-authoring). - Shared Conventions: Enforces a uniform REQ-F requirement format (heading, priority emoji, actor, Given/When/Then acceptance criteria), a five-section document structure, and core principles like terminology consistency and TP traceability. - Use Case: Given a technical protocol document, load this skill to route to the derivation phase, produce a traceable SRS draft, then route to review and revision phases as the document matures. ## Quick Start Ask the agent to load the SRS lifecycle skill and describe your current task, such as deriving an SRS from a technical protocol or reviewing an existing SRS for quality issues.
