# Implement Plan

Implement technical plans from thoughts/shared/plans with verification

- Repository: https://github.com/parcadei/Continuous-Claude-v3 (3947 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-01-26
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add parcadei/Continuous-Claude-v3 --skill implement_plan -g -a claude-code -y`
Codex: `npx skills add parcadei/Continuous-Claude-v3 --skill implement_plan -g -a codex -y`
Cursor: `npx skills add parcadei/Continuous-Claude-v3 --skill implement_plan -g -a cursor -y`
Gemini CLI: `npx skills add parcadei/Continuous-Claude-v3 --skill implement_plan -g -a gemini-cli -y`

## Description

Implement technical plans from thoughts/shared/plans with verification

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Implement Plan

You are tasked with implementing an approved technical plan from `thoughts/shared/plans/`. These plans contain phases with specific changes and success criteria.

## Execution Modes

You have two execution modes:

### Mode 1: Direct Implementation (Default)
For small plans (3 or fewer tasks) or when user requests direct implementation.
- You implement each phase yourself
- Context accumulates in main conversation
- Use this for quick, focused implementations

### Mode 2: Agent Orchestration (Recommended for larger plans)
For plans with 4+ tasks or when context preservation is critical.
- You act as a thin orchestrator
- Agents execute each task and create handoffs
- Compaction-resistant: handoffs persist even if context compacts
- Use this for multi-phase implementations

**To use agent orchestration mode**, say: "I'll use agent orchestration for this plan" and follow the Agent Orchestration section below.

---

## Getting Started

When given a plan path:
- Read the plan completely and check for any existing checkmarks (- [x])
- Read the original ticket and all files mentioned in the plan
- **Read files fully** - never use limit/offset parameters, you need complete context
- Think deeply about how the pieces fit together
- Create a todo list to track your progress

### Pre-Implementation Risk Check

Before starting implementation, run a deep pre-mortem:

```
/premortem deep <plan-path>
```

This analyzes the plan against comprehensive checklists:
- Technical risks (scalability, dependencies, data, security)
- Integration risks (breaking changes, migration, rollback)
- Process risks (unclear requirements, stakeholder input)
- Testing risks (coverage gaps, load testing needs)

**If HIGH severity risks are identified:**
- The premortem will block via AskUserQuestion
- User must: accept risks explicitly, add mitigations, or research solutions
- If mitigations are added, update the plan before proceeding

The rest: https://github.com/parcadei/Continuous-Claude-v3/blob/HEAD/.claude/skills/implement_plan/SKILL.md