writing-planslisted

# Writing Plans Create an implementation plan another agent can execute with minimal ambiguity. ## Output Path Derive the **topic folder** from the spec path (the derivation rule and the folder shape are defined in the "Artifact Layout" section of `skills/brainstorming/SKILL.md`): the spec must be `<D>/specs/<file>` where `<D>` is a direct child of `docs/superpowers-orchestrator/` at the repository root and `<D>`'s basename matches `^[0-9]{4}-[0-9]{2}-[0-9]{2}-[a-z0-9]+(-[a-z0-9]+)*$`. Then `<D>` is the topic folder, its basename is `<date>-<slug>`, and `<slug>` is that basename minus the date prefix. Save to `docs/superpowers-orchestrator/<date>-<slug>/plans/<slug>.md`, creating `plans/` if it does not exist. - User preferences for plan location override this default. - A spec that is **outside the layout** is handled by "Spec Outside the Layout" below — do not write a plan next to it. ## Spec Outside the Layout A spec whose path is not `<D>/specs/<file>` — where `<D>` is a direct child of `docs/superpowers-orchestrator/` at the repository root whose basename matches the topic-folder shape defined in the "Artifact Layout" section of `skills/brainstorming/SKILL.md` — gets **no plan written beside it**. The `specs/` segment is required: the general derivation rule in that section also accepts `<D>/plans/<file>`, but a *spec* sitting in a `plans/` folder is outside the layout and gets the offer below, exactly as this task's "Does NOT cover" note states. The invariant t