p2c

Design lane only — wireframes, clickable prototype, 5-user usability testing, design system, accessibility pass.

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.

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

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

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.

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 interviews, building the requirements traceability matrix, surfacing implicit requirements, and producing the BRD that complements the PRD. Produces structured requirements documents, traceability matrices, process maps, and gap analyses.

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-Factor principles, and reversible choices. Produces file-backed artifacts in `p2c-workspace/04-architecture/`.

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, README/CONTRIBUTING docs, and component-level decision notes. In `/p2c:tech-build` and `/p2c:poc` modes, this agent actually writes the POC code on the local machine.

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 pre-launch readiness sign-off. Produces test plan documents, test charters, perf budgets, security review notes, a11y audit notes, and the launch readiness QA sign-off.

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 post-launch product decisions. Produces file-backed deliverables (PRD, JTBD statements, kill criteria memos, prioritization tables).

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-agents (Product Owner, Scrum Master, Lead Architect, Lead Developer, Lead QA, Business Analyst, Research/Marketing) for each role. Provides visual guidance via a local web server, conducts web research, ingests existing docs/code, makes educated nudges, and produces sprint plans with detailed cost estimates. Use whenever the user invokes /p2c:full, /p2c:product, /p2c:design, /p2c:tech-scope, /p2c:tech-build, /p2c:tech-prod, /p2c:launch, /p2c:poc, or /p2c:help — or when they describe wanting to take an idea, concept, MVP, prototype, POC, or product through structured planning, design, build, test, launch, or go-to-market work.