Plan

Create the smallest implementation contract that removes meaningful ambiguity.

Workflow

1. Reality-check the repository and relevant accepted decisions.
2. Classify work depth: direct, bounded, substantial, or high-assurance. A direct task may not need a formal plan.
3. Identify primary and supporting concerns before selecting specialists.
4. Compose only domain capabilities that materially affect the plan. Domain skills report additional concerns; this skill remains the orchestration owner.
5. Preserve existing architecture and provider choices unless the requested change explicitly revisits them.
6. Break substantial work into coherent behavior slices with clear interfaces/dependencies rather than test-first microsteps.
7. Define failure behavior and verification proportional to risk.

Plan depth

For bounded work, prefer Goal / Current behavior / Change / Files-or-modules / Edge cases / Verification.