skills.rest
alissonpef
alissonpefCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-driven-development

Create structured specifications with assumptions, objectives, and testing strategy before implementation.

Updated Apr 21, 2026
Search Tags:#planning#testing#specification#requirements#copilot#spec-driven-development
One-click install
npx skills add https://github.com/alissonpef/copilot-agent-skills --skill spec-driven-development-alissonpef
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/alissonpef/copilot-agent-skills/tree/main/.github/skills/spec-driven-development
Command: npx skills add https://github.com/alissonpef/copilot-agent-skills --skill spec-driven-development-alissonpef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you turn vague ideas into clear, reviewable specifications before implementation, reducing rework and hidden assumptions.

Core Features & Use Cases

  • Clarifies requirements by surfacing assumptions and open questions before coding.
  • Defines objective, commands, structure, code style, testing strategy, and boundaries for a project or feature.
  • Supports a gated workflow for specify, plan, tasks, and implement, with human review at each stage.
  • Useful for new features, ambiguous requests, architectural changes, and larger tasks that need alignment.

Quick Start

Use the spec-driven-development skill to turn this vague feature request into a complete specification.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I turn ambiguous requirements into clear specifications before coding?▼

To turn ambiguous requirements into clear specifications, you must surface assumptions and open questions first. This approach defines objectives, commands, project structure, code style, testing strategy, and boundaries before implementation begins.

What is the best way to plan multi-file architectural changes without hidden assumptions?▼

Planning multi-file architectural changes requires a gated workflow with human review at each stage. You define boundaries, structure, and testing strategy, ensuring alignment on objectives before proceeding to implementation.

When do I need to write software specifications for a new feature?▼

You need software specifications for new features, ambiguous requests, architectural decisions, and larger tasks. It clarifies requirements by surfacing hidden assumptions and defining objective acceptance criteria before development.

Can I use a gated workflow to review plans before implementation with Copilot?▼

Yes, a gated workflow supports specify, plan, tasks, and implement stages with human review at each phase. This ensures your project structure, commands, and testing strategy are approved before coding.

What should be included in a specification to reduce rework on new projects?▼

A specification to reduce rework should include assumptions, objectives, commands, project structure, code style, testing strategy, boundaries, and acceptance criteria. This structured plan undergoes human approval before coding starts.

Related Skills

Explore More Software Engineering Skills→
hotaqhotaq

deep-interview

Clarify vague requests into execution-ready specifications with structured questioning.

Community
Advanced
skaisserskaisser
4

plan-approved

Execute reviewed plans by delegating work to subagents and tracking task completion.

Community
Advanced
GoBeromsuGoBeromsu
2

spec-driven-development

Create structured specifications with a four-phase workflow before coding.

Community
Advanced
Nero-kkNero-kk

karpathy-guidelines

Enforce explicit assumptions and minimal implementations in LLM-generated code.

Community
Basic