Implement

Skill KonH/ClaudeTools/plugins/k/skills/implement

Claude Code plugin with skills shared across project

Install

npx -y skills add KonH/ClaudeTools --skill implement

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Implement the plan at docs/specs/<YY_MM_DD_HH>_<name>/plan.md, spawning developer sub-agents per phase, writing tests test-first, and marking off completed steps.

SKILL.md

2.5 KB, 557 tokens by cl100k_base, as published. Nobody here has run it

Implement the plan at docs/specs/<YY_MM_DD_HH>_<name>/plan.md.

Plan Discovery

With $ARGUMENTS: resolve against docs/specs/ — look for docs/specs/<YY_MM_DD_HH>_<name>/plan.md using the full dated spec identifier.

Without $ARGUMENTS:

List all */plan.md files under docs/specs/
Extract the YY_MM_DD_HH prefix from each folder
Use the file with the latest timestamp prefix

Orchestration

Read the plan file first. Then decide based on plan size:

1–2 steps or trivial changes: implement inline (no sub-agent needed)
3+ steps, or steps spanning distinct areas of the codebase: spawn a developer sub-agent per major phase

When spawning a developer sub-agent, brief it with:

The full plan text
Which step(s) it is responsible for
Relevant project rules (CLAUDE.md, any project rules directory) — code style and any domain-specific conventions
Current file state / context it needs (read key files first and include excerpts)
Whether any external tool the plan depends on (an editor, engine, or service with its own connection state) is available and connected
For steps touching source code: write the test for the new behavior first so it fails against the current code, then implement until it passes — never disable or weaken an existing test to force a pass, fix the underlying code instead

After each sub-agent phase:

Relay its results and any errors to the user
Verify the work (check for errors, read changed files) before moving to the next phase
If a phase fails, diagnose and re-brief the sub-agent with the fix context — do not skip ahead
Mark each completed agent step in the plan file by changing - [ ] to - [x]

Pre-flight Checks

Follow all project standards in CLAUDE.md and any project rules directory
If the plan depends on an external tool or editor with its own connection/session state, verify that connection is live before starting. If it isn't, stop and ask the user to establish it first.

Completion

After all steps are done:

If any changes touch source code: confirm tests were written test-first (red before green) for the affected logic and all pass
Run the code-review skill (or /code-review if unavailable as a skill) on the changed files — present any concerns one by one and ask the user to approve each fix before applying it