dev

Automates end-to-end feature development guided by spec and design documents.

2|1|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill dev-byeongminlee
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dev
Source: https://github.com/ByeongminLee/nextjs-claude-code/tree/main/template/.claude/skills/dev
Command: npx skills add https://github.com/ByeongminLee/nextjs-claude-code --skill dev-byeongminlee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Transforming a written spec and design into a concrete, verified feature is error-prone and time-consuming when done manually. This Skill automates the end-to-end workflow, coordinating planning, execution, and verification so teams can ship features more reliably.

Core Features & Use Cases

  • Reads spec/feature/[name]/spec.md and design.md to extract requirements and design intent.
  • Generates PLAN.md inside the feature directory, supports resuming interrupted work and team mode (--team), and coordinates feature delivery.
  • Executes and verifies the feature implementation, ensuring alignment with the original spec and design and surfacing gaps early.

Quick Start

Run /init to analyze your codebase, then use /spec to define a feature and /dev to implement and verify it.

Frequently Asked Questions about dev

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

FAQPage Schema
How do I automate feature development from a spec and design document?

You can automate feature development by reading spec.md and design.md files to extract requirements, generating a PLAN.md, and coordinating execution and verification to ensure the delivered feature aligns with the original specification.

How does spec-driven workflow handle resuming interrupted feature implementation?

Spec-driven workflow handles interruptions by supporting a resume mode that reads the existing PLAN.md and CONTEXT.md inside the feature directory, allowing the automated development process to continue seamlessly from where it previously stopped.

Can I use team mode for collaborative feature delivery and agent spawning?

Yes, you can use the --team flag to enable team mode for collaborative feature delivery. This mode coordinates feature implementation by outputting agent spawn decisions to distribute tasks among subsequent automation agents.

Do I need a specific repository structure to generate a PLAN.md for feature implementation?

Yes, you need a properly initialized repository with a specific directory structure. The automation requires spec/feature/[name]/spec.md and design.md files to exist inside the feature directory so it can extract requirements and generate the PLAN.md.

What is the best way to verify that delivered features match the original specification?

The best way to verify delivered features against the original specification is to use an automated end-to-end workflow that executes the implementation and surfaces gaps early, ensuring alignment with the spec.md and design.md documents during delivery.

Why does dev automation require separate spec and design documents before generating a plan?

Dev automation requires separate spec.md and design.md documents because the spec extracts concrete requirements while the design captures intent. Reading both ensures the generated PLAN.md accurately reflects the full scope before execution and verification begin.