Spec
Writes a spec for one feature: a short PRD (problem and user journeys) plus the technical design an agent builds from. Use when decisions must be settled before building. The spec is the ticket.
Install
npx skills add owainlewis/blueprint --skill specgit clone --depth 1 https://github.com/owainlewis/blueprint.git /tmp/blueprint
mkdir -p ~/.claude/skills
cp -r /tmp/blueprint/skills/spec ~/.claude/skills/specPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Spec Fill in the [spec template](references/spec.md) for one feature. The top half says what to build and for whom. The bottom half says how, for the agent that builds it. The spec is the ticket. ## Process 1. Read the request, the code it touches, `REQUIREMENTS.md`, and `ARCHITECTURE.md`. 2. Ask the user about each choice that changes behavior, data, interfaces, or security. Give your recommended answer with each question. 3. Copy the template into the ticket, or into `docs/<feature-slug>/spec.md` if there is none. Fill every section, replace every bracketed placeholder, and delete the guidance comments. Write "None" where a section has nothing. 4. Compare the spec with `REQUIREMENTS.md` and `ARCHITECTURE.md`. Ask the user to settle each place they disagree. 5. Stop when another agent could build it without guessing a decision. ## Template Use [references/spec.md](references/spec.md). ## Rules - Keep existing `AC-n`, `J-n`, `REQ-n`, and `INV-n` IDs. Never reuse or renumber them. - Link to requirements and architecture instead of copying them. - Every journey has at least one acceptance row that proves it. - Every spec has a diagram. Check that it agrees with the text. - Describe interfaces, schemas, and rules. Leave the code and the list of files to the agent that builds it. - For code that does not exist yet, describe the check as a scenario and expected result.
Details
- Skill name
spec- Repository
- owainlewis/blueprint
- Path
skills/spec/SKILL.md- License
- MIT
- Repo updated
- 10 November 2026
FAQ
What does the Spec skill do?
Writes a spec for one feature: a short PRD (problem and user journeys) plus the technical design an agent builds from. Use when decisions must be settled before building. The spec is the ticket.
How do I install the Spec skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add owainlewis/blueprint --skill spec. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Spec popular?
It lives in owainlewis/blueprint, which has 434 GitHub stars and 73 forks.
Related skills
Architecture
434owainlewis/blueprint
Writes root ARCHITECTURE.md from a fixed template: the intended system, a data flow diagram, the data model, and the rules every feature must follow. Use for a new system or a change to its boundaries, data, or deployment.
Architecture Review
434owainlewis/blueprint
Reviews a technical proposal before any code is written: an architecture, spec, RFC, ADR, or design issue. Finds choices that would make it wrong, unsafe, or impossible to prove, and the open questions that block building it.
Codex Issue Coordinator
434owainlewis/blueprint
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
Content Experimentation Best Practices
200sanity-io/agent-toolkit
Content experimentation and A/B testing guidance covering experiment design, hypotheses, metrics, sample size, statistical foundations, CMS-managed variants, and common analysis pitfalls. Use this skill when planning experiments, setting up variants, choosing success metrics, interpreting statistical results, or building experimentation workflows in a CMS or frontend stack.
Requirements
434owainlewis/blueprint
Writes the product requirements document (PRD) in root REQUIREMENTS.md as user stories with checkable outcomes. Use for a new product or a change to what it should do.
Content Modeling Best Practices
200sanity-io/agent-toolkit
Structured content modeling guidance for schema design, content architecture, content reuse, references versus embedded objects, separation of concerns, and taxonomies across Sanity and other headless CMSes. Use this skill when designing or refactoring content types, deciding field shapes, debating reusable versus nested content, planning omnichannel content models, or reviewing whether a schema is too page-shaped or presentation-driven.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.