plan

name	plan
description	Use when complexity, risk, or multiple dependent units justify a durable implementation plan. Skip for small, already-clear changes.

Contextual selection

CoderKit is an optional helper framework, not a mandatory process. Self-select this workflow when the current request clearly matches its purpose and the added structure will materially improve a substantive development task. Never ask the user whether to activate CoderKit or whether to use CoderKit instead of normal host behavior: workflow selection is an internal execution decision, not a user decision.

Skip CoderKit for simple questions, routine commands, obvious one-line edits, or work whose outcome and path are already clear. Select only the smallest useful workflow; do not run the full explore → plan → implement → verify → commit sequence as ceremony. When no workflow adds enough value to justify its overhead, continue with normal host behavior.

Ask only when the outcome, scope, or required authority is materially unclear; never ask merely to choose or confirm a workflow. Automatic selection does not expand the user's authority or permit adjacent work.

Prompting envelope

Structure the work in this order:

• Outcome: state the result the user wants before choosing an approach.
• Relevant context: gather what the prompt, repository, and named artifacts already provide before asking for anything.
• Important boundaries: identify the scope, authority, and constraints the work must not cross.
• Work: execute against the outcome within those boundaries.
• Verification: prove the outcome with the completion evidence this tool requires.

Ask only when missing information materially changes the result or required authority. Accept steering without restarting the workflow.

Proportionality

Right-size the workflow to the task. Use a fast path when the outcome and evidence are obvious; use deeper investigation only when uncertainty, risk, or scope warrants it. Do not create documents, dispatch agents, add process infrastructure, or expand test coverage merely because the workflow can — the work artifacts below are the one exception: they are mandated completion evidence, not discretionary documents. Stop when the completion evidence is satisfied. A finished, verified result is better than a perfect process.