symphony-plan

Draft an implementation plan by mapping work to abstraction layers like Policy, Configuration, and Execution, ensuring spec alignment. Define runtime state transitions, failure modes, and clear PR seams to produce a single, reviewable slice.

Slice decomposition breaks substantial implementation work into a single, reviewable PR slice with explicit state and failure modes. It preserves architectural layers and maps goals to abstraction boundaries to minimize review churn.

Reduce review churn by defining explicit goal, scope, non-goals, and runtime-state considerations in the plan. Aligning with SPEC and harness principles ensures consistent architecture boundaries and minimizes back-and-forth during code review.

Map tasks to abstraction layers by analyzing sources like AGENTS.md, SPEC.md, and docs to assign work across Policy, Configuration, Coordination, Execution, Integration, and Observability. This preserves architectural boundaries and clarifies runtime state transitions.

Generate a spec-aligned plan using sources of truth like AGENTS.md, README.md, docs, SPEC.md, and Harness principles. Provide an issue summary and relevant files to produce a concise, one-slice plan with tests and acceptance criteria.

Formalize an implementation plan for substantial implementation work and tests to ensure a single, reviewable PR slice. Defining exit criteria, acceptance criteria, and runtime state transitions early prevents architectural misalignment and scope creep.