Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Create and validate product requirements documents (PRD). An agent skill from rsmdt/the-startup.
Install Specify Requirements
$ npx skills add rsmdt/the-startup --skill specify-requirements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install rsmdt/the-startup specify-requirements --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/start/skills/specify-requirements .claude/skills/specify-requirements && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .claude/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirementsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add rsmdt/the-startup --skill specify-requirements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install rsmdt/the-startup specify-requirements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/start/skills/specify-requirements .agents/skills/specify-requirements && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .agents/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rsmdt/the-startup --skill specify-requirements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install rsmdt/the-startup specify-requirements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/start/skills/specify-requirements .cursor/skills/specify-requirements && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .cursor/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/rsmdt/the-startup.git --path plugins/start/skills/specify-requirements--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add rsmdt/the-startup --skill specify-requirements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install rsmdt/the-startup specify-requirements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/start/skills/specify-requirements .gemini/skills/specify-requirements && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .gemini/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install rsmdt/the-startup specify-requirementsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add rsmdt/the-startup --skill specify-requirements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/start/skills/specify-requirements .github/skills/specify-requirements && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .github/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add rsmdt/the-startup --skill specify-requirements -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install rsmdt/the-startup specify-requirements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/rsmdt/the-startup.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/start/skills/specify-requirements .opencode/skills/specify-requirements && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "specify-requirements" agent skill from https://github.com/rsmdt/the-startup/tree/main/plugins/start/skills/specify-requirements into .opencode/skills/specify-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specify-requirements", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
specify-requirements- GitHub stars
- 557
- Token cost
- ~985 tokens
- SKILL.md length
- 443 words
- Files
- 8
- Skills in repo
- 27
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and validate product requirements documents (PRD). An agent skill from rsmdt/the-startup.
- Works in 5 steps: Brainstorm → Discover → Document → …
- Writing requirements
- SKILL.md covers Persona, Interface, Constraints and Reference Materials, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Specify Requirements is an agent skill from rsmdt/the-startup. Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on requirements.md files in .start/specs/.
Its SKILL.md is about 990 tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files (for example `evals/evals.json`, `examples/good-prd.md` and `examples/output-example.md`).
It sits in Product & Project Management, covering PRD writing and User stories. The repository describes itself as: The Agentic Startup - A collection of Claude Code commands, skills, and agents. The licence is MIT.
When your agent uses it
- Writing requirements
- Defining user stories
- Specifying acceptance criteria
- Analyzing user needs
Example prompts
- “/specify-requirements”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 88d447c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Specify Requirements loads about 985 tokens when it runs. Until then it costs about 60 tokens; SKILL.md has 443 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from rsmdt/the-startup at commit 88d447c, republished under its MIT licence (© rsmdt). 443 words, ~985 tokens.
Download SKILL.mdSave it as
.claude/skills/specify-requirements/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- 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 requirements.md files 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:
- Use template.md structure exactly — preserve all sections as defined.
- Follow iterative cycle: discover → document → review per section.
- Present ALL agent findings to user — complete responses, not summaries.
- Wait for user confirmation before proceeding to the next cycle.
- Run validation checklist before declaring PRD complete.
- Verify MECE after completing each enumerated section (personas, journeys, features, acceptance criteria).
Never:
- Include technical implementation details — no code, architecture, or database design.
- Include API specifications — belongs in SDD.
- Skip the multi-angle validation before completing.
- Remove or reorganize template sections.
- Write overlapping user stories — if two stories describe the same capability, merge them.
- Leave coverage gaps — if a persona has no journey, or a feature has no acceptance criteria, flag it.
Reference Materials
- Focus and MECE — PRD focus areas and MECE rules for personas, journeys, features, acceptance criteria
- Template — PRD template structure, write to
.start/specs/[NNN]-[name]/requirements.md - Validation — Complete validation checklist, completion criteria
- Output Format — Status report guidelines, multi-angle final validation
- Output Example — Concrete example of expected output format
- Examples — Well-structured PRD reference
Workflow
0. Brainstorm
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.
Show full SKILL.md (183 more words)Show less
1. Discover
Identify gaps between what is known and what template.md requires for the current section.
Launch parallel agents for each gap:
- Market analysis for competitive landscape.
- User research for personas and journeys.
- Requirements clarification for edge cases.
Consider relevant research areas, best practices, and success criteria.
2. Document
Update the PRD with findings for the current section:
- Apply findings to the section being processed.
- For each
[NEEDS CLARIFICATION]marker, replace with findings content.
Focus only on the current section being processed. Preserve template.md structure exactly.
3. Review
Present ALL agent findings to user, including:
- Conflicting information or recommendations.
- Questions needing clarification.
Ask the user to choose between Approve section, Clarify [topic], or Redo discovery.
4. Validate
Read validation.md and run the checklist. Read reference/output-format.md and run multi-angle validation.
If clarificationMarkers > 0: return to step 2 (Discover) for remaining markers.
If clarificationMarkers = 0: 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), then repeat steps 1 through 3 for each section in template.md, then execute step 4 (Validate).
© rsmdt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files in plugins/start/skills/specify-requirements of rsmdt/the-startup.
- SKILL.md
- evals/evals.json
- examples/good-prd.md
- examples/output-example.md
- reference/focus-and-mece.md
- reference/output-format.md
- template.md
- validation.md
Open the folder on GitHubat commit 88d447c
Compare with similar skills
Specify Requirements next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Specify Requirements this skillrsmdt/the-startup | 557 | — | ~985 | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| Ralph Tui Create JSONsubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| To Prdywwynm/EverythingDone | 144 | 11 repos | ~777 | Automated safety check: Pass | GPL-3.0 | |
| Use Case Writerphucnt-bazone-vietnam/use-case-writer | 142 | — | ~4.1k | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
To Prd
ywwynm/EverythingDone
Turn the current conversation context into a PRD and publish it to the project issue tracker.
Use Case Writer
phucnt-bazone-vietnam/use-case-writer
Generate Use Case specifications in English Markdown following the IT BA standard 13-field template (Karl Wiegers / IIBA).
Project Planner
adrianpuiu/claude-skills-marketplace
Comprehensive project planning and documentation generator for software projects.
More from rsmdt/the-startup
All 27 skills in this repoAnalyze
rsmdt/the-startup
Deep-dive codebase analysis that explains how things actually work — business rules, architecture patterns, auth flows, data models, integrations, and performance hotspots.
Implement
rsmdt/the-startup
Implementation entry point. An agent skill from rsmdt/the-startup.
Implement Factory
rsmdt/the-startup
Factory loop orchestrator for multi-feature or multi-component implementation manifests.
Agentic Patterns
rsmdt/the-startup
Context enrichment for agentic AI application development using LangChain, Vercel AI SDK, and assistant-ui.
API Contract Design
rsmdt/the-startup
REST and GraphQL API design patterns, OpenAPI/Swagger specifications, versioning strategies, and authentication patterns.
Architecture Selection
rsmdt/the-startup
System architecture patterns including monolith, microservices, event-driven, and serverless, with C4 modeling, scalability strategies, and technology selection criteria.
Related
Categories
Questions about Specify Requirements
What does Specify Requirements do?
Create and validate product requirements documents (PRD). An agent skill from rsmdt/the-startup. Specify Requirements is an agent skill from rsmdt/the-startup. Create and validate product requirements documents (PRD).
When should I use Specify Requirements?
Specify Requirements fits situations like: writing requirements; defining user stories; specifying acceptance criteria; analyzing user needs.
How do I install Specify Requirements in Claude Code?
Run `npx skills add rsmdt/the-startup --skill specify-requirements -a claude-code`. Or copy the skill folder (plugins/start/skills/specify-requirements in rsmdt/the-startup) into .claude/skills/specify-requirements in your project. Claude Code loads it when a task matches its description.
How do I install Specify Requirements in Codex?
Run `npx skills add rsmdt/the-startup --skill specify-requirements -a codex`. Or copy the skill folder (plugins/start/skills/specify-requirements in rsmdt/the-startup) into .agents/skills/specify-requirements in your project. Codex loads it when a task matches its description.
Can I use Specify Requirements in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add rsmdt/the-startup --skill specify-requirements -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specify-requirements, .gemini/skills/specify-requirements, .github/skills/specify-requirements and .opencode/skills/specify-requirements in your project.
What does Specify Requirements need to run?
SKILL.md names no scripts, command-line tools or credentials: Specify Requirements is instructions for the agent only.
Does Specify Requirements access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Specify Requirements safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Specify Requirements use?
Specify Requirements is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Specify Requirements use?
About 985 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Specify Requirements?
Skills that share tags, products or a category with Specify Requirements: Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars), Ralph Tui Create JSON (subsy/ralph-tui, 2.5k stars) and To Prd (ywwynm/EverythingDone, 144 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Specify Requirements?
rsmdt (a GitHub user) maintains it in rsmdt/the-startup, which has 557 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on August 3, 2026.
Source: rsmdt/the-startup on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.