skills.rest
hgflima
hgflimaCOMMUNITY
Explore all skills by this author →
GitHub

spec-driven-development

Create detailed specifications, technical plans, and task breakdowns for software projects.

1|1|Updated Jul 4, 2026
Search Tags:#development workflow#software development#specification#project planning#stakeholder alignment
One-click install
npx skills add https://github.com/hgflima/loopy --skill spec-driven-development-hgflima
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/hgflima/loopy/tree/main/.claude/skills/spec-driven-development
Command: npx skills add https://github.com/hgflima/loopy --skill spec-driven-development-hgflima

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps in avoiding misunderstandings and ensuring that all stakeholders have a clear understanding of the project's requirements and objectives before coding begins.

Core Features & Use Cases

  • Specify: Create comprehensive specifications for new projects or features.
  • Plan: Generate technical implementation plans based on validated specifications.
  • Tasks: Break down plans into discrete tasks with explicit acceptance criteria.
  • Implement: Execute tasks incrementally and test-driven.
  • Use Case: When starting a new project, you can use this Skill to write a spec document that outlines the project's goals, tech stack, commands, project structure, code style, testing strategy, and boundaries.

Quick Start

Generate a spec for your new project by running the spec-driven-development skill and following the guided steps.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
What is spec-driven development and how does it help with project planning?▼

Spec-driven development is a workflow that guides the creation of detailed specifications and technical plans before coding begins, ensuring stakeholder alignment and clear project objectives.

How do I create technical implementation plans from validated specifications?▼

To create technical implementation plans, you provide structured input to generate a plan based on validated specifications, which is then broken down into discrete tasks with explicit acceptance criteria.

How do I break down a software development plan into discrete tasks?▼

You break down technical implementation plans into discrete tasks with explicit acceptance criteria, allowing for incremental execution and test-driven development throughout the software development lifecycle.

Can I use this workflow for iterative development on new features?▼

Yes, this workflow supports iterative development by allowing you to specify, plan, and implement new projects or features incrementally, requiring structured input to guide the process.

What is the best way to ensure stakeholder alignment before coding begins?▼

The best way to ensure stakeholder alignment is to generate a comprehensive specification document outlining project goals, tech stack, structure, and boundaries before any implementation starts.

Related Skills

Explore More Software Engineering Skills→
sayaya1090sayaya1090

architecture

Define Handbook project architecture and module boundaries for frontend and backend layers.

Community
Advanced
flowkraftflowkraft
75

Guided Development Skill

Guide incremental feature implementation through PRD-first task decomposition.

Community
Advanced
addyosmaniaddyosmani
84.9k

spec-driven-development

Enforce a four-phase specification workflow before code implementation.

Community
Advanced
nguyenthienthanhnguyenthienthanh
24

pm-expert

Guide Agile project planning with estimation, risk, and stakeholder management.

Community
Basic