spec

Create or update feature specifications in spec/feature/[name]/spec.md and design.md.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define or update a feature specification by creating or editing spec/feature/[name]/spec.md and the accompanying design.md.

Core Features & Use Cases

  • Create or update a feature specification with a name, description, and optional Figma link.
  • Automatically generate or update spec.md and design.md files in the feature directory without modifying source code.
  • Supports collaboration and traceability by linking requirements to features.

Quick Start

Define a new feature by providing its name and description to generate or update the corresponding spec and design documentation.

Frequently Asked Questions about spec

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

FAQPage Schema
How do I create a feature specification for a new product requirement?

You can update an existing feature specification by editing the spec.md and design.md files within the specific feature's directory, ensuring your current requirements reflect any new design changes.

What is the best way to link Figma designs to a feature spec?

Linking Figma designs to a feature spec involves adding an optional Figma link to your specification, automatically embedding the visual design reference directly within the generated spec.md documentation.

Does defining a feature spec modify my existing source code?

Defining a feature spec does not modify source code; the process strictly creates or updates spec.md and design.md documentation files within the scoped feature directory to maintain separation of concerns.

What are the requirements for frontmatter when generating a feature spec?

Generating a feature spec requires frontmatter with a specific name and description, enforcing mandatory metadata fields at the top of the document to ensure proper feature identification and traceability.

Why do I need a separate design.md file for my feature specification?

A separate design.md file provides detailed design context alongside the spec.md, supporting collaboration and traceability by separating functional requirements from visual or architectural design details.