Skip to content
Skills Library
Programming · Building & coding

plan-execution

/plan-execution

Execute an approved plan or explicit scoped request through dependency-aware tasks and verified evidence. Use for implementation handoffs; do not use to redesign plans, conduct open-ended research, or create commits and pushes without explicit authorization.

Repository
dotfiles ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
6
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Execute an approved plan or explicit scoped request through dependency-aware tasks and verified evidence. Use for implementation handoffs; do not use to redesign plans, conduct open-ended research, or create commits and pushes without explicit authorization.

Original author description

Execute an approved plan or explicit scoped request through dependency-aware tasks and verified evidence. Use for implementation handoffs; do not use to redesign plans, conduct open-ended research, or create commits and pushes without explicit authorization.

How it works

  1. Trigger
  2. Non-trigger
  3. Workflow
Original SKILL.md headings · 23 lines, 502 words
SKILL.md preview
---
name: plan-execution
description: Execute an approved plan or explicit scoped request through dependency-aware tasks and verified evidence. Use for implementation handoffs; do not use to redesign plans, conduct open-ended research, or create commits and pushes without explicit authorization.
---

# Plan Execution

## Trigger

Use when an approved plan or a clear implementation request is ready to execute.

## Non-trigger

Do not activate to invent product requirements, rewrite a plan silently, perform read-only research or review, or deliver through Git when the user has not authorized it.

## Workflow

1. Read the plan or request, project instructions, working state, dependencies, and acceptance criteria. A new plan run must have `status: approved` and no unresolved user-owned blocker, then transition it to `in_progress` before implementation. Create or resume the plan's [run state](references/run-state.md) before the first task, exactly as that reference lays it out: `state.json` written at creation and kept current, `notepad.md` for learnings handed to later tasks, one JSON event per line in `ledger.jsonl` for every check and task transition — no other file name or format — and captured output under `evidence/`. The orchestrating session is its only writer; resume an interrupted `in_progress` or resolved `blocked` plan from its task states, run state, and evidence, and never replay completed tasks blindly. When the plan carries `spec:`, treat the spec's requirements, success criteria, and preserved behavior as acceptance criteria and move the spec `approved → in_progress`.
2. Build a dependency graph and declare each task's write set before dispatch. Parallelize only disjoint write sets; serialize output-dependent work and exclusive surfaces such as lockfiles, manifests, generated outputs, settings, plans, or any file shared by multiple tasks.
3. Implement dependent tasks in the orchestrating session. Dispatch a leaf worker only for parallel tasks with disjoint write sets or one large mechanical task, and give it one self-contained task following [the task contract](references/task-contract.md).
4. Prefer existing code, standard or platform behavior, and installed dependencies before custom code. Make the minimum correct change at the owning layer and follow local conventions.
5. Bound recovery: after a concrete failure, diagnose and retry with the evidence; do not stack speculative patches or expand scope. Escalate unresolved ambiguity rather than redesigning the plan. When the code cannot satisfy a linked spec as written, append the deviation to the spec's `## Deviations` section and ask; never rewrite a requirement to fit the code.
6. When the plan sets `commits: per-task` or `per-phase`, commit each verified task or phase under the work-planning plan contract's "Commit strategy"; with `none` or no plan, leave changes uncommitted. Inspect changed state yourself and record results with [the evidence contract](references/evidence-contract.md) as ledger events, appending workers' reported learnings to the notepad. Run risk-based independent review where required.
7. Complete the plan's final verification on the stable delivered state. Mark the plan `completed` only after it passes; mark it `blocked` when a required unresolved condition stops progress. On completion of a spec-linked plan, mark the spec `shipped`, merge its deltas into the living spec, and archive the change directory as described in the work-planning spec contract. Beyond the plan's commit strategy, do not commit, push, open a PR, merge, deploy, or alter shared state unless explicitly authorized.

Load [implementation guidance](references/implementation.md) or [testing guidance](references/testing.md) only when that detail is needed.
Files in this package (6)
  • SKILL.md 4 KB
  • references/evidence-contract.md 1 KB
  • references/implementation.md 1 KB
  • references/run-state.md 10 KB
  • references/task-contract.md 1 KB
  • references/testing.md 1 KB

Versions

RepositoryScoreLicence
This page · ahmet-cetinkaya/dotfiles90MIT
sentimony/skills100MIT
aquivalabs/speccy100MIT
thiientv/godmode90MIT

Database snapshot: 13.11.2026 · package version 1bf8b8823509 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100implement-plan
    Execute an approved engineering plan through verified tasks, dependency-aware delegation, integration, and repeated review and fixes until no actionable comments remain. Use when the user asks to implement a plan or carry out its tasks. Planning alone does not trigger execution.
  • 100execute
    Execute an approved implementation plan from .ai/plans/ task by task, running each task's verification and committing per task via the check-and-commit gate. Use when asked to "execute the plan", "implement the plan", or after /plan approval. Do not use without an approved plan…
  • 90sy-work
    Build only the approved slice while preserving scope, unrelated worktree changes, and validation evidence. Use when an approved execution plan or explicit bounded task is ready for implementation.
  • 100executing-plans
    Use when you have a written implementation plan to execute in a separate session with review checkpoints. Triggers on: "execute the plan", "implement the tasks", "start building", any plan execution request. Loads plan, reviews critically, executes tasks in batches with checkpoints.
  • 100implement-plan
    Execute an approved implementation plan from the configured plans directory. Use when the user wants to implement a plan phase by phase with verification.
  • 90implement
    Execute an implementation plan step by step with verification checkpoints and progress tracking. Use when the user asks to "implement the plan", "execute the steps", "start implementing", or has an approved plan ready to implement.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.