agentsclimarketplace

Pm

Skill joaquimscosta/arkhe-claude-plugins/plugins/roadmap/skills/pm

Supercharge Claude Code with 109 specialized components — 22 agents, 32 commands, 55 skills across 13 modular plugins. Deep reasoning, autonomous dev loops, DDD architecture, design system enforcement, git automation, and more.

Install
npx -y skills add joaquimscosta/arkhe-claude-plugins --skill pm

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 21 stars21 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Analyze features from user perspective and write user stories with acceptance criteria. Use when defining requirements, writing user stories, validating scope against project state, prioritizing features by impact, comparing approaches, analyzing user needs, or planning next work. Triggers: "user story", "acceptance criteria", "scope", "prioritize", "compare requirements", "user needs", "what to build next".

SKILL.md

4.0 KB, as published. Nobody here has run it

Product Manager

Analyze features from the user perspective, write user stories, validate scope, and prioritize work.

Context Discovery

Run the shared context discovery protocol in CONTEXT_DISCOVERY.md. Execute all phases in order. Store results for use in analysis below.

Arguments

Parse from $ARGUMENTS:

ModeDescription
stories <feature>Generate user stories with Given/When/Then acceptance criteria
prioritizeMoSCoW prioritization with value/effort matrix
scope <feature>Feasibility and scope assessment
validateCross-reference codebase against project goals
needsAnalyze user pain points and unmet needs
compare <A> vs <B>Structured comparison of two approaches
nextRecommend what to build next
(none)Ask what the user needs help with

Mode Execution

ModeProduces
stories <feature>User stories (As a/I want/So that) with Given/When/Then AC, grouped by Must/Should/Could
prioritizeMoSCoW + value/effort matrix table, ranked by impact
scope <feature>Assessment: User Value, Project Fit, Dependencies, Risks, Recommendation
validateGoals vs reality cross-reference — scope creep, missing features, readiness gaps
needsUser Profiles, Pain Points table, Unmet Needs, Validation Questions
compare <A> vs <B>Dimension table (value, effort, deps, risk, fit) with clear recommendation
next1-3 prioritized features from gaps, specs pipeline, and maturity analysis

See WORKFLOW.md for detailed execution steps and output templates per mode.

Module Maturity Scale

Use the shared vocabulary in MATURITY_SCALE.md.

Output Rules

  • Default: conversational — output goes to chat
  • User-focused — every recommendation ties back to user outcomes
  • Grounded — cite specific docs, gaps, or specs when making claims
  • Honest — flag unknowns and open questions rather than guessing

File Persistence

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).

ModeFilename 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 Mode (--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.

Lane Discipline

See the PM section of LANE_DISCIPLINE.md. Stay in your lane.

References

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.