Requirements
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.
Install
npx skills add owainlewis/blueprint --skill requirementsgit clone --depth 1 https://github.com/owainlewis/blueprint.git /tmp/blueprint
mkdir -p ~/.claude/skills
cp -r /tmp/blueprint/skills/requirements ~/.claude/skills/requirementsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Requirements Fill in the [requirements template](references/requirements.md) in root `REQUIREMENTS.md`. It is the PRD for the whole product; keep it current. One feature goes in a [spec](../spec/SKILL.md), technical decisions in [architecture](../architecture/SKILL.md). ## Process 1. Read the request, the existing `REQUIREMENTS.md`, and any research the user gave you. 2. Ask the user about each product decision that is missing. Give your recommended answer with each question. Look up facts in the repository instead of asking. 3. Write one user story for each thing a user needs to do, with a `REQ-n` ID and at least one "Done when" a person could check. Include what the user sees when something fails or is denied. 4. Replace every bracketed placeholder and delete the guidance comments. 5. Stop when the document is ready for review. ## Template Use [references/requirements.md](references/requirements.md). ## Rules - Keep existing `REQ-n` IDs. Never reuse or renumber them. - Write from the user's side. Leave out how it will be built, unless a technology is required. - Label assumptions. Never invent research, targets, or rules. - Take the author from the request, or else from `git config user.name`. Set the date each time the document changes. - Set the status to Approved only when a human approves the document. ## Return Report the path, the decisions made, and any blocking question.
Details
- Skill name
requirements- Repository
- owainlewis/blueprint
- Path
skills/requirements/SKILL.md- License
- MIT
- Repo updated
- 10 November 2026
FAQ
What does the Requirements skill do?
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.
How do I install the Requirements skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add owainlewis/blueprint --skill requirements. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Requirements 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.
Spec
434owainlewis/blueprint
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.
X Publish
356kangarooking/x-skills
Publish tweets and threads to X (Twitter) draft using browser automation. Use when user wants to publish content to X, save to drafts, or mentions "publish to X", "post tweet", "x-publish", "发布推文". Supports short tweets and threads. NEVER auto-publish, always saves to draft.
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.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.