axos-pm

Plugin axos-pm from marketplace axos-pm in BriannavLy/pm-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (23)

• ab-test-analysis

  Assess split test results for statistical validity before interpreting them, then give a ship, extend, or stop recommendation with the reasoning shown. Use when handed experiment results, or when asked how large a sample is needed before a test starts.

• analyze-feature-requests

  Turn a pile of inbound feature requests into themes, with the underlying need separated from the proposed solution and strategic fit assessed per theme. Use when handed a batch of requests from sales, support, or a customer advisory channel.

• cohort-analysis

  Analyse retention, adoption, or engagement by cohort, and separate a real change in behaviour from a change in who joined. Use when a headline metric moved and the cause is not obvious, or when assessing whether a change made things better for new customers.

• competitive-analysis

  Competitive analysis templates and positioning method: landscape mapping, SWOT, Five Forces. April Dunford positioning, battle cards. Load for any competitor or positioning work.

• customer-journey-map

  Map the stages a customer moves through for a specific job, with touchpoints, what they are trying to achieve, where it goes wrong, and which moments carry disproportionate weight. Use when a problem is suspected to live between steps rather than inside one screen.

• discovery-run

  Orchestrate a multi stage product discovery run end to end, creating a resumable run directory and sequencing discovery-stage across the stages the person wants. Use when starting or resuming discovery on an initiative, or when taking a raw idea through to an approved discovery document.

• discovery-stage

  Run one stage of the product discovery framework against the person's raw input, returning a strengthened statement, enriched analysis, assumptions to validate, and follow up questions. Use when working through a single discovery dimension, or when revising a stage after the person answers questions

• evidence-trail

  How to label evidence and record assumptions, review findings, and verification for a PM deliverable. Load whenever writing to evidence/ or when a deliverable makes claims that need provenance.

• go-to-market-playbooks

  GTM strategy and launch execution: launch tiers, channel selection, beta programs, messaging hierarchy. Load for launch or GTM planning.

• market-sizing

  Market sizing method: TAM/SAM/SOM, top-down vs bottom-up, sanity checks. Load when estimating market size or opportunity.

• opportunity-solution-tree

  Build a tree from a desired outcome through customer opportunities to candidate solutions and the experiments that would test them. Use when a discovery effort has research findings but no structured path from outcome to what to build.

• pbi-writer

  Write a product backlog item with a description and acceptance criteria in Gherkin from a design and its requirement, then create it in Azure DevOps after a preview. Use for writing a PBI, creating acceptance criteria, or grooming a screen for delivery.

• pm-instincts

  Continuous learning - capturing PM reasoning patterns as confidence-scored instincts, updating scores, and promoting clusters into skills or rules. Load when capturing a lesson, reviewing instinct health, or running evolve/prune.

• pm-lifecycle

  The gated PM delivery loop - frame, evidence, draft, review, verify, remember, improve. Load at the start of any substantive PM deliverable (PRD, strategy, prioritization, roadmap, launch plan) to run it as a staged workflow with an evidence trail instead of a one-shot answer.

• pm-memory

  How to recall, write, and distil durable memory - decision records, session summaries, recall budgets, and the trust boundary on recalled content. Load at session start, when saving a session, or whenever using prior decisions.

• prd-confluence-builder

  Generate a team scoped requirements document from discovery output or a scope note, map designs to each requirement, and publish it to Confluence from the team template. Use when asked to create or update a PRD, turn discovery notes into requirements, or publish requirements to Confluence.

• prd-templates

  PRD templates (Lean. Standard, PR/FAQ. Deep) and user story / acceptance criteria standards. Load when writing PRDs, specs, or user stories.

• pre-mortem

  Work backwards from an assumed failure to the risks that caused it, sorted into ones you can control, ones you can only watch, and ones that are simply large. Use before committing to a launch, a delivery plan, or a requirements document.

• prioritization-methods

  Prioritization frameworks and scoring discipline: RICE, ICE. Kano. Value vs Effort. Load when scoring, ranking, or comparing features or backlog items.

• prioritize-assumptions

  Rank the assumptions behind a decision by impact and risk, then propose the cheapest test for each one in the top quadrant. Use when a discovery stage or a requirements draft has surfaced assumptions and the question is which to test first.

