Skip to main content
skill CX Codex

specify-requirements — Claude Code skill: what it does, how to install

specify-requirements is a Claude Code skill that drafts and validates PRDs in spec.md, structuring user stories and acceptance criteria.

MIT ★ 587 updated 2026-10-26

Install into Claude Code · Plugin marketplace All methods and platforms ↓
/plugin marketplace add rsmdt/the-startup
/plugin install start@the-startup
Open on GitHub

What specify-requirements does

The skill manages the ## Requirements section of .start/specs/[NNN]-[name]/spec.md. It follows a phased workflow: gathering context, identifying missing scope items, filling the template, applying validation checks, and running a single approval gate. Each requirement receives an immutable identifier such as FR-N, AC-N.M, NFR-N, or DR-N to maintain tracking across implementation plans.

Technical implementation details, database schemas, and API payloads are intentionally forbidden: the generated PRD focuses purely on WHAT to build and WHY. MECE principles guard against overlapping user stories or missing role coverage. Requirement milestones and gate statuses register via spec.js script calls during drafting.

What it helps with

  • draft the Requirements section of a project spec.md
  • define measurable acceptance criteria without leaking implementation details
  • audit user stories against MECE guidelines to prevent overlaps
  • assign persistent identifiers to functional and quality requirements

Example prompts for the agent

  • Draft the product requirements for user authentication in spec.md
  • Validate the acceptance criteria for the current feature branch
  • Fill the Requirements section for file export with measurable quality gates

How to install specify-requirements

1Plugin marketplace

/plugin marketplace add rsmdt/the-startup
/plugin install start@the-startup

This installs the whole start plugin with all its skills

2Skills CLI (Vercel)

npx skills add rsmdt/the-startup --skill specify-requirements -a claude-code

3Manually: put the files in place

~/.claude/skills/specify-requirements/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/specify-requirements/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about specify-requirements

How to install specify-requirements in Claude Code?

Run /plugin marketplace add rsmdt/the-startup in Claude Code, then execute /plugin install start@the-startup.

What does specify-requirements do?

It guides the creation of PRDs, checks scope consistency across user roles, and writes structured Markdown into .start/specs/.

Does this skill write API endpoints or architecture designs?

No. The skill strictly limits output to observable product behavior and goals, leaving API and technical architectures to solution design docs.

Source text

SKILL.md · MIT
---
name: specify-requirements
description: Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on the Requirements part of a spec.md in .start/specs/.
---

## Persona

Act as a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.

**Spec Target**: $ARGUMENTS

## Interface

PRDSection {
  name: string
  status: Complete | NeedsInput | InProgress
  topic?: string       // what needs clarification, if NeedsInput
}

State {
  specId = ""
  sections: PRDSection[]
  clarificationMarkers: number
}

## Constraints

**Always:**
- Write the `## Requirements` part of `spec.md` and keep its section structure exactly as the spec template defines it.
- Draft every section, validate, then close the part with one approval gate — not one review per section.
- Obtain user disposition (confirm / correct / discard) on research findings before folding them into the PRD — an unconfirmed finding is a hypothesis, not a requirement. Ask each observable finding (a product rule users could tell apart in the UI or the interface the brief or contract defines) as its own question, batched up to four per call; list the rest for confirmation with the approval. Error precedence, unknown or null fields, and Origin, Host, or CSRF checks are never observable: take the recommended default.
- Cite Standing assumptions from the clarification ledger as `[ASSUMPTION An]` in the affected sections; the assumption itself lives only in the Ledger's Assumptions table.
- Run validation checklist before declaring PRD complete.
- Verify MECE after completing each enumerated section (who, features, acceptance criteria, quality gates, data).
- Assign stable IDs as sections are written — FR-N, AC-N.M, NFR-N, DR-N — and never renumber; the plan's slice tasks trace them.
- Give every quality gate a measurable, implementation-blind pass condition (threshold, or reference dataset + threshold, or behavior + condition).
- Follow the Markdown block discipline (see Markdown Blocks reference): structured, scannable Markdown — `> [!NOTE]` callouts, GitHub task lists, tables — over flat prose. Keep a stable heading spine.

**Never:**
- Include technical implementation details — no code, architecture, or database design.
- Include API specifications — they belong in the Solution part.
- Write quality gates as solution design — state observable behavior and thresholds (WHAT); mechanisms, harnesses, and architectures are the SDD's (HOW).
- Skip the multi-angle validation before completing.
- Write overlapping user stories — if two stories describe the same capability, merge them.
- Leave coverage gaps — if a role's goal is served by no feature, or a feature has no acceptance criteria, flag it.

