p2c

Plugin p2c from marketplace p2c-marketplace in dgmiller81/p2c-claude-plugin. Commands read from the repo's manifest — 1 month ago.

Skills (1)

• p2c

  Product-to-Customer orchestration. Walks a product owner / product manager through every phase of taking an idea to a shipped product (Discovery → Validation → Requirements → Design → Architecture → Build → Test → Launch → Measure). Acts as orchestrator and program manager, spawning specialized sub-

Slash commands (9)

• /p2c:design

  Design lane only — wireframes, clickable prototype, 5-user usability testing, design system, accessibility pass, and **mandatory enterprise-grade mockups** for every key screen.

• /p2c:full

  Full Product-to-Customer orchestration. Walk an idea through phases 1–8 end-to-end with the full agent team, producing every deliverable from JTBD through post-launch growth experiments.

• /p2c:help

  Show the p2c command map, sub-agents, and quick-start.

• /p2c:launch

  Launch strategy and all launch documentation — soft launch, gradual rollout, rollback, runbooks, status page, comms kit, support FAQ.

• /p2c:poc

  All-in-one POC — build full working POC + validate it + produce production-ready design specs + planned production sprint plan + detailed cost estimates including all sprints to develop, test (perf/security/QA), and build out the production system.

• /p2c:product

  Product-only scope — discovery, validation, requirements, scope, success metrics. No tech, design, or build work.

• /p2c:tech-build

  Build a working local POC (proof of concept). NOT production-ready — runs on the local machine, demonstrates the validated MVP slice end-to-end.

• /p2c:tech-prod

  Production build path — vertical slices, hardening, CI/CD, observability, launch readiness. The full production engineering effort, not a POC.

• /p2c:tech-scope

  Technical scoping — architecture, ADRs, threat model, data model, observability plan, plus sprint scope and cost estimates. No code yet.

Subagents (8)

• business-analyst

  Acts as the Lead Business Analyst. Fleshes out business requirements and product requirements details. Owns requirements traceability, gap analysis, stakeholder alignment, and process modeling. Use during p2c phases 1–2 and again at phase 8 — for capturing business context, user/stakeholder intervie

• lead-architect

  Acts as the Lead Architect. Owns architectural decisions, alignment, and strategy. Produces C4 diagrams, ADRs, threat models, data models, observability plans, and stack-choice memos. Use during p2c phase 4, and on any cross-cutting technical decision in phases 5–7. Defaults to boring tech, 12-Facto

• lead-developer

  Acts as the Lead Developer. Owns development best practices, vertical-slice design, code structure, build/CI configuration, and component-level documentation. Use during p2c phases 4 (handoff from architect), 5 (build), and 6 (test integration). Produces working code, scaffold structures, CI configs

• lead-qa-coordinator

  Acts as the Lead QA Testing Coordinator. Owns the test strategy across regression, functional, performance, security, and accessibility testing. Use during p2c phases 5–7 — defining the testing pyramid, picking critical paths, designing the test plan, running OWASP/perf/a11y passes, and producing pr

• lead-ux-designer

  Acts as the Lead UX Designer. Owns the visual design of the product — wireframes, prototypes, **mockups (mandatory in p2c)**, design tokens, component library, accessibility quality, brand application, and the design handoff to development. Use during p2c phase 3 (primary owner), and on any cross-ph

• product-owner

  Acts as the Lead Product Owner. Owns product decisions, the PRD, scope cuts, prioritization, success metrics, and go/no-go calls. Use when working on phases 1, 2, or 8 of the p2c flow — discovery, validation, requirements, scope, MoSCoW prioritization, success metric definition, kill criteria, and p

• research-marketing

  Acts as the Research and Marketing Team Lead. Focuses on market research, competitive landscape, positioning, Go-to-Market (GTM) strategy, launch comms, content plan, and post-launch growth experiments. Use during p2c phases 1, 7, and 8 — early competitive scan, launch comms package, and post-launch

• scrum-master

  Acts as the Lead Scrum Master. Facilitates scrum work, breaks bodies of work into stories and sprints, links stories to development components, runs ceremonies, and keeps development teams on task. Use during p2c phases 2, 5, and 7 — story mapping, sprint planning, sprint execution, daily cadence, r

Similar plugins