product-roadmap-scoping
Skill1 starsChanged 21 days agoNo licenceView on GitHub
Scope a product ask (a client change request, a Monday or Slack item, or meeting notes) into a scoping doc that converts into a Jira Epic plus one discovery ticket. Uses Jobs To Be Done (JTBD) and the reviewing lead's scoping rules: treat the requester's proposed behavior as points to validate, not a spec; decide configuration vs feature flag; leave UX copy and button decisions to the UX owners; keep discovery async before any meeting; and end with next steps for designers, engineers and the PM. Use when asked to scope a request, write a scoping doc or epic description, turn meeting notes or a Monday item into an epic, break a client ask into jobs, decide config vs feature flag, or say what the next steps are for design. Not for writing stories (jira-ticket-writer) or a Confluence initiative brief (cohere-initiative-doc-writer).
In this repository30 other files it gives its agents.
- artifact-documentorSkill
- cohere-bug-triageSkill
- cohere-config-doc-writerSkill
- cohere-initiative-doc-writerSkill
- cohere-pcr-writerSkill
- cohere-rca-investigatorSkill
- communication-skill-typesSkill
- councilSkill
- crisp-test-plan-writerSkill
- dev-signoff-writerSkill
- eod-context-updaterSkill
- eod-updaterSkill
- framework-writerSkill
- grill-meSkill
- grooming-notes-updaterSkill
- jira-ticket-writerSkill
- marketing-psychologySkill
- market-researchSkill
- meet-a-userSkill
- mom-trackerSkill
- mom-writerSkill
- po-review-helperSkill
- ram-writing-styleSkill
- release-notes-writerSkill
- slack-mcp-troubleshooterSkill
- slack-question-writerSkill
- speed-reading-skillSkill
- test-plan-writerSkill
- the-humanizerSkill
- write-a-skillSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.