Spec Workflow Skill

Purpose

Keep one stable spec per feature as the source of truth. Get user approval before starting implementation. Check in after each logical chunk of work before continuing.

• Spec = what — locked requirements, stable across the entire feature
• Plan mode = how — in-session design derived from the spec before each implementation run

When to Use

• Spec-first workflow for a new feature
• Stable requirements document driving phased implementation
• "Do only the next phase" loop
• Locked requirements with explicit user approval gates

Typical trigger phrases: