cds-execute-phase — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited cds-execute-phase (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> Execute all plans in a phase using wave-based parallel execution.
Orchestrator stays lean: discover plans, analyze dependencies, group into waves, spawn subagents, collect results. Each subagent loads the full execute-plan context and handles its own plan.
Optional wave filter:
--wave N executes only Wave N for pacing, quota management, or staged rolloutFlag handling rule:
$ARGUMENTS$ARGUMENTS, treat it as inactiveContext budget: ~15% orchestrator, 100% fresh per subagent. </objective>
<execution_context> @$HOME/.claude/cds-workflow/workflows/execute-phase.md @$HOME/.claude/cds-workflow/references/ui-brand.md </execution_context>
<runtime_note> Copilot (VS Code): Use vscode_askquestions wherever this workflow calls AskUserQuestion. They are equivalent — vscode_askquestions is the VS Code Copilot implementation of the same interactive question API. </runtime_note>
<context> Phase: $ARGUMENTS
Available optional flags (documentation only — not automatically active):
--wave N — Execute only Wave N in the phase. Use when you want to pace execution or stay inside usage limits.--gaps-only — Execute only gap closure plans (plans with gap_closure: true in frontmatter). Use after verify-work creates fix plans.--interactive — Execute plans sequentially inline (no subagents) with user checkpoints between tasks. Lower token usage, pair-programming style. Best for small phases, bug fixes, and verification gaps.Active flags must be derived from `$ARGUMENTS`:
--wave N is active only if the literal --wave token is present in $ARGUMENTS--gaps-only is active only if the literal --gaps-only token is present in $ARGUMENTS--interactive is active only if the literal --interactive token is present in $ARGUMENTSContext files are resolved inside the workflow via gsd-tools init execute-phase and per-subagent <files_to_read> blocks. </context>
<process> Execute the execute-phase workflow from @$HOME/.claude/cds-workflow/workflows/execute-phase.md end-to-end. Preserve all workflow gates (wave execution, checkpoint handling, verification, state updates, routing). </process>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.