What problem does it solve? Turning a vague product or technical request into a precise, evidence-grounded requirements package is slow and error-prone. This Skill investigates the actual product and codebase, documents current versus desired behavior, captures explicit user approval, and decides whether the work can go straight to implementation or needs architecture design first. ## Core Features & Use Cases - Evidence-grounded investigation: Builds canonical requirements-doc.md and investigation-notes.md artifacts from real code, runtime, contract, and stakeholder evidence, with stable REQ, AC, BEH, and SCN identifiers. - Approval and revision governance: Enforces a readiness gate, explicit user approval, and a chronological requirements revision record (RER-*) across refinement rounds. - Architecture routing assessment: Classifies approved packages as direct-implementation-ready, architecture-ready, unclear, or blocked, and routes them through dynamic handoff rules, including Product Design & Prototyping coordination when requested. - Use Case: A stakeholder asks to change how an API handles expired sessions. The Skill investigates the current behavior in the codebase, writes testable requirements and acceptance criteria, gets user approval, detects a contract-level structural impact, and routes the package to the Architecture Designer with full evidence. ## Quick Start Ask the agent to investigate the current behavior of a feature in your repository and produce an approved requirements package with acceptance criteria and a routing recommendation.
