implement-plan

Implements task-based plans through orchestrator and implementer Codex tasks using wt worktrees.

1|Updated Dec 18, 2009
One-click install
npx skills add https://github.com/thurn/dotfiles --skill implement-plan-thurn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-plan
Source: https://github.com/thurn/dotfiles/tree/main/.llms/skills/implement-plan
Command: npx skills add https://github.com/thurn/dotfiles --skill implement-plan-thurn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Executing multi-task implementation plans manually risks inconsistent review, lost state, and unverified promotion. This Skill coordinates a persistent orchestrator and implementer pair of Codex tasks to execute plan assignments with certified promotion and durable state tracking. ## Core Features & Use Cases - Two-task orchestration: A receiving orchestrator task reviews and authorizes work while a single persistent implementer task executes each assignment in a fresh wt worktree. - Bounded review and promotion: At most three reviews per task, with explicit promotion mandates, exact immutable candidates, and Tollgate-certified promotion and remote synchronization. - CI interruption handling: Suspected CI unreliability suspends the active task for a fresh investigation worktree, with structured resume and blocker adjudication flows. - Use Case: Given a plan document with multiple dependent tasks, invoke $implement-plan to have the orchestrator dispatch assignments one at a time, review each submitted candidate, and promote verified changes without manual worktree management. ## Quick Start Invoke $implement-plan with the paths to your plan documents to start the orchestrated implementation run.

Frequently Asked Questions about implement-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a plan document with Codex tasks?▼

Invoke $implement-plan explicitly with your plan paths. The receiving task becomes the orchestrator, which creates one persistent implementer task and dispatches assignments one at a time, reviewing and authorizing each promoted candidate.

How does the orchestrator and implementer workflow work?▼

The orchestrator builds assignments from the plan, sends ASSIGN messages, reviews submitted candidates in at most three reviews, and issues promotion mandates. The implementer works in a fresh wt worktree per task, submits exact candidates, and drives certified promotion.

Can implement-plan run without explicitly invoking it?▼

No. The Skill must be invoked by name as $implement-plan. It does not activate from a generic request to implement a task or execute a plan, and its policy disables implicit invocation.

What happens when CI becomes unreliable during implementation?▼

The implementer suspends the active task, preserves work and evidence, and sends CI_UNRELIABLE. The orchestrator inserts a bounded investigation in a fresh worktree, then resumes the suspended assignment in its original worktree without resetting review counts.

What are the limitations of the implement-plan workflow?▼

It uses exactly two persistent Codex tasks and never creates per-assignment implementers or substitutes subagents. Reviews are capped at three per task, promotion never bypasses Tollgate certification, and material product decisions remain with the user.