speckit-docguard-score
Skill1 starsChanged 3 days agoApache-2.0View on GitHub
Calculate CDD maturity score with multi-signal quality breakdown
In this repository28 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- autopilot-supervisorSkill
- reclaim-diskSkill
- speckit-analyzeSkill
- speckit-autopilotSkill
- speckit-bugfix-patchSkill
- speckit-bugfix-reportSkill
- speckit-bugfix-switchSkill
- speckit-bugfix-verifySkill
- speckit-checklistSkill
- speckit-clarifySkill
- speckit-constitutionSkill
- speckit-convergeSkill
- speckit-docguard-diagnoseSkill
- speckit-docguard-fixSkill
- speckit-docguard-generateSkill
- speckit-docguard-guardSkill
- speckit-docguard-reviewSkill
- speckit-implementSkill
- speckit-planSkill
- speckit-specifySkill
- speckit-tasksSkill
- speckit-taskstoissuesSkill
- speckit-tdd-planSkill
- speckit-tdd-runSkill
- speckit-tdd-setupSkill
- speckit-tdd-verifySkill
- visual-passSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Run DocGuard score on the current project:
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Docguard Score Skill
DocGuard Score
Calculate your project's Canonical-Driven Development maturity score (0-100) across 8 weighted categories.
User Input
$ARGUMENTS
Steps
- Run DocGuard score on the current project:
npx --yes docguard-cli@latest score $ARGUMENTS- Review the breakdown:
- Structure (25%) — required files present
- Doc Quality (20%) — docs have required sections
- Testing (15%) — test spec alignment
- Security (10%) — no hardcoded secrets
- Environment (10%) — env docs configured
- Drift (10%) — drift tracking discipline
- Changelog (5%) — changelog maintenance
- Architecture (5%) — layer boundary compliance
- For per-signal quality labels, add
--signals.
Grading
| Score | Grade | Status |
| 90-100 | A | Strong CDD compliance |
| 75-89 | B | Good, some gaps |
| 50-74 | C | Needs work |
| < 50 | D | Significant gaps |
Flags
--signals— Show multi-signal CJE composite breakdown with quality labels--tax— Show estimated maintenance effort--format json— Output as JSON
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

