executing-plans

Execute written implementation plans with sequential tasks and blocker handling.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/brmatola/gremlins --skill executing-plans-brmatola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/brmatola/gremlins/tree/main/skills/executing-plans
Command: npx skills add https://github.com/brmatola/gremlins --skill executing-plans-brmatola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between a written plan and concrete execution, enabling automatic progression from plan review to task completion while maintaining guardrails and visibility.

Core Features & Use Cases

  • Autonomous plan execution by default with optional batched checkpoints.
  • Critical blocker handling: stops on blockers and requests guidance.
  • Structured progress reporting and traceable completion through standard plan directories.

Quick Start

Start by selecting a plan name. For autonomous mode, run: /executing-plans {plan-name}. For batched mode with checkpoints, run: /executing-plans {plan-name} --batched

Frequently Asked Questions about executing-plans

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

FAQPage Schema
How do I automate task execution from a written implementation plan?

Automating plan-driven task execution involves sequentially processing written implementation plans with progress checkpoints, enabling automatic progression from plan review to task completion while maintaining guardrails and visibility.

Can I run plan execution in batches with checkpoints instead of fully autonomous mode?

Yes, batched processing with checkpoints is supported alongside autonomous execution. You can run batched mode to pause for progress reviews, ensuring deterministic task execution maintains structured reporting and traceable completion.

How does blocker handling work during automated sequential task execution?

Blocker handling stops automated execution when critical issues are encountered and requests guidance. This ensures plan-driven software development maintains guardrails, preventing tasks from proceeding until the blocker is resolved.

What is the best way to track progress and completion during plan-driven software development?

Structured progress reporting and traceable completion are achieved through standard plan directories and a defined implementation path, ensuring visibility and traceable completion throughout the automated sequential task execution process.

Do I need specific dependencies to run automated plan execution?

No specific dependencies are required to run automated plan execution. The process applies to plan-driven software development and engineering tasks, using standard plan directories to manage sequential execution and structured reporting.

When should I use autonomous mode versus batched mode for task management?

Use autonomous mode for automatic progression through implementation plans without interruption, and use batched mode when you need progress checkpoints to review sequential task execution before continuing to the next stage.