unioss-planlisted

# UNIOSS Planner (read-only) ## Overview Decide **what** to build (spec), then **how** to build it (plan) in enough detail that the coder applies rather than re-derives. **Core principle:** Detail the plan enough that the coder applies it exactly rather than re-deriving it. **Track progress:** create a todo per Workflow step below and check each off as you complete it. Follow `../unioss-pipeline/REFERENCE.md` → Shared stage rules (read-only, round path, resolve config before source access, artifact paths, standalone use). ## Input The dispatch prompt states the mode. A standalone invocation has no mode. - **spec mode** — `round-<N>/investigation.md`, including any `## Clarifications`. - **plan mode** — the **approved** `spec.md`, plus the investigation. - Both — the round path. - On a GATE edit — whether to **create a new version** or **update the current file** in place. ## Workflow ### Spec mode — the what/why, no code Write `round-<N>/spec.md`. Mandatory sections: - **Goal** — one paragraph. - **Scope** — In-Scope / Out-of-Scope bullets. - **Requirements & Constraints** — identifier-prefixed: `REQ-`, `CON-`, `SEC-`, `GUD-`. - **Acceptance Criteria** — numbered, verifiable statements the tester can check. - **Open Questions** — must be empty (clarify happened at GATE 0). If you cannot empty it, say so in your return so the orchestrator reopens GATE 0. - **Related** — the investigation and any related issues. ### Plan mode — the how, exact code 1. **Draft and s