After finishing the design or implementation and giving the user an initial answer, adversarially verify the deliverable and connect the findings to self-improvement.
Minimum execution order
- Confirm that the initial answer has been given. If not, give the initial answer first → procedures.md
- Launch verification according to the type of deliverable → procedures.md
- Confirm the boundaries with other skills → boundaries.md
- Complete handling of the findings and the addendum → procedures.md
references table of contents
| File | Reference start conditions |
|---|---|
| procedures.md | Confirmation of the initial answer, launching verification, countermeasures, addendum |
| boundaries.md | Boundaries with other skills, situations where this does not apply |
Final check
- The initial answer is given before verification
- For design,
kf-g-agent-review-adversarial-evaluationis followed - For implementation, use the verification worker and
kf-g-agent-review-post-implementation-two-stage, and do not substitute the adversarial evaluation skill - There is a countermeasure for each finding. If there are substantive branches, list the options, and put the recommendation at the end of the line
(推奨)(for HTML, a badge). If there is essentially only one choice, state that it has been adopted/reflected