What problem does it solve? Raw ideas and informal requests lack the structure needed for reliable planning and implementation. This Skill turns an unformalized task, problem, or investigation context into a formal, operator-approved requirements document that fixes what must be true when the work is done, without prescribing how to build it. ## Core Features & Use Cases - Structured intake and reconnaissance: Classifies the request type, harvests existing investigation context, and grounds every claim in code, docs, or config with file:line evidence. - Operator-driven fork resolution: Resolves scope, behavior, priority, and compatibility decisions through structured question rounds, recording each outcome in a decision log. - Validated document contract: Produces a self-contained Markdown document with functional requirements, non-functional requirements, acceptance criteria, risks, and defaults, saved under .agents/requirements/. - Use Case: After debugging a CLI defect, invoke the Skill with no arguments to harvest the investigation context, clarify scope with the operator, and produce an approved requirements document ready for solution handoff. ## Quick Start Ask the agent to formalize your raw task or harvested investigation context into an approved requirements document using the requirements skill.
