skills.rest
anaregdesign
anaregdesignOFFICIAL
Explore all skills by this author →
GitHub

spec-driven-workflow

Manage spec-first planning workflows with hierarchical execution plans in /doc/plan.md.

2|Updated Feb 23, 2026
Search Tags:#workflow#planning#development#documentation#task management#spec
One-click install
npx skills add https://github.com/anaregdesign/skills --skill spec-driven-workflow-anaregdesign
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-workflow
Source: https://github.com/anaregdesign/skills/tree/main/skills/development/spec-driven-workflow
Command: npx skills add https://github.com/anaregdesign/skills --skill spec-driven-workflow-anaregdesign

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the development process by enforcing a spec-first approach, ensuring user-visible requirements are clearly defined before implementation begins, and providing a clear, actionable plan for execution.

Core Features & Use Cases

  • Spec Documentation: Guides the creation and maintenance of user-facing requirements in /doc/spec/.
  • Execution Planning: Manages a temporary, hierarchical plan in /doc/plan.md with trackable checkboxes.
  • Workflow Synchronization: Ensures the spec and plan remain aligned throughout the development lifecycle.
  • Use Case: When tasked with building a new user-facing feature, this Skill helps define exactly what the feature should do from the user's perspective, then breaks down the implementation into manageable, checkable steps, ensuring nothing is missed and the final product meets the defined requirements.

Quick Start

Use the spec-driven-workflow skill to create a new user-facing spec document under /doc/spec/ and a corresponding execution plan in /doc/plan.md.

Frequently Asked Questions about spec-driven-workflow

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

FAQPage Schema
How do I manage a spec-first planning workflow for feature development?▼

You manage a spec-first planning workflow by defining user-visible requirements in `/doc/spec/` and generating a temporary execution plan in `/doc/plan.md` to track implementation progress via checkboxes.

What is the best way to track feature development progress alongside requirements?▼

Tracking feature development progress is done by structuring a hierarchical plan in `/doc/plan.md` with `Section`, `Subsection`, and `Sub-subsection` checkboxes that stay aligned with your spec documents.

How do I structure a temporary execution plan for software development tasks?▼

You structure a temporary execution plan by creating `/doc/plan.md` with hierarchical `Section`, `Subsection`, and `Sub-subsection` headings, tracking task completion via checkboxes, and cleaning up the file upon project completion.

Can I use this spec-driven workflow for cloud platform topology decisions?▼

No, you cannot use this spec-driven workflow for cloud platform topology decisions or app-code architecture. It is specifically designed to manage user-facing feature requirements and temporary execution planning.

When do I need a spec-first approach for my development documentation?▼

You need a spec-first approach for development documentation when building new user-facing features, ensuring user-visible requirements are clearly defined in `/doc/spec/` before implementation begins to prevent missed steps.

Related Skills

Explore More Software Engineering Skills→
jinglemansweepjinglemansweep

jp-setup

Create a .plans directory with a .gitkeep file at the repository root.

Community
Basic
beratcelik1beratcelik1
1

work

Execute development plans into tasks, code changes, tests, and commits.

Community
Intermediate
Luney-IndustriesLuney-Industries
4

ship-task

Merge GitHub pull requests and transition Linear or Jira tickets to Done.

Official
Advanced
coco-decoco-de

System Architect

Design system architectures from product and tech specs.

Official
Advanced