Specification

Write and maintain SPEC.md technical specifications. Use when the user asks to create, update, or review a SPEC.md file, or when planning a new feature/application that needs a specification document. Also use when the user mentions "spec", "specification", "requirements document", or asks to document what a system should do.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add roby2358/skills --skill specification
Manual install
git clone --depth 1 https://github.com/roby2358/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/specification ~/.claude/skills/specification

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Technical Specification Writing

Specs document **what** a system does, not **how** it's implemented.

They serve as:
- Reference documentation for developers
- Requirements tracking for features
- Testing guidance for QA
- Communication tool between stakeholders

## Language Requirements

Use RFC 2119 keywords for requirement levels:
- **MUST** / **MUST NOT** — Absolute requirements
- **SHOULD** / **SHOULD NOT** — Recommended but not mandatory
- **MAY** — Optional features

Write in present tense, implementation-agnostic language. Be specific about expected behavior. No code snippets.

- Keep language high-level and implementation-agnostic
- Avoid code snippets and syntax examples
- Focus on behavior and capabilities, not implementation details
- Use present tense ("The application MUST validate...")
- Be specific about expected behavior

## Required Sections

1. **Purpose** — What the system does and why
2. **UI Layout** — ASCII diagrams of component layout
3. **Functional Requirements** — Grouped by domain (e.g., Input, Processing, Output, API Integration, Storage)
4. **Non-Functional Requirements** — Performance, styling, accessibility, security
5. **Dependencies** — Libraries and frameworks with versions
6. **Implementation Notes** — Technical details too specific for requirements (framework quirks, data formats, architectural decisions)
7. **Error Handling** — Expected error conditions and responses

### Functional Requirements
Read the full skill on GitHub

Details

Skill name
specification
Path
specification/SKILL.md
Repo updated
14 November 2026

FAQ

What does the Specification skill do?

Write and maintain SPEC.md technical specifications. Use when the user asks to create, update, or review a SPEC.md file, or when planning a new feature/application that needs a specification document. Also use when the user mentions "spec", "specification", "requirements document", or asks to document what a system should do.

How do I install the Specification skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add roby2358/skills --skill specification. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Specification popular?

It lives in roby2358/skills, which has 5 GitHub stars and 0 forks.

Related skills

Coding

5

roby2358/skills

Project-specific coding conventions and constraints. Use when writing, modifying, or refactoring any code, implementing features, writing tests, or building MCP servers in this project.

Software Development

Game Design

5

roby2358/skills

Design principles for tactics and strategy games. Use when designing new mechanics, tuning existing systems, adding units or abilities, adjusting difficulty, or making any game design decision. Triggers on discussions about game balance, unit roles, terrain, pacing, spawning, healing, combat, win/loss conditions, or UI for conveying game state.

Frontend & Design

Game Productize

5

roby2358/skills

Audit a browser game for ship-readiness and produce a tiered gap list: a SHIP.md in the game repo plus pjpd tasks. Finds what gets forgotten between "the game works" and "a stranger can play it": title/menus/end screens, save and resume, audio and settings, onboarding, the mobile "sorry" screen, localization readiness, error recovery, hosting on the author's site and on portals (itch.io, Newgrounds), credits, asset licenses, and AI disclosure. Use when the user says "productize", "/game-productize", "get this game ready to ship/release/publish/launch", "what's missing before I launch", "prep f

Documents & Office Files

Writing Plans

9

sandbaseai/workbuddy-skill

Use when a specification or requirements describe a multi-step implementation and a file-specific, testable plan is needed before editing code.

Writing & Content

Repo Standardizer

9

sandbaseai/workbuddy-skill

Use when auditing or polishing a repository's public surface, documentation, templates, CI metadata, ownership, and governance configuration.

Writing & Content

End Iteration

5

tilmon-engineering/claude-skills

Use when concluding work on an open-ended goal to write iteration journal entry documenting work performed, decisions made, and state changes

Writing & Content

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.