## Reference Materials

- [Focus and MECE](reference/focus-and-mece.md) — PRD focus areas and MECE rules for who, features, acceptance criteria, quality gates, data
- [Markdown Blocks](../specify-plan/reference/markdown-blocks.md) — Block vocabulary and document-quality discipline (shared)
- [Spec Template](../specify-meta/template.md) — the `## Requirements` part of `.start/specs/[NNN]-[name]/spec.md`
- [Validation](validation.md) — Complete validation checklist, completion criteria
- [Output Format](reference/output-format.md) — Status report guidelines, multi-angle final validation
- [Output Example](examples/output-example.md) — Concrete example of expected output format

## Workflow

### 0. Brainstorm

If the specify orchestrator already ran its Clarify Intent phase, consume its ledger (answered unknowns, Standing assumptions) instead of re-probing — ask only about new gaps the template exposes. Never re-ask what clarification already answered.

Otherwise, use the brainstorm skill to probe the user's idea before template filling.

Focus on understanding:
- What problem this solves and for whom.
- Key constraints and success criteria.
- Scope boundaries — what's in and what's out.

Output feeds into the discover/document cycle with clearer context.

### 1. Discover

Identify the gaps between what is known and what each section of the Requirements part needs.

Close them yourself in the main context: competitive landscape, roles, goals, and pain points, edge cases. Launch parallel research agents only when the domain is unknown territory — an unfamiliar market, regulation, or standard needing independent investigations — and present their findings in full.

### 2. Document

Write every section of the Requirements part with the findings, replacing each `[NEEDS CLARIFICATION]` marker. Set `gates.requirements` to `draft`. Record the gate and one `requirement` event per feature with its criteria ids (`node ${CLAUDE_PLUGIN_ROOT}/scripts/spec.js {specId} --event '{"kind":"requirement","id":"FR-1","acs":["AC-1.1","AC-1.2"]}'`).

### 3. Validate

Read `validation.md` and run the checklist. Read `reference/output-format.md` and run multi-angle validation. Fix what fails; if a gap needs the user, carry it to step 4 as a question.

### 4. Approve

Present the part for one approval:
- one or two lines per section — what it now says;
- each observable item still undecided (a finding, an assumption, an open question), each as its own question with its proposed default, sent in the same call as the approval question (up to four questions per call);
- the non-observable findings and defaults together, confirmed with the approval.

Ask the user to choose between *Approve and continue*, *Walk me through section by section*, or *Change [topic]*. A walkthrough presents one section at a time for approval. Record each answered assumption and question as an event. On approval set `gates.requirements` to `approved`, record the `gate` event, and report status per `reference/output-format.md`.

### Entry Point

Read `reference/focus-and-mece.md` for the four PRD dimensions (WHAT/WHY/WHO/WHEN) and MECE rules. Then execute step 0 (Brainstorm) and steps 1 through 4 in order.

© Rudolf S. · MIT · rsmdt/the-startup

Similar skills

All skills for Writing and docs →

From the same set50

The whole set →
requirements-elicitation requirements-elicitation is a Claude Code skill that turns vague ideas into testable requirements with priorities and acceptance criteria. CX Codex +1 ★ 587repo stars pattern-detection pattern-detection finds naming conventions, architectural layers, and test styles across files. Keeps generated code aligned with repository habits. CX Codex +1 ★ 587repo stars monitor-production The monitor-production subagent plans production metrics, logs, traces, alerts, and dashboards. Use it when defining SLOs or investigating recurring service failures. CX Codex ★ 587repo stars review-compatibility review-compatibility — a subagent for Claude Code that examines code for breaking changes to APIs, databases, and configs. CX Codex ★ 587repo stars build-feature build-feature is a Claude Code subagent that implements features across UI, APIs, services, and other project layers. It joins coding requests to build or change something. CX Codex ★ 587repo stars reflect The reflect skill reads Claude Code session logs over a date range, spots weaknesses in project setup, and proposes concrete changes — new skills, hooks, rules, or edits to CLAUDE.md. CX Codex +1 ★ 587repo stars validate validate orchestrates spec reviews, file audits, spec-to-code drift detection, and constitution rule checks across specialist subagents. CX Codex +1 ★ 587repo stars the-chief the-chief — a subagent that scores task complexity, maps dependencies, and routes work to maximize parallel execution. Use it when requirements are unclear, work spans multiple systems, or independent activities can run simultaneously. CX Codex ★ 587repo stars

Project sponsors

Companies that keep this analytics open