penpot/review-plan.md at f91ea6efc4ffdfb403c22307bfe50d8e812725c1

mirror of https://github.com/penpot/penpot.git synced 2026-09-16 17:06:17 +00:00

Andrey Antukh 32d313b0c8 🎉 Add planning and review agent commands

Add the planning/review command suite for opencode and align the
planner skill with it:

- /make-a-plan (build agent): researches the session subject, drafts
  the plan with the planner skill, asks open questions, then saves
  the final plan to .opencode/plans/.
- /review-plan: reviews a plan with the plan-review skill; on
  approval suggests /implement-plan, on request changes /make-a-plan.
- /review-code: reviews a diff, PR, or code change with the
  code-review skill; suggests /make-a-plan for substantive findings.

All commands run as the build agent with explicit read-only rules
that expire when the command's work is done, so follow-up requests
need no agent switching. The planner skill no longer writes the plan
file on its own: it saves only when a command or the user explicitly
instructs it, and it suggests /review-plan and /implement-plan as
next steps.

AI-assisted-by: omen-alpha

2026-09-08 15:40:15 +00:00

2.7 KiB

Raw Blame History

description, agent

description	agent
Plan review — evaluate an implementation plan with the plan-review skill before executing it (read-only while reviewing)	build

Act as a senior software engineer and perform a thorough review of an implementation plan.

Instructions

Determine the plan under review from the session context (for example, a plan just produced by /make-a-plan) or from a plan file path given by the user (typically under .opencode/plans/). If a file path is given, read the file first so the complete plan is in context.
Delegate the review to the general subagent (via the task tool), unless the user specifies another agent. Include in the prompt the plan-review skill name and all user context.
When the subagent returns, output the review to the user verbatim. Do not summarize it and do not act on its findings.
Right after the review, suggest the next step based on the verdict. These are suggestions — the user decides, and any instruction overrides them:
- Approve → suggest /implement-plan to execute it.
- Request changes → suggest /make-a-plan to make a plan to address the findings.

Hard rule — read-only while reviewing

This command is read-only for the duration of the review: from the moment it starts until the user considers the review finished (including any feedback, questions, or clarifications about it). During that period, never fix, implement, edit files or create commits — not even "obvious" fixes derived from the findings. Once the user explicitly states the review is done (or moves on to a different task), this rule no longer applies and you act as a normal build agent again.

Instructions for the subagent

Load the plan-review skill and follow its process and output format.
Read AGENTS.md (if present) and follow its instructions for finding and reading all related documentation and testing memories before reviewing.
Return in your final message the COMPLETE review, verbatim, exactly as the skill instructs it to be produced. Do not summarize it — include the full structured review.

Strong rules for the subagent

Do not invent problems. Every finding must be real and actionable.
Read-only: do not modify any file and do not create a commit — this command only reviews.
Be specific and constructive. "This could be better" is not helpful — explain why and how.
Prioritize by impact. One structural issue outweighs ten nits.
Judge the plan as the implementer would: every task executable without guessing, ordering follows the dependency graph, risks named.

User input, overrides and additional context

$ARGUMENTS

2.7 KiB Raw Blame History