p2a-speclisted

# Plan2Agent Spec Create a development-ready product and implementation specification from approved intake information. ## Inputs - `intake_json` with `status: ready_for_spec`. - User answers for every high-impact `needs_user_decision`. - Explicit constraints and non-goals. - Optional prior `spec_json` when resuming. - Optional Feature Radar preflight research from `.plan2agent/artifacts/<project_id>/preflight-research/`. - Optional same-project, conditional cross-project, or targeted Gate B Memory recall reports prepared by the harness. ## Ownership - Product spec authorship belongs to `p2a-spec-author`. - Implementation planning belongs to `p2a-implementation-planner`. - If subagents are unavailable, produce both sections locally but keep the two responsibilities separate. ## Output Return: - `spec_json` conforming to `.plan2agent/schemas/spec.schema.json` - `open_decisions` - `clarifying_question_disposition` inside `spec_json`, with one disposition for every intake `CQ-n` - `evidence` inside `spec_json`, preserving intake sources and adding any new `WEB-n` or `LOCAL-n` sources - Optional `reference_reconnaissance` inside `spec_json` when Gate B compares reusable technologies, local patterns, prior artifacts, or external implementation approaches - Optional generated Markdown views may be returned when useful for export or review, but `spec_json` is the source of truth. The harness persists `gate-b-spec/spec.json` under `.plan2agent/artifacts/<project_id>/` for Gat