Menu
Use when delivery work needs review, a PR or local diff needs validation, or Done readiness is in question.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when a maintainer explicitly asks for Knowledge Workflow setup, checks, upgrade migration, manifest work, or approved configuration updates.
Use when the user asks to implement an approved Kanban task or linked project change with clear acceptance criteria.
Use when delivery work needs a proposal before editing task candidates, Kanban cards, backlog shape, or board changes.
Use when a user asks how to use Knowledge Workflow in a repository, where content belongs, which skill applies, what project rules mean, how to recover safely, or how to record local workflow feedback.
Use when the user has approved a specific shared-knowledge write, promotion, reorganization, or update.
Use when an idea, requirement, feedback, research note, decision, or fact may become shared knowledge but the target is not yet approved.
| name | delivery-review |
| description | Use when delivery work needs review, a PR or local diff needs validation, or Done readiness is in question. |
Before acting, resolve <knowledge_dir> using the runtime bootstrap rules, then read <knowledge_dir>/.workflow/runtime.md and <knowledge_dir>/.workflow/manifest.yml; do not assume non-default workflow paths or default ids.
Use this skill to independently review delivery work after implementation and before completion. Review normally happens while the Kanban card is in Reviewing.
<knowledge_dir>/planning/KANBAN.md.<knowledge_dir>/.workflow/rules/knowledge.md, <knowledge_dir>/.workflow/schemas/common.md, and relevant area schemas under <knowledge_dir>/.workflow/schemas/ for changed knowledge.<knowledge_dir>/members/<member-id>.md.When available, Superpowers verification-before-completion output can be used as validation evidence. Still inspect the diff, tests, acceptance criteria, and knowledge updates directly; Superpowers evidence supports delivery review but does not replace it.
Doing to Reviewing move -> delivery-review -> approved Reviewing to Done move.Doing, this skill may run a pre-review, but pre-review does not replace the Reviewing -> Done acceptance gate.minor-fix, recommend keeping the card in Reviewing while fixes are applied.rework-required, recommend moving the card back to Doing through kanban-maintenance.Blocked and recording blocker details in the linked task item.Reviewing -> Done, reverse-look up downstream tasks whose blocked_by entries reference the completed task and check whether they require readiness or Kanban follow-up proposals.Default review handoffs are not separate files. Put ordinary return-to-implementation or acceptance context in the review report, local work log, task item update, or Kanban maintenance request.
Create a formal shared handoff under <knowledge_dir>/workspace/<member-id>/handoffs/ only when the review handoff is cross-member, long-lived, complex enough to survive the chat, or explicitly requested. Use <knowledge_dir>/.workflow/templates/handoff.md as a reference template. Do not write into another member's workspace.
references/checklist.md.