Claude Skills by crenshawdev

Initialize .planning/ from a repo that already exists - PROJECT.md, REQUIREMENTS.md and a remaining-work ROADMAP.md derived from the code and the git history

Internal role contract, preloaded into every cad-assumptions-analyzer rung agent. Not a user command.

Pre-ship traceability audit - every requirement traced to a phase, plan and verification, orphan detection both directions, a FAIL gate before shipping

Capture a phase-linked todo, a seed idea for a future milestone, or a note, without losing your place - .planning/CAPTURE.md, or --cadence for friction with Cadence itself

Configure Cadence's config.json - workflow toggles, routing stakes, and interactive cross-model review provider setup

Gather phase context before planning - codebase assumptions, locked decisions, falsifiable acceptance criteria - in one pass

Find a completed phase's requirements with no failing-capable test coverage and generate tests to close the gaps, in the project's own framework

Systematic debugging - hypothesis and symptom tracked in a state file that survives /clear, with a user-gated second-model consult at dead ends

Adversarial refute-then-adjudicate pass over one load-bearing decision - a CONTEXT D-NN line or a PROJECT Key Decisions row - with per-objection rulings

Verify docs claims against the live codebase - paths, commands, symbols, config keys - each reported accurate, stale or unverifiable. Reports; it does not rewrite docs

Execute a phase's plans - a subagent per plan, an atomic commit per task, a slim per-phase SUMMARY

Internal role contract, preloaded into every cad-executor rung agent. Not a user command.

Planning-health check - .planning's core docs present, the STATE cursor, ROADMAP and REQUIREMENTS parseable and consistent. Not a traceability audit (that is /cad-audit)

Cadence's own help - the command reference for every /cad-* skill, grouped by cluster; pass a command name for just that entry

Land finished work - report git state, then ask the mechanism (push / MR or PR / tag / leave local). Never decides how you publish

Cut a milestone - audit that nothing was dropped, tag when the project tags, prune completed phases from the roadmap, evolve PROJECT and refresh REQUIREMENTS

Ranked delete-list over code that works and should not exist - reinvented stdlib, one-implementation abstractions, dead flexibility, config nobody sets

Initialize a project through deep questioning - PROJECT.md, REQUIREMENTS.md, a phased ROADMAP.md and .planning/ state

Pause work cleanly - a WIP commit of in-flight changes plus a STATE cursor set to paused with a one-line resume pointer (/cad-progress offers to resume it)

CRUD phases in ROADMAP - add, insert, remove, edit, with remove/insert renumbering the following phases, their .planning dirs and every phase reference

Internal role contract, preloaded into every cad-plan-checker rung agent. Not a user command.

On-demand adversarial plan review of a phase PLAN.md before code - for a hand-written, imported or just-edited plan (/cad-plan fires this itself)

Create an executable phase plan (PLAN.md) - planner subagent, optional check gate, plan review trigger

Internal role contract, preloaded into every cad-planner rung agent. Not a user command.

Project progress - count-based status from files and git, finds incomplete or paused work and offers to resume it, --stats for a quick summary

Render a phase's run record as a receipts narrative - what each dispatch cost, what the gates caught, what got refuted - straight from trace.jsonl and the phase artifacts

Internal role contract, preloaded into every cad-reviewer rung agent. Not a user command.

Spike - a time-boxed experiment resolving one unknown before you bet on it, risk-first, with a validated | invalidated | inconclusive verdict

Turn the run record into evidence-backed retune suggestions - each with its config key, the value in force, a direction and a target - and offer to route the ones you accept to /cad-config

Execute a small off-roadmap task with atomic commits - inline by default, --plan for multi-step work

Safely undo a phase - roll back its commits from the SUMMARY manifest, revert (or --no-commit to re-do), and reset the phase status

Internal role contract, preloaded into every cad-verifier rung agent. Not a user command.

Verify a completed phase by conversational UAT - a persistent checklist that survives /clear, plus cross-phase and goal-backward passes

Why is this code like this - a git-log chain over one file[:line], joined to the phase, task, decision, deviation and review record on disk