spec-workflow

Spec Workflow

Spec-driven development transforms feature requests into structured specs through sequential phases, then executes them task-by-task.

Skills-First Architecture

This skill is the canonical workflow guidance. curdx-flow is now skills-only at the plugin surface: every /curdx-flow:* entry point is a namespaced skill under skills/<name>/SKILL.md.

• Keep public invocation names stable (/curdx-flow:start, /curdx-flow:tasks, /curdx-flow:implement, etc.).
• Keep direct workflow entry points user-invocable and explicit; shared/background rules live in support skills such as curdx-core and interview-framework.
• Put long procedures in skill-local references/ or plugin-global ${CLAUDE_PLUGIN_ROOT}/references/ files instead of bloating frontmatter descriptions.
• See references/entrypoints.md for the skills-only entry point policy.
• See references/skill-quality-patterns.md before adding or changing curdx-flow skills.

Decision Tree: Where to Start

Situation	Slash Skill
New feature, want guidance	/curdx-flow:start <name> <goal>
New feature, skip interviews	/curdx-flow:start <name> <goal> --quick
Large feature needing decomposition	/curdx-flow:triage <goal>
Resume existing spec	/curdx-flow:start (auto-detects)
Jump to specific phase	/curdx-flow:<phase>

Single Spec Flow

start/new -> research -> requirements -> design -> tasks -> implement

Each phase produces a markdown artifact in ./specs/<name>/. Normal mode pauses for approval between phases. Quick mode runs all phases then auto-starts execution.

Phase Skills

Slash Skill	Agent	Output	Purpose
/curdx-flow:research	research-analyst	research.md	Explore feasibility, patterns, context
/curdx-flow:requirements	product-manager	requirements.md	User stories, acceptance criteria
/curdx-flow:design	architect-reviewer	design.md	Architecture, components, interfaces
/curdx-flow:tasks	task-planner	tasks.md	POC-first task breakdown
/curdx-flow:implement	spec-executor	commits	Autonomous task-by-task execution

Epic Flow (Multi-Spec)

For features too large for a single spec, use epic triage to decompose into dependency-aware specs.

triage -> [spec-1, spec-2, spec-3...] -> implement each in order

Entry points:

• /curdx-flow:triage <goal> -- create or resume an epic
• /curdx-flow:start -- detects active epics, suggests next unblocked spec

File structure:

specs/
  _epics/<epic-name>/
    epic.md            # Triage output (vision, specs, dependency graph)
    research.md        # Exploration + validation research
    .epic-state.json   # Progress tracking across specs
    .progress.md       # Learnings and decisions

Management Skills

Slash Skill	Purpose
/curdx-flow:status	Show all specs and progress
/curdx-flow:switch <name>	Change active spec
/curdx-flow:cancel	Cancel active execution
/curdx-flow:refactor	Update spec files after execution

Common Workflows

Quick prototype

/curdx-flow:start my-feature "Build X" --quick
# Runs all phases automatically, starts execution

Guided development

/curdx-flow:start my-feature "Build X"
# Interactive interviews at each phase
# Review and approve each artifact
/curdx-flow:implement

Large feature

/curdx-flow:triage "Build entire auth system"
# Decomposes into: auth-core, auth-oauth, auth-rbac
/curdx-flow:start  # Picks next unblocked spec

References

• references/phase-transitions.md -- Detailed phase flow, state transitions, quick mode behavior, phase skipping
• references/entrypoints.md -- Skills-only public entry point policy