implement-plan

Name: implement-plan
Author: tobihagemann

3installs29forks

How to install implement-plan?

tobihagemann/turbo/implement-plan

$npx -y skills add tobihagemann/turbo --skill implement-plan

Installs into the current project.

Summary

Execute an implementation plan file produced by /draft-plan, /turboplan, or /expand-shell. Runs pre-implementation prep, then runs /implement to execute the steps and finalize. Use when the user asks to \"implement plan\", \"implement the plan\", \"execute the plan\", \"run the p

Files · 1

View on GitHub

SKILL.md

1	# Implement Plan
2
3	Execute an implementation plan file.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each step:
8
9	1. Resolve and read the plan file
10	2. Read context files
11	3. Run `/implement` skill
12	4. Update plan status
13
14	## Step 1: Resolve and Read the Plan File
15
16	Determine which plan file to implement using these rules in order:
17
18	1. Explicit path — If an absolute or relative path was passed, use it
19	2. Explicit slug — If a slug was passed (e.g., `add-image-cache`), resolve to `.turbo/plans/<slug>.md` if that file exists; otherwise fall through to rule 5 before erroring
20	3. Single file — Glob `.turbo/plans/*.md`. If exactly one plan exists, use it
21	4. Most recent — If multiple plans exist, use the most recently modified
22	5. Unexpanded shell — If a slug or path was passed but resolved to no plan, derive `<slug>` from the basename (stripping `.md`) and check `.turbo/shells/<slug>.md`. If it exists, halt with: "`<slug>` is a shell that needs expansion first. Run `/pick-next-shell` to expand and implement it."
23	6. Legacy fallback — If `.turbo/plans/` does not exist but `.turbo/plan.md` exists, use it
24	7. Nothing found — If no plan matched any rule above, tell the user to run `/turboplan` (for a new task) or `/pick-next-shell` (for existing shells) and stop
25
26	If multiple plans exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use `AskUserQuestion` to let the user pick from the candidates.
27
28	State the resolved plan path before continuing, then read the file.
29
30	## Step 2: Read Context Files
31
32	Read in full:
33
34	- Every file listed in the plan's Context Files section
35	- Files the user referenced in their original request (if any)
36	- Every file path the plan references in the Context, Pattern Survey, and Implementation Steps sections
37
38	## Step 3: Run `/implement` Skill
39
40	Run the `/implement` skill. The plan file, its file references, and its Verification section are already in conversation context from Step 1.
41
42	## Step 4: Update Plan Status
43
44	After `/implement` completes, set the plan's frontmatter `status:` to `done`. If the plan is the legacy `.turbo/plan.md` without frontmatter, skip this step.
45
46	## Rules
47
48	- The plan file is read-only during execution. If revisions are needed, run `/refine-plan` or `/draft-plan` separately.
49	- Never skip Step 2.
50	- Never enumerate or execute the plan's Implementation Steps inline. The work runs through `/implement`. Restating steps as a turn-level narration counts as inline execution and bypasses the delegation.
51	- If the plan's Implementation Steps or Verification include `git commit`, `git push`, or PR creation, halt before Step 3 and ask the user to remove them via `/refine-plan`.

People who liked this also viewed

6 picks

Type

implement-plan

3installs29forks

View on GitHub

How to install implement-plan?

tobihagemann/turbo/implement-plan

$npx -y skills add tobihagemann/turbo --skill implement-plan

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Implement Plan
2
3	Execute an implementation plan file.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each step:
8
9	1. Resolve and read the plan file
10	2. Read context files
11	3. Run `/implement` skill
12	4. Update plan status
13
14	## Step 1: Resolve and Read the Plan File
15
16	Determine which plan file to implement using these rules in order:
17
18	1. Explicit path — If an absolute or relative path was passed, use it
19	2. Explicit slug — If a slug was passed (e.g., `add-image-cache`), resolve to `.turbo/plans/<slug>.md` if that file exists; otherwise fall through to rule 5 before erroring
20	3. Single file — Glob `.turbo/plans/*.md`. If exactly one plan exists, use it
21	4. Most recent — If multiple plans exist, use the most recently modified
22	5. Unexpanded shell — If a slug or path was passed but resolved to no plan, derive `<slug>` from the basename (stripping `.md`) and check `.turbo/shells/<slug>.md`. If it exists, halt with: "`<slug>` is a shell that needs expansion first. Run `/pick-next-shell` to expand and implement it."
23	6. Legacy fallback — If `.turbo/plans/` does not exist but `.turbo/plan.md` exists, use it
24	7. Nothing found — If no plan matched any rule above, tell the user to run `/turboplan` (for a new task) or `/pick-next-shell` (for existing shells) and stop
25
26	If multiple plans exist and the most-recent choice is non-obvious (e.g., several plans were modified within the same minute), use `AskUserQuestion` to let the user pick from the candidates.
27
28	State the resolved plan path before continuing, then read the file.
29
30	## Step 2: Read Context Files
31
32	Read in full:
33
34	- Every file listed in the plan's Context Files section
35	- Files the user referenced in their original request (if any)
36	- Every file path the plan references in the Context, Pattern Survey, and Implementation Steps sections
37
38	## Step 3: Run `/implement` Skill
39
40	Run the `/implement` skill. The plan file, its file references, and its Verification section are already in conversation context from Step 1.
41
42	## Step 4: Update Plan Status
43
44	After `/implement` completes, set the plan's frontmatter `status:` to `done`. If the plan is the legacy `.turbo/plan.md` without frontmatter, skip this step.
45
46	## Rules
47
48	- The plan file is read-only during execution. If revisions are needed, run `/refine-plan` or `/draft-plan` separately.
49	- Never skip Step 2.
50	- Never enumerate or execute the plan's Implementation Steps inline. The work runs through `/implement`. Restating steps as a turn-level narration counts as inline execution and bypasses the delegation.
51	- If the plan's Implementation Steps or Verification include `git commit`, `git push`, or PR creation, halt before Step 3 and ask the user to remove them via `/refine-plan`.

People who liked this also viewed

6 picks

Type