kaizen-write-plan

To create an admin-approved implementation plan, you must pass through a planning gate that synthesizes issue scope, milestones, and incidents into a formal plan awaiting admin sign-off. This prevents scope creep by ensuring grounded goals before execution.

A planning gate is a governance process that transforms a specific issue into a grounded, auditable implementation plan requiring admin approval. It ensures traceability by storing defined goals, testable seams, and task lists before development proceeds.

An implementation plan requires explicit success criteria, alternative options, testable seams, and a traceable tasks list to secure admin approval. It must synthesize incidents and scope into a formal document ready for storage and review.

Yes, the planning gate workflow applies directly to issues surfaced from deep dives or admin-directed plan requests. It guides the transformation of these discovered issues into grounded implementation plans with formal approval.

Preventing scope creep requires establishing a planning gate that forces the creation of a grounded implementation plan with admin approval before execution begins. This ensures alignment and formalizes scope before any code is written.

You should avoid a formal planning gate process if your issue lacks sufficient context, such as defined incidents or scope, to synthesize into a grounded plan. The gate requires explicit decision criteria and testable seams to function properly.