Capture and structure product work into a complete, testable specification.
npx skills add https://github.com/doodledood/codex-workflow --skill spec-doodledood
Please help me install this Agent Skill. Skill: spec Source: https://github.com/doodledood/codex-workflow/tree/main/skills/spec Command: npx skills add https://github.com/doodledood/codex-workflow --skill spec-doodledood
Build requirements specification through structured discovery interview. Use when defining scope, gathering requirements, or specifying WHAT work should accomplish - features, bugs, refactors, infrastructure, migrations, performance, documentation, or any other work type. Triggers: spec, requirements, define scope, what to build.
Start the discovery interview by providing the work name and initial user request to begin structured discovery.
High-intent search queries and answers about installing and using this skill.
To define project scope, you need structured discovery interviews that capture product work into a complete, testable specification with well-defined requirements and traceable decisions. This process uses iterative interview rounds to expand todos and finalize the spec.
A structured discovery interview for requirements specification is a phase-based workflow that gathers context, iteratively refines requirements through interactive todos, and logs decisions to external memory. It ensures each requirement is testable and verifiable before finalization.
You create testable requirements with traceable decisions by enforcing a formal specification workflow with phase-based setup, context gathering, iterative interviews, and finalization steps. Interview logs track decisions and iterations to ensure verifiable requirements.
Yes, you can use this requirements specification workflow for infrastructure, migrations, refactors, features, bugs, performance, and documentation work. It applies to any project requiring clear scope, well-defined requirements, and traceable decisions.
To start a discovery interview, provide the work name and initial user request. This begins the structured discovery process, generating temporary spec and interview files to persist progress through the iterative phases.
Yes, the specification workflow persists progress by generating spec and interview files in the temporary directory. These files act as external memory to track decisions, iterations, and todos throughout the phase-based workflow.
SQDR2Generate a new OpenSpec change scaffold with a derived kebab-case name and validate its uniqueness.
JmarquesGenerate project specifications from codebase analysis and conversation context.
carlosamesarConvert project proposals and design documents into detailed development tasks.
JotJuniorConduct structured discovery interviews to capture project context into briefing documents.
