docguard-scorelisted

<!-- docguard:version: 0.34.9 --> # DocGuard Score Skill ## User Input ```text $ARGUMENTS ``` You **MUST** consider the user input before proceeding (if not empty). ## Goal Run DocGuard's CDD maturity scoring engine, analyze the category breakdown, identify highest-ROI improvements, and produce an actionable improvement roadmap showing projected score gains per fix. ## Execution Flow ### Step 1: Run Scoring Engine Execute both tools for comprehensive data: ```bash npx docguard-cli score 2>&1 npx docguard-cli guard 2>&1 ``` If in DocGuard dev environment: ```bash node cli/docguard.mjs score 2>&1 node cli/docguard.mjs guard 2>&1 ``` ### Step 2: Parse Score Breakdown Extract the category-level scores: | Category | Score | Weight | Points | Potential Gain | |----------|:-----:|:------:|:------:|:--------------:| | Structure | X% | ×25 | N | [25 - N] | | Doc Quality | X% | ×20 | N | [20 - N] | | Testing | X% | ×15 | N | [15 - N] | | Security | X% | ×10 | N | [10 - N] | | Environment | X% | ×10 | N | [10 - N] | | Drift | X% | ×10 | N | [10 - N] | | Changelog | X% | ×5 | N | [5 - N] | | Architecture | X% | ×5 | N | [5 - N] | Calculate `Potential Gain` for each category = (weight - current points). ### Step 3: Grade Classification | Grade | Score | Description | |-------|:-----:|------------| | A+ | 95-100 | Exemplary — production-grade documentation, CDD fully adopted | | A | 85-94 | Strong — minor improvements possible, CI-gate ready | | B | 70-84 | Good — document