execplan-improve

Rewrite ExecPlan files with code-grounded improvements from deep file analysis.

83|4|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/grp06/slop-janitor --skill execplan-improve
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: execplan-improve
Source: https://github.com/grp06/slop-janitor/tree/main/.agents/skills/execplan-improve
Command: npx skills add https://github.com/grp06/slop-janitor --skill execplan-improve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Read an existing ExecPlan, deeply analyze every referenced file and code path, and rewrite the plan with concrete, code-grounded improvements. Prefer work-item plans under .agent/work/, while preserving backward-compatible support for older singleton plan files.

Core Features & Use Cases

  • Deep analysis of ExecPlan and referenced code to surface gaps, dependencies, and actionable improvements.
  • Code-grounded rewrites that encode concrete changes in the plan while preserving backward compatibility with legacy singleton plans.
  • Traceability and safety: maintain Progress, Decision Log, and Outcomes, with clear auditability of changes.

Quick Start

Provide an existing ExecPlan path or a work-item path to trigger an in-place rewrite that improves plan accuracy and execution reliability.

Frequently Asked Questions about execplan-improve

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

FAQPage Schema
How do I improve an existing execution plan with code-backed refinements?

Yes, you can refactor legacy singleton plans. The rewriting process preserves backward-compatible support for older singleton plan files while applying concrete, code-grounded improvements to the execution workflow.

How do I analyze code paths to update a work-item plan?

An execution plan rewrite maintains traceability by preserving Progress, Decision Log, and Outcomes sections. This ensures that all applied code-grounded improvements remain fully observable and auditable after the plan is updated.

What's the best way to make an automation workflow plan more accurate?

The best way to make an automation workflow plan accurate is to deeply analyze referenced code paths and rewrite the plan with concrete changes. This grounds the workflow in actual code dependencies and refactoring requirements.

Does the plan rewriting process work with work-item plans under .agent/work/?

Yes, the plan rewriting process specifically targets work-item plans under .agent/work/. It deeply analyzes the referenced files and code paths to ensure execution reliability and maintain an auditable decision log.