Implement Plan

Carry the accepted outcome through implementation, relevant validation, and self-review without pausing after the first passing slice.

Preconditions and Authority

• Start from an accepted plan. A clear, low-risk implementation request can carry a brief inline plan; use /plan-it when material decisions remain unresolved.
• Apply /persistent-side-effects and /agentic-change-governance. Necessary in-scope source and test changes do not need per-file approval; protected or out-of-scope actions do.
• Use relevant code and tests to confirm the plan, reusing evidence already gathered. Preserve unrelated user work.
• Adapt implementation details when new evidence preserves the accepted outcome and boundaries. Stop for a decision only when evidence invalidates a load-bearing design choice or changes scope, public behavior, ownership, or risk beyond what was approved.

Applicable Formal Gates

If no documented checker applies and none was requested, skip this section's workflow. Honor an explicit Formal principle check: not needed decision unless new evidence establishes applicability.

For a required gate, run the named checker before product tests or production edits. A missing checker, tooling failure, or design conflict blocks proceeding until resolved or handled by explicit user decision. Do not silently waive a gate or weaken it to pass. Accepted formal model edits may precede the check.

Implement and Validate