implement-execplan

Execute an ExecPlan from a work item and update meta.json state transitions.

83|4|Updated Mar 17, 2026

Search Tags:#automation #planning #execution #state-management #execute #work-item #execplan

Ready to run

npx skills add https://github.com/grp06/slop-janitor --skill implement-execplan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: implement-execplan
Source: https://github.com/grp06/slop-janitor/tree/main/.agents/skills/implement-execplan
Command: npx skills add https://github.com/grp06/slop-janitor --skill implement-execplan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Executes an ExecPlan from a work item under .agent/work/ or, when necessary, from the legacy .agent/execplan-pending.md flow. It coordinates the execution-state transitions in meta.json to ensure plans are applied safely and auditable.

Core Features & Use Cases

Resolve the target ExecPlan from explicit work-item paths, execplan.md, .agent/active, or the most recently updated item under .agent/work/.
Update execution state transitions (stage and state) in meta.json as the plan is implemented, blocked, or completed.
Support legacy workflows by falling back to .agent/execplan-pending.md when needed.
Read the ExecPlan and associated decision rationale to stay aligned with the original decision and ensure proper verification.

Quick Start

Provide a work-item path or allow the skill to locate the active ExecPlan to begin execution.

Frequently Asked Questions about implement-execplan

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

FAQPage Schema

How do I execute an ExecPlan from a work item?▼

To execute an ExecPlan, the skill resolves the target plan from explicit work-item paths, execplan.md, or the most recently updated item, then applies planned changes while tracking execution state in meta.json.

What is the best way to manage execution state transitions for automation plans?▼

Execution state transitions for automation plans are managed by updating stage and state fields in meta.json as the plan is implemented, blocked, or completed, ensuring changes are applied safely and remain auditable.

How does work-item state management handle legacy execplan-pending flows?▼

Work-item state management handles legacy flows by falling back to .agent/execplan-pending.md when necessary, reading the pending plan and coordinating execution-state transitions to maintain alignment.

Can I use decision rationale to stay aligned during plan execution?▼

Yes, you can use decision rationale to stay aligned during plan execution by reading decision.md when present alongside execplan.md, ensuring implementation respects the original decision and proper verification.

Does plan execution rename or move files during implementation?▼

Plan execution avoids renaming or moving files during implementation, preserving the original work-item structure under .agent/work/ while safely updating stage and state metadata.