implementing-plans

Implementation Phase

Execute the implementation plan for: $ARGUMENTS

Purpose

Implementation executes an approved plan with discipline and verification. The goal is not just working code, but verified, documented progress that matches the plan. Implementation follows the plan strictly, verifying each step before proceeding.

Process

1. Locate the Plan

If $ARGUMENTS is a file path (starts with / or docs/ or ends with .md):

• Read the file at that path directly
• Check if plan is marked approved
• Proceed based on stakes level

Otherwise, search for plan by topic:

Look for plan at: docs/plans/YYYY-MM-DD-<topic>-plan.md

(Search for files matching *-<topic>-plan.md pattern using $ARGUMENTS as the topic)

If plan exists:

• Read the plan document
• Check if plan is marked approved
• Proceed based on stakes level

If no plan exists:

• Check stakes level of the requested work
• Apply enforcement based on stakes

2. Apply Stakes-Based Enforcement

High Stakes (architectural, security-sensitive, hard to rollback):

Cannot proceed without an approved plan.

High-stakes implementations require:
1. Research phase (rpikit:researching-codebase skill)
2. Approved plan (rpikit:writing-plans skill)

Invoke the Skill tool with skill "rpikit:writing-plans" to create a plan first.

Stop and do not proceed.

Medium Stakes (multiple files, moderate impact):

Warning: No approved plan found for '$ARGUMENTS'.

Medium-stakes changes benefit from planning.

Use AskUserQuestion with options:

• "Create a plan first" (recommended)
• "Proceed with caution"
• "Cancel"

Low Stakes (isolated, easy rollback):

Note: Consider rpikit:researching-codebase and rpikit:writing-plans skills for better results.
Proceeding with implementation...

Proceed with inline planning.

3. Offer Worktree Isolation

Before making changes, offer to create an isolated worktree.

First, check if already in a worktree: