How do I install the Spec skill?

Run npx skillmds add majiayu000/spec-9 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Spec skill do?

Generate an implementation-ready specification from a feature idea It is listed under Coding & Dev Tools on SkillMD.

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Spec?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Spec by majiayu000 — Agent Skill

Name: Spec
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

Specification Generator

PROSE constraint: Orchestrated Composition — transforms a high-level idea into an implementation-ready blueprint that bridges planning and coding.

Purpose

Create a .spec.md file that serves as a deterministic contract between the planning phase and the implementation phase. Specs ensure consistent outcomes regardless of who (or what) implements them.

Process

Parse $ARGUMENTS for the feature name and description
Research the existing codebase for related patterns and conventions
Identify affected layers (frontend, backend, shared types, tests)
Generate the spec using the template below
Write the spec to docs/specs/<feature-name>.spec.md

Spec Template

# Feature: [Name]

## Problem Statement
[Why this feature is needed — the user or business problem it solves]

## Approach
[High-level strategy for implementing this feature]

## Implementation Requirements

### Core Components
- [ ] [File path] — [What this file does]
- [ ] [File path] — [What this file does]

### API Contracts (if applicable)
- `METHOD /path` — [Description] → [Response shape]

### Data Model Changes (if applicable)
- [Table/collection] — [Fields added/modified]

### UI Components (if applicable)
- [Component] — [Purpose and behavior]

## Acceptance Criteria
- [ ] [Testable criterion]
- [ ] [Testable criterion]
- [ ] [Testable criterion]

## Validation Criteria
- [ ] Unit tests >90% coverage for new code
- [ ] Integration tests for all new endpoints
- [ ] No `any` types introduced
- [ ] All inputs validated at system boundaries
- [ ] Error states handled and tested

## Dependencies
- [External package or service, if any]

## Risks
- [Risk] → [Mitigation]

## Handoff Checklist
- [ ] Spec reviewed and approved
- [ ] Architecture aligns with existing patterns
- [ ] No breaking changes to existing APIs (or migration plan included)
- [ ] Ready for implementation via `/implement-feature docs/specs/<name>.spec.md`

Output

Write the completed spec to docs/specs/ and inform the user they can implement it by running /implement-feature docs/specs/<feature-name>.spec.md.

---name: spec-9description: Generate an implementation-ready specification from a feature idea--- # Specification Generator > PROSE constraint: **Orchestrated Composition** — transforms a high-level idea > into an implementation-ready blueprint that bridges planning and coding. ## Purpose Create a `.spec.md` file that serves as a deterministic contract between the planning phase and the implementation phase. Specs ensure consistent outcomes regardless of who (or what) implements them. ## Process 1. Parse `$ARGUMENTS` for the feature name and description 2. Research the existing codebase for related patterns and conventions 3. Identify affected layers (frontend, backend, shared types, tests) 4. Generate the spec using the template below 5. Write the spec to `docs/specs/<feature-name>.spec.md` ## Spec Template ```markdown # Feature: [Name] ## Problem Statement [Why this feature is needed — the user or business problem it solves] ## Approach [High-level strategy for implementing this feature] ## Implementation Requirements ### Core Components - [ ] [File path] — [What this file does] - [ ] [File path] — [What this file does] ### API Contracts (if applicable) - `METHOD /path` — [Description] → [Response shape] ### Data Model Changes (if applicable) - [Table/collection] — [Fields added/modified] ### UI Components (if applicable) - [Component] — [Purpose and behavior] ## Acceptance Criteria - [ ] [Testable criterion] - [ ] [Testable criterion] - [ ] [Testable criterion] ## Validation Criteria - [ ] Unit tests >90% coverage for new code - [ ] Integration tests for all new endpoints - [ ] No `any` types introduced - [ ] All inputs validated at system boundaries - [ ] Error states handled and tested ## Dependencies - [External package or service, if any] ## Risks - [Risk] → [Mitigation] ## Handoff Checklist - [ ] Spec reviewed and approved - [ ] Architecture aligns with existing patterns - [ ] No breaking changes to existing APIs (or migration plan included) - [ ] Ready for implementation via `/implement-feature docs/specs/<name>.spec.md` ``` ## Output Write the completed spec to `docs/specs/` and inform the user they can implement it by running `/implement-feature docs/specs/<feature-name>.spec.md`.

Frequently asked questions

Spec