cds-complete-milestone — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cds-complete-milestone (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<objective> Mark milestone {{version}} complete, archive to milestones/, and update ROADMAP.md and REQUIREMENTS.md.
Purpose: Create historical record of shipped version, archive milestone artifacts (roadmap + requirements), and prepare for next milestone. Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tagged. </objective>
<execution_context> Load these files NOW (before proceeding):
</execution_context>
<context> Project files:
.planning/ROADMAP.md.planning/REQUIREMENTS.md.planning/STATE.md.planning/PROJECT.mdUser input:
</context>
<process>
Follow complete-milestone.md workflow:
.planning/v{{version}}-MILESTONE-AUDIT.md/cds-audit-milestone firstgaps_found: recommend /cds-plan-milestone-gaps firstpassed: proceed to step 1 ## Pre-flight Check
{If no v{{version}}-MILESTONE-AUDIT.md:}
⚠ No milestone audit found. Run `/cds-audit-milestone` first to verify
requirements coverage, cross-phase integration, and E2E flows.
{If audit has gaps:}
⚠ Milestone audit found gaps. Run `/cds-plan-milestone-gaps` to create
phases that close the gaps, or proceed anyway to accept as tech debt.
{If audit passed:}
✓ Milestone audit passed. Proceeding with completion..planning/milestones/v{{version}}-ROADMAP.md.planning/milestones/v{{version}}-REQUIREMENTS.md.planning/REQUIREMENTS.md (fresh one created for next milestone)<details> (if v1.1+)chore: archive v{{version}} milestonegit tag -a v{{version}} -m "[milestone summary]"/cds-new-milestone — start next milestone (questioning → research → requirements → roadmap)</process>
<success_criteria>
.planning/milestones/v{{version}}-ROADMAP.md.planning/milestones/v{{version}}-REQUIREMENTS.md.planning/REQUIREMENTS.md deleted (fresh for next milestone)</success_criteria>
<critical_rules>
/cds-new-milestone which includes requirements definition</critical_rules>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.