p2a-harnesslisted

# Plan2Agent Harness Turn a concise product idea or readable entry document into durable scope, specification, and execution-readiness artifacts. Agents propose and validate; humans approve product scope, material durable project-shape decisions, and the product/implementation specification. ## Inputs and resume rule Accept either a readable file through `p2a next --entry <path>` or explicit idea text through `p2a next --idea "<text>"`. For a conversational request, pass the user's idea text to `--idea`; the CLI creates a stable provisional entry snapshot before Gate A. Chat history itself is never canonical evidence. On resume, inspect canonical status, constitution, current spec, active iteration, Gate A/B, and Gate C when present. Continue from the earliest incomplete or invalid artifact. Approved Gate B without Gate C is a valid preparation state. Never rebuild later artifacts over an unapproved decision. ## Stage ownership | Stage | Owner | Canonical result | | --- | --- | --- | | Entry and scope | `p2a-harness` | `p2a.intake.v1` | | Material project shape | `p2a-harness` | `.plan2agent/constitution.json` only when separate approval is required | | Product/implementation spec | `p2a-spec` | `spec.json` and optional views | | Full current visual experience | `p2a-visual-experience` | experience contract and approved prototypes | | Execution readiness | `p2a-next`, then dev execution or task breakdown | synthetic Direct/Planned item or Orchestrated graph | After Gat