From roadmap
Generates user stories with acceptance criteria, prioritizes features by impact, validates scope against codebase, analyzes user needs, and plans next work.
npx claudepluginhub joaquimscosta/arkhe-claude-plugins --plugin roadmapThis skill is limited to using the following tools:
Analyze features from the user perspective, write user stories, validate scope, and prioritize work.
Defines product requirements including PRDs, user stories, acceptance criteria; gathers needs, prioritizes features, scopes MVPs, and makes trade-offs. Translates business goals into engineering specs.
Generates product feature specs with user stories, testable acceptance criteria, scope IN/OUT, priority, success metrics, and vertical slices for multi-layer features. Use for business requirements and dev handoffs.
Generates prioritized user stories with Given/When/Then acceptance criteria, story point estimates, epic story mapping, and MoSCoW prioritization for sprint planning and backlogs.
Share bugs, ideas, or general feedback.
Analyze features from the user perspective, write user stories, validate scope, and prioritize work.
Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order. Store results for use in analysis below.
Parse from $ARGUMENTS:
| Mode | Description |
|---|---|
stories <feature> | Generate user stories with Given/When/Then acceptance criteria |
prioritize | MoSCoW prioritization with value/effort matrix |
scope <feature> | Feasibility and scope assessment |
validate | Cross-reference codebase against project goals |
needs | Analyze user pain points and unmet needs |
compare <A> vs <B> | Structured comparison of two approaches |
next | Recommend what to build next |
| (none) | Ask what the user needs help with |
| Mode | Produces |
|---|---|
stories <feature> | User stories (As a/I want/So that) with Given/When/Then AC, grouped by Must/Should/Could |
prioritize | MoSCoW + value/effort matrix table, ranked by impact |
scope <feature> | Assessment: User Value, Project Fit, Dependencies, Risks, Recommendation |
validate | Goals vs reality cross-reference — scope creep, missing features, readiness gaps |
needs | User Profiles, Pain Points table, Unmet Needs, Validation Questions |
compare <A> vs <B> | Dimension table (value, effort, deps, risk, fit) with clear recommendation |
next | 1-3 prioritized features from gaps, specs pipeline, and maturity analysis |
See WORKFLOW.md for detailed execution steps and output templates per mode.
Use the shared vocabulary in MATURITY_SCALE.md.
After producing the analysis, ask the user:
Save this analysis to
{output_dir}/requirements/{filename}.md?
Where {output_dir} comes from .arkhe.yaml (default: arkhe/roadmap).
| Mode | Filename Pattern |
|---|---|
stories <feature> | {feature-slug}-stories.md |
prioritize | {YYYY-MM-DD}-priorities.md |
scope <feature> | scope-{feature-slug}.md |
validate | {YYYY-MM-DD}-validation.md |
needs | {YYYY-MM-DD}-needs.md |
compare <A> vs <B> | {a-slug}-vs-{b-slug}.md |
next | {YYYY-MM-DD}-next.md |
--deep)When $ARGUMENTS contains --deep, run the full multi-agent pipeline instead of conversational analysis. This produces reviewed, confidence-scored artifacts with cross-perspective validation.
See WORKFLOW.md § Deep Pipeline for the 5-phase execution protocol.
Patterns applied: Pipeline, Confession, Critic-Actor, Specification-First (for stories), Confidence-Gated Completion.
See the PM section of LANE_DISCIPLINE.md. Stay in your lane.