SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsinteractive-human-review

interactive-human-review

General & other

View repository

Updated 10-15 17:31

About this skill

Skill: interactive-human-review

1. Overview

This Skill aims to solve the problem that after large-scale modifications, humans find it difficult to fully grasp the details and reasons for the changes; it can also be used when reviewing a large amount of content for the first time, to help humans gradually digest and understand it. The Agent will guide the user through an interactive review, using a progressive checklist and Q&A feedback to ensure the user has fully grasped all changes or content to be reviewed.

2. Workflow

  1. Establish a checklist: At the beginning of the modification or discussion, create and maintain a review plan document under the project or artifacts YYYY-MM-DD-HH-mm-review-方案-{简述}.md(for the template, see Checklist Template), as a progress tracking tool for this task. At the beginning of establishing the document, you must fully explore the scope of changes or the review scope to ensure no part of the scope is missed.
  2. Progressive restatement: Do not postpone until the end of the session; each time a phased modification is completed, proactively invite the user to restate their understanding, and provide targeted ELI-level gap-filling (ELI5/ELI14/ELII).
  3. Interactive quiz: Based on the key points in the Checklist, use the AskUserQuestion tool to initiate open-ended or multiple-choice questions.
    • Note: Randomly shuffle the options, and do not reveal the answers before submission.
    • When necessary, directly show the code lines (for example, [filename.py:L10-20](file://...)) or guide the user to use a debugger.
  4. Exit only after everything is complete: The session goal is not considered complete until the user has fully mastered all content on the checklist and successfully passed the quiz (/goal condition).

3. Basic Principles

  • Dig deeper into Why: In addition to "What" and "How", ask more "Why" questions.
  • User first: Let the user restate first, and after exposing cognitive blind spots, provide targeted explanations.
  • Protect the answers: Before the user answers, never spoil the quiz answers in Thought or replies.
  • Develop a multi-dimensional understanding of the project: If what is being reviewed is code or a development project, pay attention to guiding the human to understand and master the change details and connections across multiple dimensions such as **Plan, Design, Architecture, Implementation, Testing, and User Story**.