MCAF: Human Review Planning

Trigger On

• a large AI-generated code drop needs a human review plan
• the reviewer cannot inspect every line and needs prioritization
• the user asks which files are highest risk before doing manual review
• the user names a generated folder and wants a saved review plan for it

Workflow

1. Read enough of the target area and its immediate boundaries to understand the generated code before planning review.
2. Map the natural flow of operations first:

- sign up or authentication - create - update - register or configure - execute primary business action - complete, archive, or finalize

1. Use that flow to derive the most efficient human review sequence.
2. Use the reviewer's domain knowledge as a force multiplier:

- compare the generated code against known architecture and existing entities - look for places where the new feature should behave like nearby existing flows - prioritize boundaries where generated code may drift from established system rules

1. Identify high-risk review zones:

- entry points and orchestration layers - persistence and state transitions - cross-boundary integrations - permissions, validation, and invariants - side effects such as email, payments, jobs, or notifications

1. Produce two separate outputs:

- prioritized review flow - prioritized files or modules to inspect

1. Present both outputs in chat.
2. If the user asks for a durable artifact, save the plan to the exact docs path they requested; otherwise use docs/AREA/HUMAN_REVIEW_PLAN.md.

Deliver

• a prioritized human review sequence
• a prioritized list of files or modules to inspect first
• both sections presented separately in chat
• a saved HUMAN_REVIEW_PLAN.md when requested

Validate

• the plan is grounded in actual code reading, not only the folder names
• the review order follows actual user or system flows
• high-risk files are explained, not only listed
• priorities account for likely mismatch against existing architecture or analogous entities
• the plan helps a human skip low-value line-by-line review
• the saved plan is readable without extra chat context

Load References

Related skills