requirements
Skill3 starsChanged 7 months agoMITView on GitHub
Transform a raw idea into a structured PRD (Product Requirements Document). Dispatches Grace (product-manager) to elicit, structure, and validate requirements.
16 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 versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- 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
- jvalin17/agent-toolkit★ 2same name
6 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 repository21 other files it gives its agents.
- skills/setup/templates/AGENTS.mdAGENTS.md
- skills/setup/templates/CLAUDE.mdCLAUDE.md
- add-supervisorSkill
- architectureSkill
- core-loopSkill
- doSkill
- implementationSkill
- investigateSkill
- manifestoSkill
- planSkill
- productSkill
- qualitySkill
- researchSkill
- reviewSkill
- setupSkill
- specificationSkill
- specSkill
- subagents-disciplineSkill
- tasksSkill
- updateSkill
- workflowSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 8 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Create a structured Product Requirements Document from a raw idea or concept.
- Distinctive: line 14
If the user provides $ARGUMENTS, analyze them for:
- Very specific: line 21
No strict prerequisites — this is typically the first skill in Stage 1 after /manifesto.
- Very specific: line 23
If a manifesto exists at docs/MANIFESTO.md:
- Distinctive: line 24
Read it for context — the PRD should align with the manifesto's principles and governing laws.
- Distinctive: line 29
Ask the user if they have any existing documents about the idea (briefs, notes, sketches, competitive analysis)
- Distinctive: line 30
If documents exist, read them and include their paths in the dispatch prompt
- Distinctive: line 33
Ask the user where the PRD should be saved
- Distinctive: line 35
Ensure the parent directory exists (create if needed)
- Distinctive: line 50
Verify the PRD file was created at the agreed path
“Common” is measured: kept by at least 6 in 10 of the 12 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
Requirements
Create a structured Product Requirements Document from a raw idea or concept.
<on-init>
If the user provides $ARGUMENTS, analyze them for:
- A raw idea or concept description
- An existing PRD path to review/iterate
- Reference documents (briefs, notes, competitive analysis)
</on-init><on-check>
No strict prerequisites — this is typically the first skill in Stage 1 after `/manifesto`.If a manifesto exists at docs/MANIFESTO.md:
- Read it for context — the PRD should align with the manifesto's principles and governing laws.
</on-check>
<on-execute>
1. **Gather context:**
- Ask the user if they have any existing documents about the idea (briefs, notes, sketches, competitive analysis)
- If documents exist, read them and include their paths in the dispatch prompt- Define output location:
- Ask the user where the PRD should be saved
- Suggest default:
docs/prd/PRD-{feature-name-kebab-case}.md - Ensure the parent directory exists (create if needed)
Dispatch using exactly these parameters — no more, no less:
Agent( subagent_type="product-manager", prompt="Create a PRD for the requested feature/product. Save the PRD to {agreed_path}. Context: {user_idea}. Reference documents: {doc_paths_if_any}" )Do NOT add extra parameters unless the user explicitly requests it.
</on-execute>
<on-complete>
1. Verify the PRD file was created at the agreed path
2. Show the user the status from Grace's report (DRAFT or APPROVED)
</on-complete><on-complete if="status=DRAFT">
Inform the user they can continue iterating with Grace by running `/requirements` again or editing directly.
</on-complete><on-next>
Recommend proceeding with `/architecture` referencing the PRD path.
</on-next>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.