Menu

Individual skill

executing-plans

0upvotes

Carry an actionable change plan through implementation, checks, review and an evidence-backed report. Use when executing several planned steps or integrating bounded worker returns, within existing authorization.

skills/executing-plans/SKILL.md

Read pinned source

Source commit 14c75a97ccbcca4c11daca25a93c8f0da5ad70d1

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
33
Repository last updated
Oct 25, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Executing plans

Use the plan as a map of intended work, then verify the actual results. Continue
ready authorized tasks until the requested outcome is handled or a concrete
constraint blocks them. A plan is not evidence and cannot grant authority.

## Reconcile before writing

1. Read the plan, user request and project instructions. Confirm the assigned
   repository or worktree, current revision, dirty inputs and file ownership.
2. Check prerequisites against the current artifacts rather than task status.
   Identify already delivered work, changed inputs and inaccessible dependencies.
3. Confirm acceptance commands and expected observations before implementing.
   If a command cannot test the outcome, record its correction and reason;
Back to top