A Claude Code plugin for intent-driven development: brainstorm, design, plan, execute
Skill Claude CodeCodex
Repo-local docs-maintenance dev skill for the Cadence documentation site (the Starlight project in website/). NOT a distributed plugin skill — it never ships to Cadence users. A thin dispatcher that routes to one of three self-contained actions: drift-check (semantically compare each reference page against its source…
Skill Claude CodeCodex
User-facing standalone skill that audits a plan against the codebase. Reads basesha: from the plan's overview frontmatter to compute the diff range. Dispatches cadence-completion-auditor agent which fans out per-audit sub-agents in parallel and synthesizes results. /c-execute does NOT route through this skill — it…
Skill Claude CodeCodex
Interactive Q&A — works in two modes. Thought-partner mode explores an idea conversationally with no artifact required. Design-brainstorm mode converges on an approach and writes a 00-overview.md stub under /{yyyy-mm-dd-slug}/. Same Q&A discipline in both modes (one question, options with a Recommended pick, advisor…
Skill Claude CodeCodex
Substance review of an existing design or plan. Reads doc(s); reports on accuracy, internal consistency, completeness, hidden assumptions, contradictions, scope creep. Does NOT review code quality (that's /c-find-bugs) but narrowly verifies plan-cited paths/symbols/imports exist in the codebase. Default: substance…
Skill Claude CodeCodex
Takes a 00-overview.md stub from /c-brainstorm and materializes the full design folder (child docs in reading order, plain-English narrative, optional 97/98 sections, OOS shell). Generation modes: all-at-once (parallel generators, the default), one-by-one (write, pause for review, repeat), or inline (main session…
Skill Claude CodeCodex
Drives a draft-status plan to implemented. PM-and-sub-agent model — user's main session is the PM; fresh cadence-implementer per task; DAG-scheduled parallel lanes per Depends: edges with a Touches: conflict guard; two-stage review (cadence-spec-reviewer then cadence-code-reviewer, spec wins on conflicts); records…
Skill Claude CodeCodex
Interactive discussion of an existing design or plan — opens with a one-screen orientation (section list + plain-English summaries) then drops into open user-driven Q&A. Answers lead with plain English; cite both design sections and code locations when implementation comes up. Gaps trigger investigation (design → code…
Skill Claude CodeCodex
Concrete defect hunting on a target. Operates on docs OR code. Different lens from /c-check ("is this good?"); this asks "what specific defects exist?" Targets: design folder, plan folder, branch, file, or --repo. Repo scope is token-heavy and requires explicit confirmation before starting. Output is a prioritized…
Skill Claude CodeCodex
Takes an approved design and writes an AI-readable plan folder with the same slug. Plans are exact paths, exact diffs, exact commands — no narrative. One design always becomes one plan; phase docs handle decomposition. Bidirectional linkage: writes linkeddesign: on the new plan and linkedplan: (singular) on the…
Skill Claude CodeCodex
Walks a plan's 96-validation.md post-deploy. Category C (prereqs) first, then A (automated), then B (manual workflow). Checks off items as it walks. Flips plan status to completed on full pass. Reads linkeddesign: and offers to flip the design to completed (user confirms).
Skill Claude CodeCodex
Full git-worktree lifecycle for isolated interactive sessions — create an isolated worktree, optionally run its dev server on a dedicated port, ship the branch home by local merge or by GitHub PR, and clean up. Generic and standalone: works in any git repo with no Cadence design, plan, or other /c- skill; local merges…