Skip to content
Skills Library
Programming · Automation

implement-change

/implement-change

Executes plan.md for an active change under Docs/<scope>/Specs/<change-name>/. Use after plan-change when the user approves implementation. Follows tasks in order, validates each step, retries obvious failures once, and stops to ask if blocked. Does not change spec intent without approval.

Repository
spar-kit ↗
Licence
Apache-2.0
Last repository change
07.05.2026

Assessment and security

85/ 100Class: good
Format20 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 07.05.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

Executes plan.md for an active change under Docs/<scope>/Specs/<change-name>/. Use after plan-change when the user approves implementation. Follows tasks in order, validates each step, retries obvious failures once, and stops to ask if blocked. Does not change spec intent without approval.

Original author description

Executes plan.md for an active change under Docs/<scope>/Specs/<change-name>/. Use after plan-change when the user approves implementation. Follows tasks in order, validates each step, retries obvious failures once, and stops to ask if blocked. Does not change spec intent without approval.

How it works

  1. Inputs
  2. Outputs
  3. Workflow
  4. Stop conditions
  5. Completion
Original SKILL.md headings · 95 lines, 428 words
SKILL.md preview
---
name: implement-change
description: >-
  Executes plan.md for an active change under Docs/<scope>/Specs/<change-name>/.
  Use after plan-change when the user approves implementation. Follows tasks in
  order, validates each step, retries obvious failures once, and stops to ask if
  blocked. Does not change spec intent without approval.
---

# Implement change

Execute the plan in `plan.md` while strictly preserving the intent in `<change-name>_spec.md`. Work sequentially, validate each step, keep progress updated. Refine or reorder tasks only for correctness; do not change underlying intent without approval. No silent workarounds, no drifting from the spec.

## Inputs

- `Docs/<scope>/Specs/<change-name>/<change-name>_spec.md`
- `Docs/<scope>/Specs/<change-name>/plan.md`
- Repository code and docs

## Outputs

- Code changes that satisfy `<change-name>_spec.md`
- Updated `plan.md` with progress
- Proposed `<change-name>_spec.md` updates (for approval only—do not apply without approval)

## Workflow

### 1. Load context

- Read `<change-name>_spec.md` and `plan.md`
- Confirm scope and change folder
- Identify current progress (checked tasks)

### 2. Execute tasks in order

For each unchecked task:

1. Understand the task and affected files
2. Implement the change
3. Validate (build/run/tests or targeted checks as appropriate)
4. Mark the task complete in `plan.md`

Proceed sequentially unless reordering is clearly required for correctness.

### 3. Validation

- Prefer targeted checks when a full build is unnecessary
- Ensure changes align with **Success Criteria** in `<change-name>_spec.md`
- Ask the user to test or validate only if the agent cannot run the needed checks

### 4. Failure handling

If a task fails:

1. Fix obvious issues and **retry once**
2. If still failing: **stop**, explain the blocker, propose next steps, ask how to proceed

Do not introduce workarounds that change intent or degrade quality without approval.

### 5. Task evolution (allowed)

- Refine wording for clarity
- Split tasks into smaller steps
- Reorder tasks if needed for correctness

Do not alter task intent in a way that would change the spec.

### 6. Spec change handling

If implementation reveals incorrect assumptions, missing constraints, or a better approach that **changes intent**:

1. Propose the spec update clearly
2. **Do not** implement that divergent path yet
3. Wait for user approval
4. Update `<change-name>_spec.md` only after approval

### 7. Keep context accurate

- Keep `plan.md` in sync with progress
- Add brief notes for edge cases, follow-ups, or partial work

## Stop conditions

Stop and ask if:

- A task cannot be completed after one retry
- A required spec change is identified
- The task list is insufficient or conflicts with the spec

## Completion

Implementation is complete when:

- All tasks are completed or explicitly resolved
- Code satisfies **Success Criteria** in `<change-name>_spec.md`
- No unresolved blockers remain

Then:

1. Summarize: tasks completed, deviations or notes, validation results. Be concise.
2. Ask: **Should I clean up and proceed with documentation?**
3. If yes: begin the **`document-change`** skill if available; otherwise document per repo conventions

Versions

RepositoryScoreLicence
This page · Jed-Tech/spar-kit85Apache-2.0
yaohuangguan/agent-playbook100MIT
shivaedev/pardes90MIT
codagent-ai/agent-skills84MIT

Database snapshot: 13.11.2026 · package version 829aed6c3d41 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100implementing-plans
    Use when an approved implementation plan (a docs/rse/specs/plan-*.md file) exists and the next step is writing the code. Triggers: implement the plan, execute the plan, start building, run the plan.
  • 84execute-plan
    Execute implementation plans step-by-step. Use when user says "execute the plan", "implement the plan we created", "start building based on the plan", "go ahead and implement it", "proceed with the implementation", "execute as a stack", "create a PR stack while implementing",…
  • 100piv-implement
    Executes an implementation plan task-by-task with validation at every step. Use when you have a completed feature plan and want to implement it in one pass.
  • 90implement
    Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.
  • 100ctx-implement
    Execute a plan step-by-step with verification. Use when you have a plan document — canonically specs/plans/<milestone>.md from /ctx-task-out — and need disciplined, checkpointed implementation.
  • 100executing-plans
    Execute a written implementation plan task by task, reviewing it critically first, following each step exactly, running every verification, and stopping to ask rather than guessing when blocked. Use when you have a plan document (such as one from the writing-plans skill) and…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.