Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agent skill
Awesome Requirements Writer
by muchengracedriver in muchengracedriver/awesome-requirements-writer
A skill your agent uses when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics…
Install Awesome Requirements Writer
$ npx skills add muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install muchengracedriver/awesome-requirements-writer awesome-requirements-writer --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/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .claude/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .claude/skills/awesome-requirements-writer && 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 "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .claude/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writerType 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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install muchengracedriver/awesome-requirements-writer awesome-requirements-writer --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .agents/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .agents/skills/awesome-requirements-writer && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .agents/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install muchengracedriver/awesome-requirements-writer awesome-requirements-writer --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .cursor/skills/awesome-requirements-writer && 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 "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .cursor/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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/muchengracedriver/awesome-requirements-writer.git --path adapters/codex/.agents/skills/awesome-requirements-writer--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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install muchengracedriver/awesome-requirements-writer awesome-requirements-writer --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .gemini/skills/awesome-requirements-writer && 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 "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .gemini/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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 muchengracedriver/awesome-requirements-writer awesome-requirements-writerInstalls 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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .github/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .github/skills/awesome-requirements-writer && 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 "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .github/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install muchengracedriver/awesome-requirements-writer awesome-requirements-writer --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/muchengracedriver/awesome-requirements-writer.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/adapters/codex/.agents/skills/awesome-requirements-writer .opencode/skills/awesome-requirements-writer && 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 "awesome-requirements-writer" agent skill from https://github.com/muchengracedriver/awesome-requirements-writer/tree/main/adapters/codex/.agents/skills/awesome-requirements-writer into .opencode/skills/awesome-requirements-writer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "awesome-requirements-writer", 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
awesome-requirements-writer- GitHub stars
- 104
- Token cost
- ~1.1k tokens
- SKILL.md length
- 469 words
- Files
- 4 (incl. references)
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics…
- Works in 9 steps: Identify the item under requirement:… → Extract stakeholder intent, system… → Determine if the content is… → …
- Decomposing technical product requirements for product systems
- SKILL.md covers Overview, Requirement Principles, Workflow and Requirement Shape, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Awesome Requirements Writer is an agent skill from muchengracedriver/awesome-requirements-writer. Use when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics, interfaces, or specifications, engineering change requests. Helps turn engineering know-how, notes, standards, customer nots and test expectations from conversational casual writing into clear, atomic, measurable, traceable，unambiguous requirements with acceptance criteria.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `references/automotive-context.md`, `references/requirement-patterns-en.md` and `references/requirement-patterns-zh.md`).
It sits in Product & Project Management, covering PRD writing and User stories. The repository describes itself as: Turn engineering intent into requirements that can be designed, reviewed, implemented, verified, and traced. Prefer precise requirements over broad product prose, and flag… The licence is MIT.
When your agent uses it
- Decomposing technical product requirements for product systems
- Micro-processors
- Engineering change requests
Example prompts
- “/awesome-requirements-writer”
Workflow steps
9 steps, taken from the first numbered list in SKILL.md.
- Identify the item under requirement: product system, subsystem, feature, variant, and lifecycle phase.
- Extract stakeholder intent, system behavior, constraints, interfaces and validation expectations.
- Determine if the content is "information" or "requirement". Information is the content which is rationale, examples, diagrams, repeated…
- Classify requirements by type: functional (direct related to a specific feature or design), non-functional (performance, efficiency…
- Draft atomic "shall" statements with a single subject, condition, behavior, measurable target, operating bounds, and verification path.
- Add metadata: type(information/requirement), ID , content body and acceptance criteria.
- List all functinal requirements and related information in one chapter, while all non-functional requirements in another.
- In a new chapter make a table of all static variables and its value. If no value is given, type TBD.
- Audit the result for ambiguity, hidden design decisions, unverifiable claims, duplicate requirements, conflicting limits, missing fault…
What it can do on your machine
Read from SKILL.md and the folder at commit 1584110. 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
Awesome Requirements Writer loads about 1.1k tokens when it runs, and up to ~3.8k if it reads all its reference files. Until then it costs about 119 tokens; SKILL.md has 469 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 muchengracedriver/awesome-requirements-writer at commit 1584110, republished under its MIT licence (© muchengracedriver). 469 words, ~1,053 tokens.
Download SKILL.mdSave it as
.claude/skills/awesome-requirements-writer/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.- name
- awesome-requirements-writer
- description
- Use when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics, interfaces, or specifications, engineering change requests. Helps turn engineering know-how, notes, standards, customer nots and test expectations from conversational casual writing into clear, atomic, measurable, traceable，unambiguous requirements with acceptance criteria.
Awesome Requirements Writer
Overview
Turn engineering intent into requirements that can be designed, reviewed, implemented, verified, and traced. Prefer precise requirements over broad product prose, and flag missing engineering inputs instead of inventing thresholds.
Requirement Principles
A strong requirement is:
- Clean and direct: include only necessary normative or definitional content in the requirement statement, no rationale content.
- Unambiguous: avoid subjective terms, vague modifiers, and implicit Boolean logic; use explicit
AND/ORfor compound conditions. - Atomic: assign one requirement ID to one indivisible obligation, condition, or behavior.
- Positively defined: describe when the system shall perform the required behavior; avoid defining behavior by negating the opposite condition.
- No magic numbers: all static numbers shall be expressed by a static variable name with a table of all stactic variables with its real engineering value.
- Directly testable: make required inputs controllable and required outputs observable by the intended verification method.
- Separate from information: keep rationale, examples, diagrams, repeated context, and verification notes outside the normative requirement text.
- Traceable: link upward to source, system, safety, customer, regulatory, or design-constraint needs, and sideways or downward to test and design evidence.
Workflow
- Identify the item under requirement: product system, subsystem, feature, variant, and lifecycle phase.
- Extract stakeholder intent, system behavior, constraints, interfaces and validation expectations.
- Determine if the content is "information" or "requirement". Information is the content which is rationale, examples, diagrams, repeated else-defined requirements, and verification notes outside the normative requirement text.
- Classify requirements by type: functional (direct related to a specific feature or design), non-functional (performance, efficiency, expansion etc).
- Draft atomic "shall" statements with a single subject, condition, behavior, measurable target, operating bounds, and verification path.
- Add metadata: type(information/requirement), ID , content body and acceptance criteria.
- List all functinal requirements and related information in one chapter, while all non-functional requirements in another.
- In a new chapter make a table of all static variables and its value. If no value is given, type TBD.
- Audit the result for ambiguity, hidden design decisions, unverifiable claims, duplicate requirements, conflicting limits, missing fault behavior, and missing open questions.
Show full SKILL.md (122 more words)Show less
Requirement Shape
Use this format unless the user asks for another one:
for information:
- [Info]
<information body>
for requirement:
- [Req
<ID>]<requirement body>|<acceptance criteria>
Output Rules
- Match the user's language. If the user writes in Chinese, draft requirements in Chinese unless they request English.
- If source notes are incomplete, produce the best draft plus a short "Open Questions" list.
- If multiple interpretations are plausible, state the assumption used.
- Generate output as a .md file.
Project-Specific Guidelines
User can add their customized project-spicific guidelines in this section.
References
- Read
references/requirement-patterns-en.mdwhen drafting many requirements or converting informal engineering notes in English. - Read
references/requirement-patterns-zh.mdwhen drafting many requirements or converting informal engineering notes in Chinese. - Read
references/automotive-context.mdwhen the work involves automotive engineering.
© muchengracedriver, 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 3 other files (references) in adapters/codex/.agents/skills/awesome-requirements-writer of muchengracedriver/awesome-requirements-writer.
- SKILL.md
- references/automotive-context.md
- references/requirement-patterns-en.md
- references/requirement-patterns-zh.md
Open the folder on GitHubat commit 1584110
Compare with similar skills
Awesome Requirements Writer 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 |
|---|---|---|---|---|---|---|
| Awesome Requirements Writer this skillmuchengracedriver/awesome-requirements-writer | 104 | — | ~1.1k | 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 | 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 muchengracedriver/awesome-requirements-writer
Awesome Requirements Writer
muchengracedriver/awesome-requirements-writer
A skill your agent uses when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics…
Related
Categories
Questions about Awesome Requirements Writer
What does Awesome Requirements Writer do?
A skill your agent uses when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics…. Awesome Requirements Writer is an agent skill from muchengracedriver/awesome-requirements-writer. Use when drafting, rewriting, reviewing, or decomposing technical product requirements for product systems, micro-processors, sensors, actuators, or functions, diagnostics, interfaces, or specifications, engineering change requests.
When should I use Awesome Requirements Writer?
Awesome Requirements Writer fits situations like: decomposing technical product requirements for product systems; micro-processors; engineering change requests.
How do I install Awesome Requirements Writer in Claude Code?
Run `npx skills add muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a claude-code`. Or copy the skill folder (adapters/codex/.agents/skills/awesome-requirements-writer in muchengracedriver/awesome-requirements-writer) into .claude/skills/awesome-requirements-writer in your project. Claude Code loads it when a task matches its description.
How do I install Awesome Requirements Writer in Codex?
Run `npx skills add muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a codex`. Or copy the skill folder (adapters/codex/.agents/skills/awesome-requirements-writer in muchengracedriver/awesome-requirements-writer) into .agents/skills/awesome-requirements-writer in your project. Codex loads it when a task matches its description.
Can I use Awesome Requirements Writer 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 muchengracedriver/awesome-requirements-writer --skill awesome-requirements-writer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/awesome-requirements-writer, .gemini/skills/awesome-requirements-writer, .github/skills/awesome-requirements-writer and .opencode/skills/awesome-requirements-writer in your project.
What does Awesome Requirements Writer need to run?
SKILL.md names no scripts, command-line tools or credentials: Awesome Requirements Writer is instructions for the agent only.
Does Awesome Requirements Writer 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 Awesome Requirements Writer 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 Awesome Requirements Writer use?
Awesome Requirements Writer 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 Awesome Requirements Writer use?
About 1.1k tokens (SKILL.md is roughly 4.2k 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 2.8k tokens, read only when the agent opens those files.
What are the alternatives to Awesome Requirements Writer?
Skills that share tags, products or a category with Awesome Requirements Writer: 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 Awesome Requirements Writer?
muchengracedriver (a GitHub user) maintains it in muchengracedriver/awesome-requirements-writer, which has 104 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on June 20, 2026.
Source: muchengracedriver/awesome-requirements-writer on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.