Formalizes project work by creating an execution contract that defines scope, forbidden actions, and success criteria.

Install

mkdir -p .claude/skills/ac-plan && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16857" && unzip -o skill.zip -d .claude/skills/ac-plan && rm skill.zip

Installs to .claude/skills/ac-plan

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Plan and freeze workflow execution by creating an Execution Contract, setting PLAN_FROZEN/CURRENT_ROLE, and updating PROJECT_STATE decisions and Top 3. Use when starting workflow delivery, re-planning after unfreeze, or when scope/constraints change before execution.
267 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Read `PROJECT_STATE.md` and create if missing
  • Define goal, scope boundary, forbidden changes, and acceptance checks
  • Fill `Execution Contract` completely with scope, files to change, forbidden items, steps, checks, commit plan, and rollback note
  • Update `下一步 Top 3` and append `关键决策日志`
  • Set `PLAN_FROZEN: true` and `CURRENT_ROLE: planner`
  • Emit a `[STATE]` anchor and hand off to `$ac-execute`

How it works

This skill formalizes workflow planning by reading and updating `PROJECT_STATE.md`, defining an `Execution Contract`, and setting the plan to frozen, preparing for execution.

Inputs & outputs

You give it
Request to plan and freeze workflow execution, or re-plan after unfreeze
You get back
Updated `PROJECT_STATE.md` with a complete `Execution Contract`, `PLAN_FROZEN: true`, and `CURRENT_ROLE: planner`

When to use ac-plan

  • Defining project scope
  • Freezing execution plans
  • Setting project acceptance criteria
  • Planning delivery workflows

About this skill

  1. Read PROJECT_STATE.md; create it from docs/PROJECT_STATE_TEMPLATE.md if missing.
  2. Define goal, scope boundary, forbidden changes, and acceptance checks.
  3. Fill Execution Contract completely:
  • Scope
  • Files to change
  • Forbidden
  • Steps
  • Checks
  • Commit plan
  • Rollback note
  1. Update 下一步 Top 3 and append 关键决策日志.
  2. Set PLAN_FROZEN: true and CURRENT_ROLE: planner.
  3. Emit a [STATE] anchor and hand off to $ac-execute.

Hard rules:

  • Do not implement feature changes in this skill.
  • Do not hand off if Contract fields are incomplete.

When not to use it

  • When implementing feature changes
  • When `Execution Contract` fields are incomplete
  • When the workflow execution is not being planned or re-planned

Limitations

  • Does not implement feature changes
  • Requires all `Execution Contract` fields to be complete before hand-off
  • Relies on `PROJECT_STATE.md` for project state management

How it compares

This workflow explicitly freezes the plan and assigns a planner role, ensuring a structured and controlled transition to execution, unlike informal planning.

Compared to similar skills

ac-plan side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
ac-plan (this skill)05moNo flagsIntermediate
github-project-management46moReviewAdvanced
create-plans18moReviewIntermediate
phasing17moNo flagsIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry