writing-planslisted

# Writing Plans Settle every implementation decision before handoff. The executor writes the code; the planner specifies the contracts, steps, patterns, and proof that remove the need to choose an approach. Keep production code and complete test bodies out of the plan; include signatures, data examples or concise algorithms only when needed to settle ambiguity. ## Contract Inputs: - Requirements, target repository, current issue/document, and scope constraints. - Harness-selected planner and authorized publication scope. Outputs: - One current implementation plan bound to requirements and an inspected revision. - Resolved decisions, exact paths/symbols, ordered steps, verification mapping, and blocking readiness result. Creates/Modifies: - The authorized `## Implementation Plan` comment on the requirements issue, or the plan section in the single canonical local document. - No implementation files and no autonomous executor dispatch. External Side Effects: - Repository/tracker reads and authorized plan publication. Confirmation Required: - Ask only for missing authority or consequential intent. Authorization to prepare or plan this issue already covers that scope; skip repeated approval prompts. Return a draft to a coordinating engine when it owns publication. Delegates To: - `prd-quality-gate` for the canonical plan template and execution-readiness check. ## Research and Decide 1. Read live requirements and relevant comments, repository instructions a