This skill guides the user through a structured specification process: a mandatory six-question Step 0 gate, a clarifying requirements interview, complexity tiering, CVA analysis (when relevant), and generation of durable PRD artifacts (REQ/DESIGN/TASK). It produces verifiable, EARS-style acceptance criteria ready for engineering work.
Use when you need to transform a problem, ticket, or idea into a formal, testable requirements document before implementation — e.g., preparing a PRD, splitting work for engineers, or validating scope with stakeholders. It is blocking for cases that require clear demand/signal evidence (Step 0).
This is a monolithic 63K-char SKILL.md that transforms problem statements into testable requirements with acceptance criteria. It implements a rigorous multi-step process (Steps 0–9+) with gate logic, hedge-phrase detection, tier classification, and references to multiple sub-skills (threat-modeling, slo-designer, adr-generator, etc.). No scripts to run. The instructions are exceptionally detailed and precise, but the entire skill is one massive file with no separation into scripts/ or references/. It references external sub-skills and files like @CLAUDE.md that won't exist outside its original repo, making it non-portable.
Security is clean — pure instruction document, no code execution. The skill is well-thought-out and comprehensive for its original context (rjmurillo/ai-agents repo with Claude/Copilot), but severely lacks architectural separation. A 63K SKILL.md defeats the purpose of progressive disclosure. The skill is deeply coupled to its home repo's sub-skill ecosystem and won't work standalone. Usefulness is limited to teams using that specific multi-skill setup.