• roadmap-frameworks

  Roadmap formats and sequencing logic: Now-Next-Later, theme-based, outcome roadmaps. Load when building or restructuring roadmaps.

• stakeholder-map

  Map the people who can advance or block an initiative by influence and interest, then produce a communication plan matched to each group. Use at the start of a cross functional initiative or when an effort keeps stalling for reasons that are not technical.

• user-research-techniques

  User research methods: interview design, JTBD questioning, survey design, usability testing, synthesis. Load when designing studies or synthesizing user feedback.

Slash commands (3)

• /axos-pm:prd-stress-test

  Three parallel reviewers score a PRD before it goes to engineering. Usage - /pm-teams:prd-stress-test path/to/prd.md. Verdict - READY / NEEDS REVISION / MAJOR REWORK.

• /axos-pm:validation-sprint

  Multi-agent validation of a product idea. Usage - /pm-teams:validation-sprint "idea description". Verdict - BUILD / Do not BUILD / NEEDS MORE EVIDENCE.

• /axos-pm:war-room

  Parallel competitor deep-dives synthesized into positioning + battle cards. Usage - /pm-teams:war-room "Competitor A. Competitor B. Competitor C

Subagents (10)

• deliverable-critic

  Reviews a finished PM deliverable from a clean context. Receives only the artifact and the shared product-context files - never the conversation that produced it. Use before any PRD, strategy doc, prioritization, or roadmap is treated as final. - Read - Glob - Grep

• doc-extractor

  Utility agent (not a PM specialist). Auto-discovers product facts from a codebase: features, tech stack, integrations, scale. Invoked by pm-setup or by PM agents needing current product state. Fast and mechanical, uses haiku. - Read - Glob - Grep

• feature-prioritizer

  Prioritization specialist. Use for RICE/ICE scoring. Kano analysis, value vs effort matrices, backlog ranking, and feature trade-off decisions. - prioritization-methods - Read - Glob - Grep - Write - Skill

• launch-planner

  Go-to-market and launch specialist. Use for launch plans, GTM strategy, distribution channel selection, beta programs, and launch messaging. - go-to-market-playbooks - Read - Glob - Grep - WebSearch - Write - Skill

• market-analyst

  Market research, competitive analysis, and positioning specialist. Use for competitive landscape analysis, market sizing (TAM/SAM/SOM), positioning and differentiation, and win/loss analysis. - competitive-analysis - market-sizing - Read - Glob - Grep - WebSearch - WebFetch - Write - Skill

• product-manager

  Main entry point for all product management work. Use for any PM question, multi-faceted product problems, or when unsure which specialist applies. Routes requests to specialist agents and synthesizes their outputs. - pm-lifecycle - pm-memory - Read - Glob - Grep - Write - Edit - Task - Skill

• product-strategist

  Vision, strategy, and goals specialist. Use for product vision, strategy documents, quarterly/annual goals. North Star metric definition, and strategic trade-off decisions. - Read - Glob - Grep - Write

• requirements-engineer

  Requirements specialist. Use for PRDs, technical specs, user stories, Gherkin acceptance criteria, and feature documentation. - prd-templates - evidence-trail - Read - Glob - Grep - Write - Edit - Skill

• research-ops

  User research and validation specialist. Use for interview study design, survey design, usability testing, problem/solution validation, and synthesizing interview transcripts or customer feedback into insights. - user-research-techniques - Read - Glob - Grep - Write - Skill

• roadmap-builder

  Roadmap planning and sequencing specialist. Use for Now-Next-Later roadmaps, theme-based roadmaps, quarterly planning, feature sequencing, and milestone planning. - roadmap-frameworks - Read - Glob - Grep - Write - Skill

Hooks (3)

• PreToolUse

  python "${CLAUDE_PLUGIN_ROOT}/core/hooks/bootstrap.py" pre:write:sensitive-scan sensitive_scan.py minimal,standard,strict

• PreToolUse

  python "${CLAUDE_PLUGIN_ROOT}/core/hooks/bootstrap.py" pre:write:prd-gate check_prd_gate.py standard,strict

• PostToolUse

  python "${CLAUDE_PLUGIN_ROOT}/core/hooks/bootstrap.py" post:write:run-log log_run.py minimal,standard,strict

Similar plugins