requirements
Skill2 starsChanged 34 days agoMITView on GitHub
Craft requirements phase - produce the product-requirements doc via the requirements-writer agent; returns decision candidates for the ADR conversation.
17 other projects use a version of this.
Adopted by
Most recently taken up by
- Jakeschincariol/whale-skilltheir own version, first seen Nov 8, 2026
- marcusbelz/di2-starter-kittheir own version, first seen Oct 31, 2026
- owainlewis/blueprinttheir own version, first seen Oct 13, 2026
- jvalin17/agent-toolkittheir own version, first seen Oct 12, 2026
- ngthluu/my-ba-skillstheir own version, first seen Oct 9, 2026
- rizsotto/Beartheir own version, first seen Oct 8, 2026
Used with
Projects with it also use agent-browser.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
VercelSkillagent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Also in 3 projects that use this
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- rizsotto/Bear★ 6.5ksame name
- owainlewis/blueprint★ 423same name
- ptsilivis/autonomousguy★ 33same name
- Jakeschincariol/whale-skill★ 15same name
- aborroy/aiup-alfresco★ 14same name
- dewil/ai-toolkit★ 9same name
- dewil/claude-toolkit★ 9same name
- saitarrun/Devforge-ai★ 4same name
- digitaldreams/tuhin★ 3same name
- websublime/mister-anderson★ 3same name
7 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- architectureSkill
- decisionsSkill
- designSkill
- documentationSkill
- impact-triageSkill
- implementationSkill
- initSkill
- integrateSkill
- lessonsSkill
- metricsSkill
- planningSkill
- promote-configSkill
- proposeSkill
- pruneSkill
- refactoringSkill
- reviewSkill
- runSkill
- tuneSkill
- validationSkill
- workspaceSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 13 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
When it returns: READ THE DOC (not the agent's exploration).
“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
craft:requirements
Preamble (always runs — non-overridable)
manifest-lint.shmust pass (skip if the orchestrator already ran it this turn); read manifest. Standalone: scope defaults to the current branch vs the default branch; establish global-context preconditions against the current checkout root.- Probe: requirements docs directory (
paths.requirements, elsedocs/requirements/, create if absent); repo's own requirements template, else"${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/templates/requirements.md".
Procedure (default body — a manifest override: replaces everything below)
- Spawn craft:requirements-writer with: the resolved brief (and any source
PRD/spec path); the absolute working directory; the output path
<requirements-dir>/<slug>.md; the template; the commit messagedocs(requirements): <slug>; the manifest's global + requirements-phasecontext:files verbatim. - When it returns: READ THE DOC (not the agent's exploration). Sanity-check it against the brief; verify the commit exists and the decision-candidates were returned.
- The
designphase consumes the producedrequirementsartifact; record the outcome in the run record. - Dead agent → respawn fresh from the brief + whatever the doc already contains.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.