planlisted

Create a plan for the requested task and save it to `docs/specs/<YY_MM_DD_HH>_<name>/plan.md`. ## Doc paths Default convention: `docs/specs/` for spec/plan folders, `docs/constitution.md` for project principles. Check the project's `CLAUDE.md` for overriding locations before falling back to these defaults. ## Constitution Gate (required) A plan may not be finalized without a constitution. Before anything else: 1. Check whether `docs/constitution.md` exists. 2. If it does not: stop, tell the user no constitution was found, and ask whether they want one created now — and what principles it should capture. Do not invent principles on their behalf. Only continue once a constitution exists (pre-existing or just created with their input). Once a constitution exists, the architect sub-agent reads it before finalizing the plan and appends a **Constitution Check** section to the plan: - Either: `No conflicts found — plan aligns with all principles.` - Or: a numbered list of principles the plan would violate, each with a one-sentence proposed resolution The orchestrator surfaces any violations to the user before presenting the final plan. If there are violations, the user must confirm each resolution before the plan is written. Do not write the plan file if unresolved violations exist. ## Orchestration Spawn an **architect sub-agent** (general-purpose) to design and write the plan. Brief it with: - The user's task description - Relevant project rules (from `CLAUDE.md` and any p