cds-new-milestone 100/100

Is cds-new-milestone safe to install?

SaferSkills independently audited cds-new-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.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

vendor/cds-workflow/skills/cds-new-milestone/SKILL.md · 1 file

vendor/cds-workflow/skills/cds-new-milestone/SKILL.md1.7 KB · Markdown

name: cds-new-milestone

description: "Start a new milestone cycle — update PROJECT.md and route to requirements"

argument-hint: "[milestone name, e.g., 'v1.1 Notifications']"

allowed-tools:

- Read

- Write

- Bash

- Task

- AskUserQuestion

<objective> Start a new milestone: questioning → research (optional) → requirements → roadmap.

Brownfield equivalent of new-project. Project exists, PROJECT.md has history. Gathers "what's next", updates PROJECT.md, then runs requirements → roadmap cycle.

Creates/Updates:

.planning/PROJECT.md — updated with new milestone goals
.planning/research/ — domain research (optional, NEW features only)
.planning/REQUIREMENTS.md — scoped requirements for this milestone
.planning/ROADMAP.md — phase structure (continues numbering)
.planning/STATE.md — reset for new milestone

After: /cds-plan-phase [N] to start execution. </objective>

<execution_context> @$HOME/.claude/cds-workflow/workflows/new-milestone.md @$HOME/.claude/cds-workflow/references/questioning.md @$HOME/.claude/cds-workflow/references/ui-brand.md @$HOME/.claude/cds-workflow/templates/project.md @$HOME/.claude/cds-workflow/templates/requirements.md </execution_context>

<context> Milestone name: $ARGUMENTS (optional - will prompt if not provided)

Project and milestone context files are resolved inside the workflow (init new-milestone) and delegated via <files_to_read> blocks where subagents are used. </context>

<process> Execute the new-milestone workflow from @$HOME/.claude/cds-workflow/workflows/new-milestone.md end-to-end. Preserve all workflow gates (validation, questioning, research, requirements, roadmap approval, commits). </process>

cds-new-milestone— agent skill

Is cds-new-milestone safe to install?

Audit the pieces. Scan the whole. Decide.