Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and…
Install Requirements
$ npx skills add AI-Unified-Process/marketplace --skill requirements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install AI-Unified-Process/marketplace 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/AI-Unified-Process/marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/aiup-core/skills/requirements .claude/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .claude/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/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 AI-Unified-Process/marketplace --skill requirements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install AI-Unified-Process/marketplace requirements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Unified-Process/marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/aiup-core/skills/requirements .agents/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .agents/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 AI-Unified-Process/marketplace --skill requirements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install AI-Unified-Process/marketplace requirements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Unified-Process/marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/aiup-core/skills/requirements .cursor/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .cursor/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/AI-Unified-Process/marketplace.git --path aiup-core/skills/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 AI-Unified-Process/marketplace --skill requirements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install AI-Unified-Process/marketplace requirements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Unified-Process/marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/aiup-core/skills/requirements .gemini/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .gemini/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 AI-Unified-Process/marketplace 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 AI-Unified-Process/marketplace --skill requirements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/AI-Unified-Process/marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/aiup-core/skills/requirements .github/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .github/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 AI-Unified-Process/marketplace --skill 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 AI-Unified-Process/marketplace requirements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/AI-Unified-Process/marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/aiup-core/skills/requirements .opencode/skills/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 "requirements" agent skill from https://github.com/AI-Unified-Process/marketplace/tree/main/aiup-core/skills/requirements into .opencode/skills/requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
requirements- GitHub stars
- 142
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,094 words
- Files
- 3 (incl. references)
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and…
- Works in 10 steps: Read the vision document or project brief → Use TodoWrite to create tasks for each… → Write the document header → …
- The user asks to write requirements
- SKILL.md covers Instructions, DO NOT, Requirement Types and Glossary, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Requirements is an agent skill from AI-Unified-Process/marketplace. Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints. Use when the user asks to "write requirements", "create a PRD", "gather requirements", "document feature specs", "write user stories", "define NFRs", "list constraints", "write a glossary", "define domain terms", or mentions requirements catalog, requirements analysis, product requirements document, feature…
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/REFERENCE.md` and `references/glossary.md`).
It sits in Product & Project Management, covering PRD writing and User stories. The licence is Apache-2.0.
When your agent uses it
- The user asks to write requirements
- Gather requirements
- Document feature specs
- Write user stories
Example prompts
- “write requirements”
- “create a PRD”
- “gather requirements”
- “/requirements”
Workflow steps
10 steps, taken from the first numbered list in SKILL.md.
- Read the vision document or project brief
- Use TodoWrite to create tasks for each requirement type
- Write the document header
- For functional requirements
- For non-functional requirements
- For constraints
- Validate: run every requirement against the quality checks table above
- When updating an existing catalog whose use cases exist, set the progress status of each requirement (Open,
- Create or update docs/glossary.md with the domain terms used in the catalog, and use exactly those terms (never
- Mark todos complete
What it can do on your machine
Read from SKILL.md and the folder at commit d25bf91. 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
Links to these hosts (documentation or services it may open):
unifiedprocess.ai
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
Requirements loads about 2.5k tokens when it runs, and up to ~3.5k if it reads all its reference files. Until then it costs about 138 tokens; SKILL.md has 1,094 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 AI-Unified-Process/marketplace at commit d25bf91, republished under its Apache-2.0 licence (© AI-Unified-Process). 1,094 words, ~2,476 tokens.
Download SKILL.mdSave it as
.claude/skills/requirements/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- requirements
- description
- Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints. Use when the user asks to "write requirements", "create a PRD", "gather requirements", "document feature specs", "write user stories", "define NFRs", "list constraints", "write a glossary", "define domain terms", or mentions requirements catalog, requirements analysis, product requirements document, feature specification, or glossary.
<!--
Copyright 2025-2026 Simon Martinelli and the AI Unified Process contributors.
Part of the AI Unified Process — https://unifiedprocess.ai
Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
-->Requirements
Instructions
Create or update the requirements catalog at docs/requirements.md based on docs/vision.md.
The document contains functional requirements, non-functional requirements, and constraints organized as Markdown
tables. Alongside it, create or update the glossary at docs/glossary.md (see Glossary).
DO NOT
- Mix requirement types in a single table
- Skip the user story format for functional requirements
- Use duplicate IDs across requirement types
- Leave the Status column empty
Requirement Types
Functional Requirements (FR)
Define what the system should do. Always use the user story format:
Format: As a [role], I want [goal] so that [benefit].
| ID | Title | User Story | Priority | Status |
|---|---|---|---|---|
| FR-001 | Create Task | As a project manager, I want to create tasks so that I can track work items. | High | Open |
| FR-002 | Assign Task | As a project manager, I want to assign tasks to team members so that work is distributed. | High | Open |
| FR-003 | Filter Tasks | As a team member, I want to filter tasks by status so that I can focus on relevant items. | Medium | Open |
Non-Functional Requirements (NFR)
Define quality attributes. Must be measurable.
| ID | Title | Requirement | Category | Priority | Status |
|---|---|---|---|---|---|
| NFR-001 | Response Time | All page loads must complete within 2 seconds. | Performance | High | Open |
| NFR-002 | Availability | System must maintain 99.9% uptime during business hours. | Availability | High | Open |
| NFR-003 | Concurrent Users | System must support 100 concurrent users without degradation. | Scalability | Medium | Open |
| NFR-004 | Data Encryption | All data in transit must use TLS 1.3 encryption. | Security | High | Open |
Constraints (C)
Define limitations and boundaries imposed on the solution.
| ID | Title | Constraint | Category | Source | Priority | Status |
|---|---|---|---|---|---|---|
| C-001 | Runtime Platform | Backend must run on Java 21 LTS. | Technical | High | Open | |
| C-002 | Database Platform | System must use PostgreSQL 16. | Technical | High | Open | |
| C-003 | Browser Support | UI must support Chrome, Firefox, and Safari (latest 2 versions). | Technical | High | Open | |
| C-004 | Budget Limit | Total development cost must not exceed $50,000. | Business | High | Open | |
| C-005 | Deadline | System must be production-ready by Q2 2025. | Schedule | High | Open | |
| C-006 | Right to Erasure | Personal data of a customer must be erased within 30 days of a request. | Regulatory | GDPR Art. 17(1), 12(3) | High | Open |
The Source column is optional — omit it when no constraint comes from an outside document. It names where a
constraint comes from — a law, regulation, standard, or internal policy, down to the article or paragraph and, where it
matters, the version (GDPR Art. 17(1), ISO 27001:2022 A.8.24, Operating Policy OP-12 v3) — so the origin of a
mandated rule stays traceable. When the column is present, fill it for every Regulatory constraint and leave it empty
for the others. Keep Status the last column.
Glossary
The glossary fixes one name per domain concept, so requirements, use cases, test cases, and code all use the same
word. Use references/glossary.md as the structure (the path is relative to the folder
containing this SKILL.md): one table with the columns Term | Definition | Avoid.
- Term — the preferred name, in singular, as the business says it. One row per concept; never define a term twice.
- Definition — one or two sentences that tell this concept apart from its neighbors (a Guest is not necessarily the person who made the Reservation).
- Avoid — comma-separated synonyms that must not be used for this concept, or empty. Only list a word here when it would be ambiguous or misleading; a word listed here is flagged wherever it appears in the specifications.
Take the terms from the vision and from the nouns of the user stories: roles, business objects, states, and business events. Leave out generic words (system, data, user interface). When the glossary already exists, add new terms and keep existing rows unless the user asks to change them.
Reference
See references/REFERENCE.md for ID prefixes, priority levels, status values, NFR categories, and constraint categories. The path is relative to the folder containing this SKILL.md, not to the project root.
Show full SKILL.md (464 more words)Show less
Requirement Quality Checks
Every requirement must pass these checks before finalizing:
| Check | Rule | Bad Example | Good Example |
|---|---|---|---|
| Measurable | NFRs must have a number or threshold | "System should be fast" | "Pages load within 2 seconds" |
| Singular | One requirement per row | "System must import and export data" | Split into FR-001 and FR-002 |
| Unambiguous | No subjective terms | "User-friendly interface" | "WCAG 2.1 AA compliant" |
| Testable | Can write a pass/fail test | "System is reliable" | "99.9% uptime over 30 days" |
| Unique IDs | No duplicate IDs across all tables | Two FR-001 entries | Each ID used exactly once |
Error Recovery
- Incomplete source document: List what is missing (roles, NFR categories, constraints) and ask the user to clarify before proceeding
- Ambiguous requirement from user: Rewrite it as a measurable requirement and ask the user to confirm the threshold
- Conflicting requirements: Flag the conflict explicitly (e.g., "FR-003 requires real-time sync but C-002 limits to batch processing") and ask the user to resolve
- Missing stakeholder roles: Default to generic roles (User, Admin, System) and note them for user review
Format survives error recovery. Ambiguity, conflict, and provisional status never justify abandoning the user-story form. Every FR row — even one you are flagging as conflicting or unconfirmed — must still read "As a [role], I want [goal] so that [benefit]." Record the issue in a note or in the Status column (e.g.,
Conflict,Needs review); never by dropping the requirement to a flat statement like "Support real-time sync."
Workflow
- Read the vision document or project brief
- Use TodoWrite to create tasks for each requirement type
- Write the document header
- For functional requirements:
- Identify user roles
- Define user stories with clear goals and benefits
- Assign priorities based on business value
- For non-functional requirements:
- Define measurable quality attributes
- Categorize by NFR type
- Ensure requirements are testable
- For constraints:
- Document technical and business limitations
- Categorize by constraint type
- Name the source of each regulatory or externally imposed constraint in the Source column
- Validate: run every requirement against the quality checks table above
- No duplicate IDs across all tables
- All Status columns filled
- Hard gate: every FR User Story matches "As a [role], I want [goal] so that [benefit]" — scan each row; any row missing "As a", "I want", or "so that" is rejected and rewritten before finalizing, no exceptions
- All NFRs contain a measurable threshold
- When updating an existing catalog whose use cases exist, set the progress status of each requirement (Open,
In Progress, Implemented, Verified) from the
**Status:**of the use cases that link it, as defined under Status in the reference; never change a Deferred or Rejected status on your own - Create or update
docs/glossary.mdwith the domain terms used in the catalog, and use exactly those terms (never an Avoid synonym) in every requirement - Mark todos complete
© AI-Unified-Process, Apache-2.0. 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 2 other files (references) in aiup-core/skills/requirements of AI-Unified-Process/marketplace.
- SKILL.md
- references/REFERENCE.md
- references/glossary.md
Open the folder on GitHubat commit d25bf91
Compare with similar skills
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 |
|---|---|---|---|---|---|---|
| Requirements this skillAI-Unified-Process/marketplace | 142 | — | ~2.5k | Automated safety check: Pass | Apache-2.0 | |
| 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 | 143 | — | ~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 AI-Unified-Process/marketplace
All 14 skills in this repoSpec Review
AI-Unified-Process/marketplace
Reviews the specification artifacts in docs/ (requirements, use case diagram, use case specifications, test cases, BPMN process models, entity model, glossary) against each other in two parts: a…
Use Case Spec
AI-Unified-Process/marketplace
Creates detailed use case specification documents with actors, preconditions, main success scenarios, alternative flows, postconditions, and business rules.
Business Process
AI-Unified-Process/marketplace
Creates or updates BPMN 2.0 business process models (docs/processes/BP-XXX-.bpmn) from the requirements catalog and the use case diagram: one pool per process, one lane per actor, every activity one…
Test Case
AI-Unified-Process/marketplace
Creates end-to-end test case documents (TC-.md) that chain several use cases into one user journey with a step-by-step Flow table, concrete test data, and final validations.
Entity Model
AI-Unified-Process/marketplace
Creates entity model documents with Mermaid.js ER diagrams and attribute tables defining entities, relationships, data types, and validation rules.
Browserless Test
AI-Unified-Process/marketplace
Creates Vaadin Browserless server-side unit tests for Vaadin views covering navigation, component interactions, form validation, grid operations, and notifications.
Related
Categories
Questions about Requirements
What does Requirements do?
Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and…. Requirements is an agent skill from AI-Unified-Process/marketplace. Gathers, organizes, and documents software requirements into structured catalogs with functional requirements (user stories), non-functional requirements (measurable quality attributes), and constraints.
When should I use Requirements?
Requirements fits situations like: the user asks to write requirements; gather requirements; document feature specs; write user stories.
How do I install Requirements in Claude Code?
Run `npx skills add AI-Unified-Process/marketplace --skill requirements -a claude-code`. Or copy the skill folder (aiup-core/skills/requirements in AI-Unified-Process/marketplace) into .claude/skills/requirements in your project. Claude Code loads it when a task matches its description.
How do I install Requirements in Codex?
Run `npx skills add AI-Unified-Process/marketplace --skill requirements -a codex`. Or copy the skill folder (aiup-core/skills/requirements in AI-Unified-Process/marketplace) into .agents/skills/requirements in your project. Codex loads it when a task matches its description.
Can I use 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 AI-Unified-Process/marketplace --skill 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/requirements, .gemini/skills/requirements, .github/skills/requirements and .opencode/skills/requirements in your project.
What does Requirements need to run?
SKILL.md names no scripts, command-line tools or credentials: Requirements is instructions for the agent only.
Does Requirements access the network?
SKILL.md names 1 domain. As links in the text: unifiedprocess.ai. This is read from the text; nothing was executed.
Is 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 Requirements use?
Requirements is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Requirements use?
About 2.5k tokens (SKILL.md is roughly 9.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.
What are the alternatives to Requirements?
Skills that share tags, products or a category with 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 Requirements?
AI-Unified-Process (a GitHub organization) maintains it in AI-Unified-Process/marketplace, which has 142 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on October 5, 2026.
Source: AI-Unified-Process/marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.