
Claude Skills by kenmulford
github.com/kenmulfordThis skill should be used when "milestone-driver:setup" is invoked directly, OR auto-invoked by solve-issue/solve-milestone when the driver profile is absent or missing a required Core key (`integrationBranch`, `protectedBranch`, or `sourceGlobs`). Guides an interactive first-run bootstrap that infers every profile key from repo signals, presents detected defaults with plain-language descriptions, lets the user accept/edit/skip optional keys (stating each skip-consequence), migrates a legacy ...
This skill should be used when the user invokes "/milestone-driver:solve-issue <n>", or asks to "solve issue <n>", "fix issue <n>", or "drive issue <n>" through the milestone-driver gated procedure. Runs one GitHub issue end-to-end as an orchestrator - triage, root-cause-or-park, dispatch the implementer subagent (TDD, citations), unit + E2E gates, code review, PR to the integration branch, auto-merge on CI green, then close - never authoring application or test code on the main thread.
This skill should be used when the user invokes "/milestone-driver:solve-milestone <name>", or asks to "solve a milestone", "drive a milestone", or "work the milestone autonomously". Iterates every issue in a GitHub milestone in dependency order via /milestone-driver:solve-issue, re-syncing the integration branch between issues. Runs unattended: parks blocked or gapped issues and continues; only a systemic failure ends a run early. Builds mutually-independent issues within a Wave concurrently...
This skill should be used when the user invokes "/milestone-driver:triage <milestone-name | issue-number>", or asks to "triage the milestone/issue", "triage the milestone", "review for gaps", or "review this issue for gaps". Reviews issues for design gaps and dependency ordering before building - the Layer 0 pre-build phase. Authors no code; opens no PRs.
Demo skill that does things
Folded · skill description here
Uses `x. y` inside then done. Tail here
Fixture stand-in for skills/setup/SKILL.md.
An H1 precedes the first level-2 heading here. The scan ignores level-1 lines entirely, so an H1 neither satisfies nor breaks the rule.
Fixture stand-in for skills/solve-milestone/SKILL.md.
Fixture stand-in for skills/triage/SKILL.md.
Fixture stand-in for skills/setup/SKILL.md.
An H1 precedes the first level-2 heading here. The scan ignores level-1 lines entirely, so an H1 neither satisfies nor breaks the rule.
Fixture stand-in for skills/solve-milestone/SKILL.md.
Fixture stand-in for skills/triage/SKILL.md.
Fixture stand-in for skills/setup/SKILL.md.
An H1 precedes the first level-2 heading here. The scan ignores level-1 lines entirely, so an H1 neither satisfies nor breaks the rule.
Fixture stand-in for skills/solve-milestone/SKILL.md.
Fixture stand-in for skills/triage/SKILL.md.
Fixture stand-in for skills/setup/SKILL.md.
An H1 precedes the first level-2 heading here. The scan ignores level-1 lines entirely, so an H1 neither satisfies nor breaks the rule.
Fixture stand-in for skills/solve-milestone/SKILL.md.
Fixture stand-in for skills/setup/SKILL.md.
An H1 precedes the first level-2 heading here. The scan ignores level-1 lines entirely, so an H1 neither satisfies nor breaks the rule.
Fixture stand-in for skills/solve-milestone/SKILL.md.
Fixture stand-in for skills/triage/SKILL.md.
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler
filler