Disciplined Plan Implementation FAQs

Question 1

What happens if a verification step fails during implementation?

Accepted Answer

Implementation stops immediately. The skill then diagnoses the error, potentially using web research, and asks the user to approve a fix or adjust the plan before continuing.

Question 2

Does this skill provide progress visibility?

Accepted Answer

Yes, it uses TodoWrite to create a real-time checklist of implementation steps, marking them as in-progress or completed only after successful verification.

Question 3

What is the RPI framework used by this skill?

Accepted Answer

RPI stands for Research-Plan-Implement. It is a disciplined software engineering methodology that ensures code changes are thoroughly researched and planned before implementation begins.

Question 4

How does the skill handle high-stakes code changes?

Accepted Answer

For high-stakes tasks (architectural or security-sensitive), the skill requires an approved plan created via the 'rpikit:writing-plans' skill and will not proceed until one is found.

Question 5

Can I use isolated workspaces with this skill?

Accepted Answer

Yes, for medium and high-stakes tasks, the skill offers to create a Git worktree to isolate your changes from the main repository for safer iteration.

Disciplined Plan Implementation

Key Features

Use Cases

Disciplined Plan Implementation

Key Features

Use Cases