Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Techniques for writing clear product specifications, user stories, and acceptance criteria.
Install Specification Techniques
$ npx skills add slgoodrich/agents --skill specification-techniques -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install slgoodrich/agents specification-techniques --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/slgoodrich/agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .claude/skills/specification-techniques && 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 "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .claude/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniquesType 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 slgoodrich/agents --skill specification-techniques -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install slgoodrich/agents specification-techniques --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/slgoodrich/agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .agents/skills/specification-techniques && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .agents/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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 slgoodrich/agents --skill specification-techniques -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install slgoodrich/agents specification-techniques --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/slgoodrich/agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .cursor/skills/specification-techniques && 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 "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .cursor/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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/slgoodrich/agents.git --path plugins/ai-pm-copilot/skills/specification-techniques--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 slgoodrich/agents --skill specification-techniques -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install slgoodrich/agents specification-techniques --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/slgoodrich/agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .gemini/skills/specification-techniques && 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 "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .gemini/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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 slgoodrich/agents specification-techniquesInstalls 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 slgoodrich/agents --skill specification-techniques -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/slgoodrich/agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .github/skills/specification-techniques && 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 "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .github/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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 slgoodrich/agents --skill specification-techniques -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install slgoodrich/agents specification-techniques --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/slgoodrich/agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/ai-pm-copilot/skills/specification-techniques .opencode/skills/specification-techniques && 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 "specification-techniques" agent skill from https://github.com/slgoodrich/agents/tree/main/plugins/ai-pm-copilot/skills/specification-techniques into .opencode/skills/specification-techniques/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specification-techniques", 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
specification-techniques- GitHub stars
- 138
- Token cost
- ~3.3k tokens
- SKILL.md length
- 1,005 words
- Files
- 11 (incl. references, assets)
- Skills in repo
- 19
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Techniques for writing clear product specifications, user stories, and acceptance criteria.
- Works in 2 steps: Solution Masquerading as Problem → Missing Acceptance Criteria
- Defining feature requirements
- SKILL.md covers Overview, When to Use This Skill, Product Requirements Documents… and User Stories, plus 8 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Specification Techniques is an agent skill from slgoodrich/agents. Techniques for writing clear product specifications, user stories, and acceptance criteria. Use when defining feature requirements, writing user stories, creating acceptance criteria, or reducing spec ambiguity. Trigger on: 'write a spec', 'acceptance criteria for this feature', 'user story format', 'define requirements', 'Given-When-Then'.
Its SKILL.md is about 3.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files and assets (for example `assets/edge-case-checklist.md`, `assets/job-story-template.md` and `assets/non-functional-requirements-template.md`).
It sits in Product & Project Management, covering User stories and PRD writing. The repository describes itself as: AI PM Workflows for Claude Code.
When your agent uses it
- Defining feature requirements
- Writing user stories
- Creating acceptance criteria
- Reducing spec ambiguity
Example prompts
- “write a spec”
- “acceptance criteria for this feature”
- “user story format”
- “/specification-techniques”
Workflow steps
2 steps, taken from the step headings in SKILL.md.
- Solution Masquerading as Problem
- Missing Acceptance Criteria
What it can do on your machine
Read from SKILL.md and the folder at commit 3b5835b. 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
Specification Techniques loads about 3.3k tokens when it runs, and up to ~26k if it reads all its reference files. Until then it costs about 92 tokens; SKILL.md has 1,005 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 1,005 words (~3,256 tokens).
“Structured methods for translating product vision into clear, actionable requirements that align teams, reduce ambiguity, and enable successful execution.”
- name
- specification-techniques
Files
SKILL.md and 10 other files (references, assets) in plugins/ai-pm-copilot/skills/specification-techniques of slgoodrich/agents.
- SKILL.md
- assets/edge-case-checklist.md
- assets/job-story-template.md
- assets/non-functional-requirements-template.md
- assets/prd-structure-template.md
- assets/use-case-template.md
- assets/user-story-template.md
- references/acceptance-criteria-guide.md
- references/specification-anti-patterns.md
- references/specification-best-practices.md
- references/user-story-writing-guide.md
Open the folder on GitHubat commit 3b5835b
Compare with similar skills
Specification Techniques 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 |
|---|---|---|---|---|---|---|
| Specification Techniques this skillslgoodrich/agents | 138 | — | ~3.3k | Automated safety check: Pass | Custom licence | |
| 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 | |
| Ralphjulianromli/opencode-template | 144 | 1 repos | ~1.1k | Automated safety check: Pass | None |
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.
Ralph
julianromli/opencode-template
Autonomous agent loop for completing features. An agent skill from julianromli/opencode-template.
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).
More from slgoodrich/agents
All 19 skills in this repoCompetitive Analysis Templates
slgoodrich/agents
Master competitive analysis templates including competitor deep-dives, battle cards, feature comparison matrices, and win/loss analysis.
Go To Market Playbooks
slgoodrich/agents
GTM strategies, product positioning, messaging, and launch planning.
Interview Frameworks
slgoodrich/agents
Frameworks for user interviews, question design, and qualitative research.
Launch Planning Frameworks
slgoodrich/agents
Launch planning frameworks including tiered launches, timelines, checklists, and go/no-go decisions.
Market Sizing Frameworks
slgoodrich/agents
TAM/SAM/SOM calculations and market sizing methodologies. An agent skill from slgoodrich/agents.
Prd Templates
slgoodrich/agents
Master PRD templates including problem statements, success metrics, requirements, user stories, and technical considerations.
Related
Categories
Questions about Specification Techniques
What does Specification Techniques do?
Techniques for writing clear product specifications, user stories, and acceptance criteria. Specification Techniques is an agent skill from slgoodrich/agents. Techniques for writing clear product specifications, user stories, and acceptance criteria.
When should I use Specification Techniques?
Specification Techniques fits situations like: defining feature requirements; writing user stories; creating acceptance criteria; reducing spec ambiguity.
How do I install Specification Techniques in Claude Code?
Run `npx skills add slgoodrich/agents --skill specification-techniques -a claude-code`. Or copy the skill folder (plugins/ai-pm-copilot/skills/specification-techniques in slgoodrich/agents) into .claude/skills/specification-techniques in your project. Claude Code loads it when a task matches its description.
How do I install Specification Techniques in Codex?
Run `npx skills add slgoodrich/agents --skill specification-techniques -a codex`. Or copy the skill folder (plugins/ai-pm-copilot/skills/specification-techniques in slgoodrich/agents) into .agents/skills/specification-techniques in your project. Codex loads it when a task matches its description.
Can I use Specification Techniques 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 slgoodrich/agents --skill specification-techniques -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specification-techniques, .gemini/skills/specification-techniques, .github/skills/specification-techniques and .opencode/skills/specification-techniques in your project.
What does Specification Techniques need to run?
SKILL.md names no scripts, command-line tools or credentials: Specification Techniques is instructions for the agent only.
Does Specification Techniques 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 Specification Techniques 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 Specification Techniques use?
Specification Techniques has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Specification Techniques use?
About 3.3k tokens (SKILL.md is roughly 13k 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 23k tokens, read only when the agent opens those files.
What are the alternatives to Specification Techniques?
Skills that share tags, products or a category with Specification Techniques: 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 Specification Techniques?
slgoodrich (a GitHub user) maintains it in slgoodrich/agents, which has 138 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on April 10, 2026.
Source: slgoodrich/agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.