Skip to main content

/logic-plan-critic

Criticize a workspace plan. Do not rewrite the plan. Do not implement.

Outcome

You hold a verdict: PASS, REVISE, or REJECT. The plan file is unchanged.

Assumptions

  • A {slug}-plan.md exists.
  • Skill file: .agents/skills/logic-plan-critic/SKILL.md
  • MCP tools are visible.

Non-goals

  • Do not rewrite the plan.
  • Do not implement.
  • Do not write the next artifact.

Contract

The critic is read-only. It re-queries hook_graph for blast radius. It does not trust the plan graph unverified.

Criticizing a plan is scope=IN.

Syntax

/logic-plan-critic
Plan: @tasks/bin-freeze-plan.md

If the slash name does not start the skill, put @.agents/skills/logic-plan-critic/SKILL.md on line 1.

Expected result: Findings with chapter and evidence. Then PASS, REVISE, or REJECT.

Fields

Rules to load

  1. .agents/rules/mcp.md
  2. .agents/rules/logic/thinking.md
  3. .agents/rules/hook-utils-mcp.md
  4. .agents/rules/logic/plan-format.md
  5. .agents/rules/logic/grill.md
  6. .agents/rules/logic/solution-proposal.md

Checklist

  • Steelman the decision. Name the strongest objection, then whether it holds.
  • Counterexamples: replay, missing document, partial failure, concurrency, empty input.
  • Audit redundancies: duplicate hooks, overlapping fields, two owners for one artifact.
  • Calculate overlaps. The same document must not be written in two phases. The same hook must not be updated twice.
  • Blast radius 🟢 / 🟡 / 🔴 vs live upstream / downstream / references.
  • Gradual order respected. Documents before hooks. Creates before deletes of dependents.
  • Every phase has separation of concerns and testable logic gates.
  • Rules loaded in the header match what the plan used.
  • No invented paths, fields, or statuses.

Verdict

VerdictWhen
REJECTGradual order violated, MCP skipped, or identity fields UNKNOWN
REVISEIncomplete gates or understated blast
PASSNo blocker remains

Cite chapter and evidence.

Constraints

  • If the verdict is not PASS, revise the plan. Do not start /hook-plan.
  • research plans do not need this critic before stop. They have no implementation phases.

Errors

ProblemCauseAction
Tools missingMCP not registeredStop. Fix Setup.
Plan graph trusted as-isCritic skipped hook_graphRe-run. Blast must be live.
REJECT on identitiesRequired field still UNKNOWNReturn to /logic-plan or /logic-discovery