skills.rest
curdx
curdxCOMMUNITY
Explore all skills by this author →
GitHub

spec-workflow

Route prompts through research, requirements, design, tasks, and implement phases.

4|Updated Apr 26, 2026
Search Tags:#requirements#architecture design#task planning#spec workflow#resume workflow#execution orchestration#epic triage
One-click install
npx skills add https://github.com/curdx/curdx-flow --skill spec-workflow-curdx
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-workflow
Source: https://github.com/curdx/curdx-flow/tree/main/plugins/curdx-flow/skills/spec-workflow
Command: npx skills add https://github.com/curdx/curdx-flow --skill spec-workflow-curdx

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns large or ongoing feature requests into structured, resumable spec artifacts so Claude Code can plan, review, and execute without context rot or silent “done” failures.

Core Features & Use Cases

  • Skills-first workflow router: a single canonical entry that guides the end-to-end phases (research, requirements, design, tasks, implement) and supports resuming active work.
  • Phase-by-phase spec artifacts: produces reviewable markdown outputs in ./specs/<name>/ with explicit approval checkpoints in normal mode.
  • Single-spec and epic (multi-spec) delivery: decomposes big asks into dependency-aware specs using triage, then executes them in order.
  • Operational management skills: supports status visibility, spec switching, cancellation, and refactoring after execution.

Quick Start

Use the spec workflow to plan and start execution for a new feature by running: /curdx-flow:start my-feature "Build X" --quick

Frequently Asked Questions about spec-workflow

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

FAQPage Schema
How do I manage requirements and execution for large epics in Claude Code?▼

To manage large epics, the spec workflow decomposes requests into dependency-aware specs using triage, then executes them sequentially with resumable artifacts to prevent context rot.

How does spec-driven planning prevent silent execution failures?▼

Spec-driven planning prevents silent failures by enforcing verification before completion and generating structured spec files with explicit approval checkpoints during execution.

Can I resume a long-running feature workflow after stopping a session?▼

Yes, you can resume long-running workflows because the system supports resuming active work by routing a single prompt into existing research, requirements, design, and tasks phases.

What is the best way to decompose big feature requests into structured tasks?▼

The best way to decompose features is using epic triage, which breaks big asks into dependency-aware specs and routes them through design, task planning, and implementation phases.

Does the spec workflow support operational management like cancellation and status visibility?▼

Yes, the spec workflow supports operational management by providing status visibility, spec switching, cancellation, and post-execution refactoring capabilities.

When do I need architecture design and task planning artifacts for feature development?▼

You need architecture design and task planning artifacts when executing large or ongoing feature requests, ensuring Claude Code can review and execute without losing context.

Related Skills

Explore More Product & Management Skills→
jtsang4jtsang4
2

shape

Guide structured conversations to define product ideas and create SPEC files.

Community
Intermediate
fhltafhlta

speckit-converge

Compare code against spec, plan, and tasks to append convergence tasks.

Community
Advanced
clearsmogclearsmog
2

context-status

Report context usage, active plan, and session log status.

Community
Intermediate
zhizhunbaozhizhunbao

full-development

Orchestrate an 11-phase software development lifecycle with automated quality gates.

Community
Advanced