planner-specification-decomposition

name	planner-specification-decomposition
description	Turn a non-basic request into a bounded, executable specification and ordered work plan. Use for multi-step features, documents, integrations, migrations, architecture, and design-uncertain tasks.

Specification and decomposition

1. State the intended outcome, audience, explicit scope, exclusions, and success checks before listing work.
2. Decompose only into ordered, independently verifiable steps. Name the owner, dependency, and observable result for each material step.
3. Capture interface, data, compatibility, configuration, documentation, and operational impacts when evidence supports them.
4. Keep undecided alternatives as user decisions. Do not disguise recommendations or assumptions as requirements.
5. Include TDD-first acceptance checks for engineering and explicit Scribe targets for non-code deliverables.