sdd

Plugin sdd from marketplace sdd in AshDevFr/claude-plugin-sdd. Commands read from the repo's manifest — 1 month ago.

Skills (12)

• dashboard-upkeep

  How to keep a project's live dashboard honest, what each hand-written section must say, when to regenerate, and where captures and mockups go. Use after starting a dashboard with /sdd:dashboard, after every task commit in a project that has one, and when publishing screenshots or mockups for the own

• finishing-work

  What to do with a branch once the work on it is done: merge, propose, or throw it away, what must be true before any of them, and how to bring a spec-repo worktree branch back. Use when implementation is complete and tests pass, and when a sdd-worktree needs unwinding.

• improver

  Propose one small, evidence-backed edit to a command, skill or rules file, drawn from the central learnings stream and this project's own log, and gated on the eval suite. Use when either has entries worth acting on, or when asked to improve the workflow itself rather than a project.

• plan-template

  Canonical implementation plan template and usage guidance. Use when creating a structured implementation plan for a feature or initiative (e.g., from /sdd:plan), where the plan organizes work into multiple phases.

• practices

  The full spec-repo conventions: layout, the commit policy, where planning artifacts go, the fitness rubric deciding whether a change earns a spec and a task file, and the three worktree modes for giving an agent access to the spec tree. Use when setting up or reorganising a spec repo, when deciding

• project-overview

  Generate or refresh a comprehensive, human-readable project overview document by reading the codebase, implementation docs (PRD/specs/tasks), config, migrations, API surface, and frontend. The doc records git provenance (date, branch, commit, tag) in frontmatter so subsequent runs diff against the l

• receiving-review

  What to do with code review feedback, including feedback that is wrong: verify each finding against the code before acting, separate a defect from a preference, and say plainly when a finding does not hold. Use when receiving a review from a person, from a review agent, or from a tool, before implem

• resolve-task-paths

  Resolve PRD, specs directory, tasks directory, and task file pattern from command arguments or the project's CLAUDE.md `## Task Workflow` section. Use at the start of any task-workflow command (/sdd:generate-specs, /sdd:generate-tasks, /sdd:next-task, /sdd:implement-next-task) before reading or writ

• spec-template

  Canonical phase spec file template and usage guidance for the project task workflow. Use when generating per-phase spec files from a PRD (e.g., from /sdd:generate-specs).

• task-template

  Canonical task file template and usage guidance for the project task workflow. Use when creating, validating, or describing task files (e.g., from /sdd:generate-tasks or /sdd:next-task).

• test-first

  The failing-test-first loop in the detail the practice rules have no room for: the order, what each step proves, the expected failure at every stage, and the two ways the loop silently becomes worthless. Use when implementing a feature or a fix, before writing implementation code, and when deciding

• tidying-spec-repos

  Use when a project's nested spec repo (the gitignored `.specs/docs` tree) has drifted: finished plans still sitting in plans/ or planned/, status headers that lag the code, a stale INDEX.md, or link rot after files were renamed. Also for "clean up the specs", "move implemented plans", "archive finis

Slash commands (21)

• /sdd:analyze

  Check the spec tree against itself and report what disagrees, without editing anything

• /sdd:bootstrap

  Prepare the current project to work with this suite: Task Workflow keys and the grants it needs

• /sdd:brainstorm

  Turn an idea into a design you have approved, then hand it to the command that owns the document

• /sdd:bug

  Diagnose, repair and verify a reproducible bug, with the three duties kept apart

• /sdd:clarify

  Work an ambiguous document down to decisions, and record them where the next reader looks

• /sdd:commit-msg

  Generate a commit message from the current diff

• /sdd:converge

  Diff the spec repo's task files against the code and reconcile the drift

• /sdd:dashboard

  Start, check, refresh or stop the live project dashboard the owner reads from another machine

• /sdd:generate-specs

  Generate per-phase spec files from a PRD

• /sdd:generate-tasks

  Generate task files from a phase spec

• /sdd:handoff

  Capture what dies with this session, so the next one resumes instead of rediscovering

• /sdd:implement-next-task

  Find the next incomplete task and implement it

• /sdd:implement

  Work on a specific section from any project document

• /sdd:next-task

  Identify (or create) the next task to work on

• /sdd:plan

  Create a new structured implementation plan (interactive)

• /sdd:pr-msg

  Generate a PR title and description from an implementation plan file

• /sdd:preflight

  Check what this machine must provide for the suite to work, and repair what is safe

• /sdd:project-overview

  Generate or refresh a provenance-stamped project overview document

• /sdd:quick

  Record a fast-lane change in the spec repo, with no phase spec or task file

• /sdd:snapshot

  Record the practice metrics that are cheap to measure, as a dated file

• /sdd:spec-repo-init

  Create the nested .specs/ spec repo for this project

Hooks (7)

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/spec-repo-guard.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/hooks/verification-guard.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/emit-practice-rules.sh

• SessionStart

  ${CLAUDE_PLUGIN_ROOT}/hooks/check-spec-ignore.sh

• UserPromptSubmit

  ${CLAUDE_PLUGIN_ROOT}/hooks/capture-learning.sh

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/hooks/dashboard-refresh.sh

• SessionEnd

  ${CLAUDE_PLUGIN_ROOT}/hooks/dashboard-session-end.sh