skills.rest
kryota-dev
kryota-devCOMMUNITY
Explore all skills by this author →
Website𝕏@ryotaneko827GitHub

spec

Guide users through five-phase spec-driven development workflows.

1|Updated Oct 13, 2022
Search Tags:#workflow#design#planning#spec-driven#claude-code#specs
One-click install
npx skills add https://github.com/kryota-dev/dotfiles --skill spec-kryota-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec
Source: https://github.com/kryota-dev/dotfiles/tree/main/.bin/.claude/skills/spec
Command: npx skills add https://github.com/kryota-dev/dotfiles --skill spec-kryota-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and scaffolds a structured, multi-phase spec-driven development workflow using Claude Code, helping teams define clear requirements and design artifacts before implementation.

Core Features & Use Cases

  • Guides users through five phased workflows: planning, requirements, design, plan, and implementation.
  • Creates a dedicated specs workspace (./.claude/specs) and per-task spec directories with timestamped naming.
  • Enforces deterministic artifacts and structured conventions for reproducible development.

Quick Start

Invoke Claude Code to initiate the five-phase spec-driven development process as described in this skill.

Frequently Asked Questions about spec

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

FAQPage Schema
What is spec-driven development and how does it structure software planning?▼

Spec-driven development formalizes software task scopes through structured phases. It guides teams through planning, requirements, design, and implementation, generating deterministic artifacts to ensure reproducible development before writing code.

How do I create structured specs and requirements with Claude Code?▼

You can create structured specs by invoking Claude Code to initiate a five-phase workflow. It scaffolds a dedicated specs workspace with timestamped directories, enforcing conventions for requirements, design, and plan artifacts.

Can I use this spec-driven workflow for existing software team projects?▼

Yes, this workflow applies to software teams wanting to formalize task scopes. It creates a dedicated specs workspace within your project directory, establishing deterministic conventions for multi-phase development.

What's the best way to manage phased development artifacts and plan documents?▼

The best way is using a structured spec workspace that organizes artifacts into per-task directories. This enforces deterministic naming and conventions across planning, requirements, design, and implementation phases.

Does spec-driven development require external dependencies or tools?▼

No external dependencies are required. The workflow operates entirely within Claude Code, creating local spec directories and artifacts to guide the development process without needing additional packages.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

trigger-setup

Initialize Trigger.dev with npx trigger init and generate trigger.config.ts.

Community
Intermediate
UBAIDRAZA1UBAIDRAZA1

phase-progress-auditor

Audit phase-level workstreams to detect complete, partial, or missing artifacts.

Community
Intermediate
CharGrnmnCharGrnmn
1

gpd-complete-milestone

Mark completed research milestones, archive documents, and tag them in version control.

Community
Advanced
ZhiHanZZhiHanZ

forge-planning

Extract goals, constraints, and unknowns to scaffold DESIGN.md and features.json.

Community
Intermediate