domains / families / software-engineering / to-plan

to-plan

separate

Use when asked for an implementation plan or execution contract for one or more GitHub issues or an in-chat task, including a read-only review of the next safe step, without drafting or provider access, when the source or contract is incomplete, or a retained approved GitHub plan has an existing amendment chain or a changed published integration decision needing durable consumption.

When to use

• implementation plan for GitHub issues
• execution contract for in-chat tasks
• read-only review of next safe step
• handling incomplete source or contract
• processing existing amendment chains
• durable consumption of changed integration decisions

When not to use

• drafting code
• provider access
• creating or switching branches
• editing source and test files
• GitHub writes without approval
• discussion-only review without executor-readiness request

Skill page

Source