Program Design

Turn an agreed task or implementation plan into a reviewable code shape before writing implementation code. Align the human and agent on the interfaces and flow that would otherwise be decided implicitly during code review.

Establish The Design Boundary

Use this skill after the goal and relevant system architecture are settled. Read the complete request or plan, repository instructions, and the surrounding code that establishes current conventions.

Apply the design gate when the work introduces or substantially reshapes modules, interfaces, types, file layout, dependencies, or control flow. Small fixes, local implementation changes, and mechanical edits can proceed without it.

If repository evidence shows that the agreed architecture cannot support a clean implementation, stop and explain the smallest upstream decision that must change. Do not silently redesign the architecture or force the work into an unsuitable shape.

Evaluate Internally

Before presenting the proposal, evaluate whether it: