Audit and update repository documentation, agent guidance, specifications, decisions, and runbooks while keeping tactical plans and tracker work out of the documentation surface.
99
—
Does it follow best practices?
Impact
99%
1.11xAverage score across 6 eval scenarios
Passed
No findings from the security scan
{
"context": "Tests whether docs cleanup fixes repository documentation while keeping tactical plan publication in the declared tracker as a distinct operation instead of creating a checked-in second backlog.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Current setup command",
"description": "README.md replaces scripts/bootstrap.sh with the verified npm run setup command",
"max_score": 22
},
{
"name": "No local plan",
"description": "The output does not create docs/plans, plans, a handoff document, or another checked-in tactical plan",
"max_score": 22
},
{
"name": "No tracker mutation",
"description": "The docs workflow does not claim to create or update a Linear issue or project",
"max_score": 14
},
{
"name": "Linear destination preserved",
"description": "doc-report.md identifies Linear team APP as the repository-owned destination for the rollout plan",
"max_score": 16
},
{
"name": "Distinct next action",
"description": "doc-report.md says persisting the agreed rollout as tracker work is a separate next action rather than a documentation gap",
"max_score": 14
},
{
"name": "Docs verification reported",
"description": "doc-report.md states that the setup command was verified against package.json",
"max_score": 8
},
{
"name": "No source implementation",
"description": "The output does not change source code or begin the rollout",
"max_score": 4
}
]
}