User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
Skill to define requirements effciently as a product manager.
Install Defining Requirements
$ npx skills add archibate/dotfiles-opencode --skill defining-requirements -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install archibate/dotfiles-opencode defining-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/archibate/dotfiles-opencode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/defining-requirements .claude/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .claude/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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/archibate/dotfiles-opencode/tree/main/skills/defining-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 archibate/dotfiles-opencode --skill defining-requirements -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install archibate/dotfiles-opencode defining-requirements --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archibate/dotfiles-opencode.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/defining-requirements .agents/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .agents/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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 archibate/dotfiles-opencode --skill defining-requirements -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install archibate/dotfiles-opencode defining-requirements --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archibate/dotfiles-opencode.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/defining-requirements .cursor/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .cursor/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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/archibate/dotfiles-opencode.git --path skills/defining-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 archibate/dotfiles-opencode --skill defining-requirements -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install archibate/dotfiles-opencode defining-requirements --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archibate/dotfiles-opencode.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/defining-requirements .gemini/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .gemini/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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 archibate/dotfiles-opencode defining-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 archibate/dotfiles-opencode --skill defining-requirements -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/archibate/dotfiles-opencode.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/defining-requirements .github/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .github/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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 archibate/dotfiles-opencode --skill defining-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 archibate/dotfiles-opencode defining-requirements --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archibate/dotfiles-opencode.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/defining-requirements .opencode/skills/defining-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 "defining-requirements" agent skill from https://github.com/archibate/dotfiles-opencode/tree/main/skills/defining-requirements into .opencode/skills/defining-requirements/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "defining-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
defining-requirements- GitHub stars
- 108
- Token cost
- ~1.8k tokens
- SKILL.md length
- 965 words
- Files
- 1
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- None found
At a glance
Skill to define requirements effciently as a product manager.
- Works in 10 steps: Shift from “Documentation” to… → Use User Stories, Not Just Feature Lists → Write Acceptance Criteria in… → …
- Tasks that involve User stories
- SKILL.md covers 1. Shift from “Documentation”…, 2. Use User Stories, Not Just…, 3. Write Acceptance Criteria… and 4. Use Story Mapping to See…, plus 7 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Defining Requirements is an agent skill from archibate/dotfiles-opencode. Skill to define requirements effciently as a product manager.
Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories. The repository describes itself as: Archibate's personal configuration for OpenCode.
When your agent uses it
- Tasks that involve User stories
Example prompts
- “/defining-requirements”
Workflow steps
10 steps, taken from the step headings in SKILL.md.
- Shift from “Documentation” to “Continuous Discovery”
- Use User Stories, Not Just Feature Lists
- Write Acceptance Criteria in “Given‑When‑Then” (Gherkin)
- Use Story Mapping to See the Big Picture
- Consider “Job Stories” for JTBD Practitioners
- Prototype + Annotate (The “Spec-Lite” Approach)
- Frame Requirements as Hypotheses (Lean Startup)
- Collaborate with the “Three Amigos”
- Keep a Living Glossary / Domain Language
- Avoid Common Pitfalls
What it can do on your machine
Read from SKILL.md and the folder at commit 46b6b23. 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 (its code samples are gherkin).
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
Defining Requirements loads about 1.8k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 965 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
Without a licence we can't republish the file, so here is its outline and opening line. It has 965 words (~1,832 tokens).
“Defining requirements is one of the most critical—and misunderstood—responsibilities of a product manager. The traditional "hand over a 50-page PRD and disappear" approach is broken. Modern product managers define requirements collaboratively, iteratively, and with a focus on outcomes, not just…”
- name
- defining-requirements
Files
Just SKILL.md in skills/defining-requirements of archibate/dotfiles-opencode.
Open the folder on GitHubat commit 46b6b23
Compare with similar skills
Defining 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 |
|---|---|---|---|---|---|---|
| Defining Requirements this skillarchibate/dotfiles-opencode | 108 | — | ~1.8k | Automated safety check: Pass | None | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from archibate/dotfiles-opencode
All 34 skills in this repoGlm Vision
archibate/dotfiles-opencode
This skill should be used when the user sends an image and asks to "analyze this image", "describe this picture", "what's in this image", or any request requiring visual understanding of images.
Pueue
archibate/dotfiles-opencode
This skill should be used before running non-interactive long-running tasks, computation intensive tasks, background tasks, or needs guidance on the pueue CLI tool usage.
Bilibili API
archibate/dotfiles-opencode
This skill should be used when the user asks to "use bilibili API", "download bilibili video", "get bilibili user info", "list bilibili favorites", "send bilibili danmaku", "upload video to…
Show Image
archibate/dotfiles-opencode
Show images in terminal using the Kitty image protocol. An agent skill from archibate/dotfiles-opencode.
Show Image
archibate/dotfiles-opencode
Show images in terminal using the Kitty image protocol. An agent skill from archibate/dotfiles-opencode.
Tmux
archibate/dotfiles-opencode
Remote control tmux sessions for interactive CLIs (python, gdb, etc.) by sending keystrokes and scraping pane output.
Related
Categories
Questions about Defining Requirements
What does Defining Requirements do?
Skill to define requirements effciently as a product manager. Defining Requirements is an agent skill from archibate/dotfiles-opencode. Skill to define requirements effciently as a product manager.
When should I use Defining Requirements?
Defining Requirements fits situations like: tasks that involve User stories.
How do I install Defining Requirements in Claude Code?
Run `npx skills add archibate/dotfiles-opencode --skill defining-requirements -a claude-code`. Or copy the skill folder (skills/defining-requirements in archibate/dotfiles-opencode) into .claude/skills/defining-requirements in your project. Claude Code loads it when a task matches its description.
How do I install Defining Requirements in Codex?
Run `npx skills add archibate/dotfiles-opencode --skill defining-requirements -a codex`. Or copy the skill folder (skills/defining-requirements in archibate/dotfiles-opencode) into .agents/skills/defining-requirements in your project. Codex loads it when a task matches its description.
Can I use Defining 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 archibate/dotfiles-opencode --skill defining-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/defining-requirements, .gemini/skills/defining-requirements, .github/skills/defining-requirements and .opencode/skills/defining-requirements in your project.
What does Defining Requirements need to run?
SKILL.md names no scripts, command-line tools or credentials: Defining Requirements is instructions for the agent only.
Does Defining 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 Defining 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 Defining Requirements use?
No licence was found for Defining Requirements or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Defining Requirements use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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 Defining Requirements?
Skills that share tags, products or a category with Defining Requirements: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Defining Requirements?
archibate (a GitHub user) maintains it in archibate/dotfiles-opencode, which has 108 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on April 29, 2026.
Source: archibate/dotfiles-opencode on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.