User Stories
phuryn/pm-skills
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking.
$ npx skills add Inebrio/Routerly --skill validation-protocol -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Inebrio/Routerly validation-protocol --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/Inebrio/Routerly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/validation-protocol .claude/skills/validation-protocol && 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 "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .claude/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocolType 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 Inebrio/Routerly --skill validation-protocol -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Inebrio/Routerly validation-protocol --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/validation-protocol .agents/skills/validation-protocol && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .agents/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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 Inebrio/Routerly --skill validation-protocol -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Inebrio/Routerly validation-protocol --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/validation-protocol .cursor/skills/validation-protocol && 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 "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .cursor/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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/Inebrio/Routerly.git --path .agents/skills/validation-protocol--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 Inebrio/Routerly --skill validation-protocol -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Inebrio/Routerly validation-protocol --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/validation-protocol .gemini/skills/validation-protocol && 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 "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .gemini/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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 Inebrio/Routerly validation-protocolInstalls 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 Inebrio/Routerly --skill validation-protocol -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/validation-protocol .github/skills/validation-protocol && 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 "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .github/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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 Inebrio/Routerly --skill validation-protocol -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Inebrio/Routerly validation-protocol --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/validation-protocol .opencode/skills/validation-protocol && 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 "validation-protocol" agent skill from https://github.com/Inebrio/Routerly/tree/develop/.agents/skills/validation-protocol into .opencode/skills/validation-protocol/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "validation-protocol", 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.
validation-protocolHow to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking.
Validation Protocol is an agent skill from Inebrio/Routerly. How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking. Use when verifying implemented work.
Its SKILL.md is about 630 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: Self-hosted LLM gateway that routes requests across AI providers (OpenAI, Anthropic, Gemini, Mistral, Ollama) using intelligent multi-policy scoring — including an LLM-native… The licence is AGPL-3.0.
Read from SKILL.md and the folder at commit bcf58f1. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Validation Protocol loads about 628 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 295 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.
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.
The full file from Inebrio/Routerly at commit bcf58f1, republished under its AGPL-3.0 licence (© Inebrio). 295 words, ~628 tokens.
.claude/skills/validation-protocol/SKILL.md (or your agent's skills folder).One file per story: <specs-root>/<feature>/03-validation/<story-id>.md.
Static. Read the story, the blueprint, and the diff. For each acceptance criterion and each edge case, find the code that satisfies it. A criterion with no code behind it is failed before anything runs.
Dynamic. Start the application with the exact command in the blueprint, in the story's own worktree, with its own environment sourced and its own ports. Then exercise every criterion the way a user would: browser for anything a user sees, real commands for the command line, real HTTP for the API. Reading the code is never a substitute for running it.
A verdict without evidence is an opinion. Every criterion carries what you actually observed:
Also check what nobody asked you to: the console for errors, the server log for stack traces, the other theme, the empty state, a second run of the same action.
Blocking — a criterion or edge case fails, the app does not start, data is lost or corrupted, a security or permission check is missing or wrong, a surface the story requires is absent, or the change breaks something that worked before.
Non-blocking — everything else: cosmetics, wording, a slow path, a refactor you would have done differently. Record it, do not gate on it.
# <story-id> — Validation
## Verdict
PASS or BLOCKED. One line of why.
## Criteria
| Id | Result | Evidence |
Every AC and EC from the story, none skipped, none invented.
## Blocking findings
### B1 — <what is wrong>
- Expected: <from the story, quoted>
- Observed: <what happened>
- Evidence: <command, output, or steps>
- Location: <file:line, when known>
## Non-blocking findings
One line each.
## Not verified
What you could not check and why. Never leave this implicit.You can run anything. You cannot change anything except this report. Do not route a fix through another tool, and never ask another agent to apply one for you: your value is that you did not write the code. A finding you fix is a finding nobody reviews.
© Inebrio, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/validation-protocol of Inebrio/Routerly.
Open the folder on GitHubat commit bcf58f1
Validation Protocol 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 |
|---|---|---|---|---|---|---|
| Validation Protocol this skillInebrio/Routerly | 100 | — | ~628 | Automated safety check: Pass | AGPL-3.0 | |
| User Storiesphuryn/pm-skills | 27k | — | ~748 | Automated safety check: Pass | MIT | |
| Job Storiesphuryn/pm-skills | 27k | — | ~743 | Automated safety check: Pass | MIT | |
| Create StoriesDonchitos/Claude-Code-Game-Studios | 26k | — | ~7.2k | Automated safety check: Pass | MIT | |
| Story ReadinessDonchitos/Claude-Code-Game-Studios | 26k | — | ~6.9k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence |
phuryn/pm-skills
Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria.
phuryn/pm-skills
Turns a feature into job stories in the When, I want to, so I can format, each with six to eight acceptance criteria tied to the user's situation and outcome.
Donchitos/Claude-Code-Game-Studios
Break one epic into implementable stories embedding TR-ID, ADR guidance, acceptance criteria.
Donchitos/Claude-Code-Game-Studios
Is a story implementation-ready?. An agent skill from Donchitos/Claude-Code-Game-Studios.
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.
sanity-io/sanity
Invoke FIRST, before creating, editing, or deleting components, stories, styles, CSS, themes, colors, or design tokens — anything that changes how the UI looks, no exceptions.
Inebrio/Routerly
Where documentation lives in this repository, how a page is structured, and what a change owes the docs.
Inebrio/Routerly
Run a Tier 1 or Tier 2 feature end to end — feature level, story level, parallelism, integration, and retrospective.
Inebrio/Routerly
Run one user story end to end in its own worktree, from claim to merge.
Inebrio/Routerly
Where tests live in this repository, how to run them, and what a story owes in coverage.
Inebrio/Routerly
Shape of a feature analysis document (00-analysis.md). An agent skill from Inebrio/Routerly.
Inebrio/Routerly
Shape of a story blueprint, the technical plan an orchestrator executes.
How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking. Validation Protocol is an agent skill from Inebrio/Routerly. How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking.
Validation Protocol fits situations like: verifying implemented work.
Run `npx skills add Inebrio/Routerly --skill validation-protocol -a claude-code`. Or copy the skill folder (.agents/skills/validation-protocol in Inebrio/Routerly) into .claude/skills/validation-protocol in your project. Claude Code loads it when a task matches its description.
Run `npx skills add Inebrio/Routerly --skill validation-protocol -a codex`. Or copy the skill folder (.agents/skills/validation-protocol in Inebrio/Routerly) into .agents/skills/validation-protocol in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Inebrio/Routerly --skill validation-protocol -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/validation-protocol, .gemini/skills/validation-protocol, .github/skills/validation-protocol and .opencode/skills/validation-protocol in your project.
SKILL.md names no scripts, command-line tools or credentials: Validation Protocol is instructions for the agent only.
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.
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.
Validation Protocol is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 628 tokens (SKILL.md is roughly 2.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Validation Protocol: User Stories (phuryn/pm-skills, 27k stars), Job Stories (phuryn/pm-skills, 27k stars), Create Stories (Donchitos/Claude-Code-Game-Studios, 26k stars) and Story Readiness (Donchitos/Claude-Code-Game-Studios, 26k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Inebrio (a GitHub organization) maintains it in Inebrio/Routerly, which has 100 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.
Source: Inebrio/Routerly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.