p2a-harnesslisted

# Plan2Agent Harness Use this workflow to convert an early product idea into development-ready planning artifacts. The harness is an orchestrator, not a checklist: it decides which Plan2Agent role owns each stage, enforces approval gates, and resumes from the latest completed artifact. ## Inputs - A one-sentence product or feature idea. - Optional clarification answers, constraints, audience, or existing artifacts. - Optional Feature Radar preflight research under `.plan2agent/artifacts/<project_id>/preflight-research/`. - Optional resume point such as `resume_from: intake`, `resume_from: spec`, or answered decision ids like `ND-1`. ## Stage to Role Mapping | Stage | Skill | Subagent owner | Input artifact | Output artifact | | --- | --- | --- | --- | --- | | 1. Intake | `p2a-intake` | `p2a-requirements` | raw idea and notes | `intake_json` (`p2a.intake.v1`) | | 2. Product spec | `p2a-spec` | `p2a-spec-author` | intake plus answered decisions | `spec_json.product` (`p2a.spec.v1`) | | 3. Implementation plan | `p2a-spec` | `p2a-implementation-planner` | product spec draft plus Gate A constraints | `spec_json.implementation` (`p2a.spec.v1`) | | 4. Task graph | `p2a-task-breakdown` | `p2a-task-graph` | approved implementation spec | `task_graph_json` (`p2a.task_graph.v1`) | | 5. Review | `p2a-review` | `p2a-quality-reviewer` | spec and task graph | `review_json` (`p2a.review.v1`) | If the CLI cannot spawn subagents automatically, run the matching skill locally and preserve