vibe-plan-execution
Vibe Plan Execution
Overview
Execute an existing implementation plan without inventing missing behavior. Bind to the plan, verify the facts it depends on, implement the smallest safe current slice, and stop when reality contradicts the plan.
Questioning a plan is allowed. Deviating from it is not allowed until verified evidence proves the plan is incorrect, stale, impossible, unsafe, or already satisfied. Treat "this looks redundant" as a hypothesis, not as permission to skip planned API, specification, implementation, or test work.
If no concrete plan exists, return to planning before coding. vibe-planning
is one valid planning workflow, not a prerequisite for this skill.
Plan Sources
This skill executes any concrete bound implementation plan. The plan may come
More from adhi-jp/agent-skills
review-scope-guard
Use when Codex or code/plan review findings need Definition-of-Done scope triage, especially to separate must-fix issues from minimal hygiene, out-of-scope hardening, repeated noise, or self-induced refinements. Also use when codex-review-cycle invokes scope guard between validity checking and summary render. Do not use for single-shot lint or unrelated changes.
34codex-review-cycle
Use when the user explicitly asks to run an iterative Codex review cycle on a non-empty git diff, including working-tree changes, current branch vs base, explicit commit/tag/branch refs, code diffs, or Markdown planning documents. Do not use for one-shot reviews, auto-hardening, background checks, plan drafting, or empty review targets.
34writing-style-guide
Use when generating or editing user-facing prose, including docs, comments, READMEs, changelogs, commit messages, PR descriptions, and chat replies.
32minecraft-modding-workbench
>
22review-fix-cascade-guard
Use when applying user-selected review findings after scope triage, especially inside codex-review-cycle or after a standalone Codex adversarial review, and a line-scoped fix may create follow-on valid findings. Do not use for ordinary edits, plan drafting, single-shot lint, no-review contexts, or generic refactor checklists.
19vibe-planning
>
17