executing-plans

Review loaded plans and convert them into executable tasks with status tracking.

1|Updated Mar 23, 2026

Search Tags:#workflow #development #task-execution #plan-review #execute-plans #verifications

Ready to run

npx skills add https://github.com/sbalagan22/bloomr --skill executing-plans-sbalagan22

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: executing-plans
Source: https://github.com/sbalagan22/bloomr/tree/main/.claude/skills/executing-plans
Command: npx skills add https://github.com/sbalagan22/bloomr --skill executing-plans-sbalagan22

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinating multi-step plans into executable tasks with built-in review and reporting.

Core Features & Use Cases

Load a plan file, review it critically, and convert it into a sequence of tasks with clear status tracking.
Execute tasks step-by-step, perform verifications after each task, and update progress until completion.
Use with required sub-skills (e.g., finishing-a-development-branch) to finalize development and present results.

Quick Start

Load a plan file, review it critically, and execute all tasks with verifications.

Frequently Asked Questions about executing-plans

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

FAQPage Schema

How do I execute a development plan step-by-step with task tracking?▼

Executing a development plan step-by-step involves loading a plan file, reviewing it critically, and converting it into a sequence of tracked tasks. The process applies verifications after each task and updates progress states like in_progress and completed until the workflow finishes.

What is the best way to review a plan before task execution?▼

The best way to review a plan before task execution is to load the plan file and critically evaluate its steps. This mechanism converts the reviewed plan into executable tasks, ensuring verifications are defined and blockers are identified before development begins.

How do you handle blockers during plan-driven workflow execution?▼

Handling blockers during plan-driven workflow execution requires escalating them when a step cannot be completed. The execution mechanism pauses the task sequence, reports the blocker, and prevents state updates to completed until the issue is resolved.

Can I use sub-skills to finalize development after executing tasks?▼

Yes, you can use required sub-skills to finalize development after executing tasks. Sub-skills like finishing-a-development-branch integrate with the execution workflow to complete the operational sequence and present the final results.

Do I need a pre-loaded plan file to start task execution and verifications?▼

Yes, you need a pre-loaded plan file to start task execution and verifications. The execution mechanism requires an existing plan to review critically, convert into tasks, and apply step-by-step verifications with state updates.

Why does my workflow execution get blocked during state updates?▼

Workflow execution gets blocked during state updates when verifications fail or required sub-skills are missing. The execution mechanism prevents advancing task states from in_progress to completed until all defined verifications pass and blockers are explicitly escalated.