skills.rest
peopleforrester
peopleforresterCOMMUNITY
Explore all skills by this author →
Website𝕏@peopleforresterGitHub

spec-driven-development

Generates .spec.md, tasks.md, and log.md artifacts via an 8-category interview process.

3|Updated Jan 29, 2026
Search Tags:#planning#documentation#onboarding#specification#interview#feature-development
One-click install
npx skills add https://github.com/peopleforrester/claude-dotfiles --skill spec-driven-development-peopleforrester
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-driven-development
Source: https://github.com/peopleforrester/claude-dotfiles/tree/main/skills/development/spec-driven-development
Command: npx skills add https://github.com/peopleforrester/claude-dotfiles --skill spec-driven-development-peopleforrester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Spec-driven development helps teams capture complete feature requirements through a structured interview process before coding, reducing scope creep and rework.

Core Features & Use Cases

  • Structured 8-category interview: Functional, Technical, Data Model, Edge Cases, Security, Testing, Non-Functional, Implementation.
  • Artifact generation: Creates .spec.md docs, tasks.md, and log.md to guide implementation.
  • Onboarding and planning: Great for unfamiliar codebases or complex features.

Quick Start

Use the /spec-new command to begin the interview-based spec, then work through the 8 categories to finalize a complete plan before coding.

Frequently Asked Questions about spec-driven-development

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

FAQPage Schema
How do I capture feature requirements before coding to reduce scope creep?▼

Capture feature requirements through an interview-driven specification process that guides teams through structured categories before coding. This establishes clear acceptance criteria and reduces rework.

What is the best way to plan complex features for an unfamiliar codebase?▼

The best way to plan complex features for an unfamiliar codebase is using a structured 8-category interview. It covers Functional, Technical, Data Model, Edge Cases, Security, Testing, Non-Functional, and Implementation requirements.

How do I start the interview process for feature specification?▼

Start the feature specification interview by running the /spec-new command. This initiates the interview process so you can work through the categories to finalize a complete plan before coding.

What artifacts are generated during interview-driven specification?▼

Interview-driven specification generates .spec.md documents, tasks.md, and log.md files. These artifacts establish conventions and provide a structured implementation plan to guide your development workflow.

Can I use this structured specification process for project onboarding?▼

Yes, you can use this structured specification process for project onboarding. It is specifically applied at project initiation and when onboarding to unfamiliar codebases to capture complete feature requirements.

Related Skills

Explore More Software Engineering Skills→
trevorbyrumtrevorbyrum
1

project-questions

Interview users to define project scope, assumptions, and constraints.

Community
Intermediate
marcius-llmusmarcius-llmus
1

tlc-spec-driven

Plan software projects into testable specifications and atomic tasks.

Community
Advanced
Luney-IndustriesLuney-Industries
4

plan-task

Fetch Jira or Linear tickets and create implementation plans with security checks.

Official
Advanced
Nir-BhayNir-Bhay
19

backlog-refinement-guide

Guide backlog refinement sessions using the DEEP framework and Planning Poker.

Community
Intermediate