Executing Plans

When to use

• A written plan exists (typically produced by ring:writing-plans)
• Inline execution in this session is preferred over full subagent orchestration
• Plan is small-to-medium and benefits from fast iteration with checkpoints

Skip when

• Plan doesn't exist yet — use ring:writing-plans first
• Production-grade work requiring the full review pool — use ring:dev-cycle instead (lean backend cycle, Gate 0/8/9, dispatches specialists in parallel)
• Plan covers multiple independent subsystems — split into separate plans before executing

Sequence

Runs after: ring:writing-plans (consumes its plan document) Alternative: ring:dev-cycle (subagent-orchestrated, gated workflow with parallel specialist dispatch)

Related

Companion skills: ring:test-driven-development (enforces RED→GREEN→REFACTOR per task), ring:commit (closes each task with a signed atomic commit)