vibe-planning
Vibe Planning
Overview
Turn rough vibe-coding intent into a plan another engineer or agent can execute without inventing missing behavior. Treat the user's request as valuable intent, not verified fact: preserve the goal, prove what can be proven, and make uncertainty visible.
vibe-planning is plan-only. While using it, create or update only the plan
artifact. Do not implement, edit application code, tests, skill packages, evals,
non-plan docs, configs, changelogs, commits, or any other non-plan artifact.
Apply the same boundary to the active task list, checklist, or tool-managed plan. Active tasks may cover only plan artifact work. Do not add current-turn implementation phases, execution slices, non-plan edit tasks, commit tasks, or "now implement the plan" follow-ups. If the user asks for planning and implementation in one request, write or revise the plan artifact and stop.
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-plan-execution
Use when the user asks to execute, implement, continue, or apply an existing implementation plan, specification, acceptance criteria, task plan, or vibe-planning output. Do not use for plan creation or coding requests with no concrete plan to bind.
17