implement

Name: implement
Author: tobihagemann

3installs29forks

How to install implement?

tobihagemann/turbo/implement

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

Installs into the current project.

Summary

Load code-style and task-specific skills, make the change described by the current context, then run /finalize for QA and commit. Use for ad-hoc changes when no plan file or improvements backlog governs the work, and when the user asks to \"just implement\", \"implement directly\

Files · 1

View on GitHub

SKILL.md

1	# Implement
2
3	Standard implementation flow: load style rules, make the change, run post-implementation QA.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each step:
8
9	1. Run `/code-style` skill
10	2. Load task-specific skills
11	3. Make the change
12	4. Run verification
13	5. Run `/preview` skill for UI/UX changes
14	6. Run `/finalize` skill
15
16	## Step 1: Run `/code-style` Skill
17
18	Run the `/code-style` skill to load mirror, reuse, and symmetry rules before editing.
19
20	## Step 2: Load Task-Specific Skills
21
22	Scan the work for types that match available skills, matching against the richest context available: a plan's Implementation Steps if a plan is in conversation context, otherwise the user request, a prior skill's task description, or an improvement entry. For each unambiguous match, run the skill via the Skill tool. For example, if the work includes "add a Drizzle migration" and a skill exists whose triggers reference Drizzle migrations, load it. If a work type has no matching skill trigger, do not load a generic skill.
23
24	If unsure, do not load.
25
26	## Step 3: Make the Change
27
28	Apply the change described by the current context — the user request, a prior skill's task description, or an improvement entry. Keep the edit scoped to what the context describes. If the scope balloons beyond what the context specified, stop and confirm scope before continuing.
29
30	## Step 4: Run Verification
31
32	If a Verification section is in conversation context (e.g., from a plan file), execute the commands, smoke checks, or MCP tool invocations it specifies. If a check fails, run the `/investigate` skill. If a check is blocked by a dependency, unclear requirement, or environmental issue, use `AskUserQuestion` to surface the blocker and let the user choose how to proceed. If no Verification section is in context, skip this step.
33
34	## Step 5: Run `/preview` Skill for UI/UX Changes
35
36	If the change touches a user-facing surface (UI components, styles, templates, markup, user-facing routes or screens), run the `/preview` skill so the user can try it firsthand before QA. When it is unclear whether the change is user-facing, use `AskUserQuestion` to ask whether to preview rather than skipping silently. Skip this step for changes with no user-facing surface (backend-only, CLI, library, build or config).
37
38	## Step 6: Run `/finalize` Skill
39
40	Run the `/finalize` skill.
41
42	Then use the TaskList tool and proceed to any remaining task.
43
44	## Rules
45
46	- Defer `git commit`, `git push`, and PR creation to Step 6.
47	- Don't reference `.turbo/` content (filenames, requirement IDs, shell references, headings) in code or comments. `.turbo/` is gitignored, so these references would be opaque to anyone reading without local copies.

People who liked this also viewed

6 picks

Type

implement

3installs29forks

View on GitHub

How to install implement?

tobihagemann/turbo/implement

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Implement
2
3	Standard implementation flow: load style rules, make the change, run post-implementation QA.
4
5	## Task Tracking
6
7	At the start, use `TaskCreate` to create a task for each step:
8
9	1. Run `/code-style` skill
10	2. Load task-specific skills
11	3. Make the change
12	4. Run verification
13	5. Run `/preview` skill for UI/UX changes
14	6. Run `/finalize` skill
15
16	## Step 1: Run `/code-style` Skill
17
18	Run the `/code-style` skill to load mirror, reuse, and symmetry rules before editing.
19
20	## Step 2: Load Task-Specific Skills
21
22	Scan the work for types that match available skills, matching against the richest context available: a plan's Implementation Steps if a plan is in conversation context, otherwise the user request, a prior skill's task description, or an improvement entry. For each unambiguous match, run the skill via the Skill tool. For example, if the work includes "add a Drizzle migration" and a skill exists whose triggers reference Drizzle migrations, load it. If a work type has no matching skill trigger, do not load a generic skill.
23
24	If unsure, do not load.
25
26	## Step 3: Make the Change
27
28	Apply the change described by the current context — the user request, a prior skill's task description, or an improvement entry. Keep the edit scoped to what the context describes. If the scope balloons beyond what the context specified, stop and confirm scope before continuing.
29
30	## Step 4: Run Verification
31
32	If a Verification section is in conversation context (e.g., from a plan file), execute the commands, smoke checks, or MCP tool invocations it specifies. If a check fails, run the `/investigate` skill. If a check is blocked by a dependency, unclear requirement, or environmental issue, use `AskUserQuestion` to surface the blocker and let the user choose how to proceed. If no Verification section is in context, skip this step.
33
34	## Step 5: Run `/preview` Skill for UI/UX Changes
35
36	If the change touches a user-facing surface (UI components, styles, templates, markup, user-facing routes or screens), run the `/preview` skill so the user can try it firsthand before QA. When it is unclear whether the change is user-facing, use `AskUserQuestion` to ask whether to preview rather than skipping silently. Skip this step for changes with no user-facing surface (backend-only, CLI, library, build or config).
37
38	## Step 6: Run `/finalize` Skill
39
40	Run the `/finalize` skill.
41
42	Then use the TaskList tool and proceed to any remaining task.
43
44	## Rules
45
46	- Defer `git commit`, `git push`, and PR creation to Step 6.
47	- Don't reference `.turbo/` content (filenames, requirement IDs, shell references, headings) in code or comments. `.turbo/` is gitignored, so these references would be opaque to anyone reading without local copies.

People who liked this also viewed

6 picks

Type