spec-workflow

Coordinate spec-driven development phases and generate research, requirements, design, and tasks artifacts.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/ForeverWorld/curdx-ralph --skill spec-workflow-foreverworld
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/ForeverWorld/curdx-ralph/tree/main/skills/spec-workflow
Command: npx skills add https://github.com/ForeverWorld/curdx-ralph --skill spec-workflow-foreverworld

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill organizes and automates the spec-driven development lifecycle to eliminate ad-hoc planning, reduce rework, and provide auditable progress from research through implementation.

Core Features & Use Cases

  • Phase orchestration: Run and transition through research, requirements, design, tasks, and implementation phases with state tracking.
  • Artifact generation & approvals: Produce structured artifacts (research.md, requirements.md, design.md, tasks.md) with awaitingApproval checkpoints and quick-mode automation.
  • Execution & traceability: Plan, execute, verify, and commit implementation tasks while maintaining progress logs and quality gates; ideal for engineering teams adopting a repeatable, reviewable workflow.

Quick Start

Start a new feature spec and run full quick-mode automation by running /curdx:start user-auth Add JWT authentication --quick

Frequently Asked Questions about spec-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is spec-driven development and how does it improve software feature planning?

Yes, you can automate the entire spec-driven workflow using quick-mode automation. Running a start command with the quick flag transitions through research, requirements, design, tasks, and implementation phases automatically, bypassing manual awaitingApproval checkpoints.

How do I track implementation progress and maintain traceability across development phases?

Spec-driven workflows produce structured artifacts including research.md, requirements.md, design.md, and tasks.md. These documents capture phase outputs sequentially, providing reviewable checkpoints for engineering teams to approve before moving forward.

Can I automate the spec-driven workflow end-to-end without manual approvals?

Yes, you can automate the entire spec-driven workflow using quick-mode automation. Running a start command with the quick flag transitions through research, requirements, design, tasks, and implementation phases automatically, bypassing manual awaitingApproval checkpoints.

How do I track implementation progress and maintain traceability across development phases?

You can track implementation progress through execution state tracking and quality gates. The workflow plans, executes, verifies, and commits implementation tasks while maintaining progress logs and generating phase artifacts for full auditability.

What artifacts are generated during the spec-driven development lifecycle?

Spec-driven workflows produce structured artifacts including research.md, requirements.md, design.md, and tasks.md. These documents capture phase outputs sequentially, providing reviewable checkpoints for engineering teams to approve before moving forward.

Does spec-driven development support manual approval checkpoints for team reviews?

Yes, spec-driven development supports awaitingApproval checkpoints between phases. Teams can review generated artifacts like design.md and tasks.md, ensuring quality gates are met before transitioning to implementation or subsequent phases.