mirror of
https://github.com/RooVetGit/Roo-Code.git
synced 2026-08-28 05:27:24 +00:00
85 lines
No EOL
3 KiB
XML
85 lines
No EOL
3 KiB
XML
<verification_workflow>
|
|
<overview>
|
|
Compare provided documentation against actual codebase implementation.
|
|
Output is a structured diff of claims vs reality.
|
|
Do NOT rewrite the docs. Do NOT suggest wording. Just report discrepancies.
|
|
</overview>
|
|
|
|
<process>
|
|
<step number="1">
|
|
<title>Receive Documentation</title>
|
|
<actions>
|
|
<action>User provides documentation to verify (text, file, or URL)</action>
|
|
<action>Identify the feature/aspect being documented</action>
|
|
</actions>
|
|
</step>
|
|
|
|
<step number="2">
|
|
<title>Extract Claims</title>
|
|
<actions>
|
|
<action>Parse the documentation into discrete claims</action>
|
|
<action>Tag each claim with a category (behavior, config, constraint, etc.)</action>
|
|
<action>Record the exact quote from the documentation</action>
|
|
</actions>
|
|
</step>
|
|
|
|
<step number="3">
|
|
<title>Verify Against Code</title>
|
|
<actions>
|
|
<action>For each claim, find the relevant code</action>
|
|
<action>Compare claim to actual implementation</action>
|
|
<action>Record: ACCURATE, INACCURATE, OUTDATED, MISSING_CONTEXT, or UNVERIFIABLE</action>
|
|
<action>For inaccuracies, record what the code actually does</action>
|
|
</actions>
|
|
</step>
|
|
|
|
<step number="4">
|
|
<title>Output Verification Report</title>
|
|
<actions>
|
|
<action>Write verification to .roo/extraction/VERIFY-[feature].yaml</action>
|
|
<action>Use the output schema (see output_format.xml)</action>
|
|
</actions>
|
|
</step>
|
|
</process>
|
|
|
|
<verification_statuses>
|
|
<status name="ACCURATE">
|
|
<meaning>Claim matches implementation</meaning>
|
|
</status>
|
|
<status name="INACCURATE">
|
|
<meaning>Claim contradicts implementation</meaning>
|
|
<requires>What the code actually does</requires>
|
|
</status>
|
|
<status name="OUTDATED">
|
|
<meaning>Claim was once true but code has changed</meaning>
|
|
<requires>Current behavior</requires>
|
|
</status>
|
|
<status name="MISSING_CONTEXT">
|
|
<meaning>Claim is true but omits important information</meaning>
|
|
<requires>The missing context</requires>
|
|
</status>
|
|
<status name="UNVERIFIABLE">
|
|
<meaning>Cannot find code to verify this claim</meaning>
|
|
<requires>Search paths attempted</requires>
|
|
</status>
|
|
</verification_statuses>
|
|
|
|
<claim_categories>
|
|
<category>behavior</category>
|
|
<category>configuration</category>
|
|
<category>constraint</category>
|
|
<category>error_handling</category>
|
|
<category>ui</category>
|
|
<category>integration</category>
|
|
<category>prerequisite</category>
|
|
</claim_categories>
|
|
|
|
<rules>
|
|
<rule>Verify facts, not writing quality</rule>
|
|
<rule>Report what code does, not what docs should say</rule>
|
|
<rule>Include source file paths as evidence</rule>
|
|
<rule>Do NOT suggest documentation rewrites</rule>
|
|
<rule>Do NOT evaluate if docs are "good" - only if they're accurate</rule>
|
|
<rule>Quote exact code when showing discrepancies</rule>
|
|
</rules>
|
|
</verification_workflow> |