implementation-executor

Name: implementation-executor
Availability: InStock
Author: Slingr

Execute implementation plans as resumable workflows with persistent logs.

Updated Sep 16, 2025

Search Tags:#planning #logging #validation #implementation #resume #checkpoint

Ready to run

npx skills add https://github.com/slingr-stack/qa-test-drumr --skill implementation-executor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implementation-executor
Source: https://github.com/slingr-stack/qa-test-drumr/tree/main/.github/skills/implementation-executor
Command: npx skills add https://github.com/slingr-stack/qa-test-drumr --skill implementation-executor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

This Skill turns an existing implementation plan into a resumable execution workflow, so work can continue safely without reconstructing hidden context or losing progress.

Core Features & Use Cases

Step-by-step execution: Follows a plan file in bounded slices instead of treating it like a one-shot document.
Checkpoint-aware progress: Stops at major handoff points, asks for confirmation when needed, and keeps execution aligned with the plan.
Persistent implementation logging: Maintains a reusable log with decisions, validation results, blockers, and the next resume point.
Ambiguity resolution: Drills into unresolved questions one at a time before coding a step.
Use case: Resume a partially completed repository change, validate each slice, and hand the work off cleanly to another agent.

Quick Start

Ask the implementation-executor skill to resume the target plan directory and keep the implementation log updated as it executes the next bounded step.

Frequently Asked Questions about implementation-executor

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

FAQPage Schema

How do I resume an implementation plan that was interrupted midstream?▼

To resume implementation midstream, you need a resumable workflow that reads a target plan directory and continues from the last checkpoint. This approach executes bounded slices step by step and maintains a persistent implementation log to track decisions, blockers, and progress.

How does checkpoint tracking work when executing a step-by-step plan?▼

Checkpoint tracking works by stopping execution at major handoff points within bounded slices and asking for confirmation before proceeding. It validates after each slice and logs decisions, blockers, and the next resume point to ensure execution stays aligned with the original plan.

What is a persistent implementation log and when do I need one for repository work?▼

A persistent implementation log is a reusable record capturing decisions, validation results, blockers, and the next resume point during repository work. You need one when executing a plan that must be paused, resumed midstream, or handed off cleanly to another agent.

Can I execute a plan file in bounded slices instead of processing it all at once?▼

Yes, you can execute a plan file in bounded slices rather than treating it as a one-shot document. This method processes the plan step by step, validates each slice before moving forward, and stops at checkpoints to ask for confirmation when needed.

How do I resolve unresolved ambiguities in an implementation plan before coding a step?▼

To resolve ambiguities before coding a step, the execution workflow drills into unresolved questions one at a time. This ensures all unclear aspects of the plan are clarified sequentially before proceeding with the actual implementation of that bounded slice.

What is the best way to hand off partially completed repository changes to another agent?▼

The best way to hand off partially completed changes is using a persistent implementation log recording decisions, validation results, blockers, and the next resume point. This handoff-ready logging allows another agent to continue execution safely without reconstructing hidden context.