cw-spec

Transform vague feature ideas into detailed actionable specifications.

14|1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/sighup/claude-workflow --skill cw-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cw-spec
Source: https://github.com/sighup/claude-workflow/tree/main/skills/cw-spec
Command: npx skills add https://github.com/sighup/claude-workflow --skill cw-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transform vague feature ideas into a detailed, actionable specification that serves as the single source of truth for the entire development lifecycle.

Core Features & Use Cases

  • Clear, testable requirements and user stories that guide implementation.
  • Definition of demoable units of work and proof artifacts to validate completion.
  • Structured scope and repository standards to ensure consistent planning and execution.

Quick Start

Describe your feature idea in one sentence and have this spec writer generate a complete specification for planning.

Frequently Asked Questions about cw-spec

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

FAQPage Schema
How do I turn a vague product idea into a concrete feature spec?

Generating a feature spec from a one-sentence idea produces structured objectives, user stories, and acceptance criteria. This actionable specification serves as the single source of truth for development planning and execution.

What is the best way to write testable requirements and user stories for development?

The best way to write testable requirements and user stories is to apply a standardized spec workflow during early discovery. This defines demoable units and proof artifacts to validate completion and align engineering outcomes.

Can I use this spec generation workflow to align product, design, and engineering teams?

Yes, you can use this spec generation workflow to align product, design, and engineering teams. It applies during early discovery and planning to establish a single source of truth with standardized repository directory structures.

How do I define demoable units of work and proof artifacts for feature validation?

To define demoable units of work and proof artifacts, generate a detailed specification from your feature idea. This enforces structured scope and repository standards to validate completion and ensure consistent execution.

Does requirement gathering for feature specs require any specific dependencies?

No, requirement gathering for feature specs requires no specific dependencies or components. You simply describe your feature idea in one sentence to generate a complete, actionable specification for planning.

When do I need to generate a standardized spec workflow with directory structure?

You need to generate a standardized spec workflow with directory structure during early discovery and planning. This establishes repository standards and a single source of truth to align development teams on outcomes.