A collection of slash commands, agent roles, and templates that extend Claude Code with structured development workflows.
- Skills (
/dtb:*) — German-language workflow system for session management, project documentation, feature planning, idea capture, and code review - Agent Roles — Reusable agent definitions (Architekt, Pragmatiker, Senior Dev, Betriebs-Waechter) for structured reviews
- Commands — Slash-command definitions for workflow shortcuts (none shipped currently)
- Project Settings — Pre-configured permissions and plugin setup
Das Kit installiert sich selbst und haelt sich aktuell — ueber eine Lock-Datei
(~/.claude/dtb-lock.json) mit Content-Hashes pro Artefakt (Drift-Erkennung
Repo ↔ installierte Kopie).
# 1. Bootstrap: den kit-sync-Skill einmalig manuell installieren
git clone https://github.com/spyrad/claude-code-workflow-kit.git
mkdir -p ~/.claude/skills/dtb-kit-sync
cp claude-code-workflow-kit/skills/dtb-kit-sync/SKILL.md ~/.claude/skills/dtb-kit-sync/
# 2. In Claude Code (beliebiges Verzeichnis):
# /dtb:kit-sync install
# → installiert Skills, Agents und Commands global nach ~/.claude/,
# adoptiert vorhandene Kopien und erzeugt ~/.claude/dtb-lock.json
# 3. Pro Projekt initialisieren:
# cd <dein-projekt> → /dtb:project-init
# → Scaffolding, workflow.config.yaml, Regel-Datei, CLAUDE.md-Block (Sentinel-Marker)Updates spaeter: /dtb:kit-sync check (Drift-Report) → /dtb:kit-sync sync
(kontrollierter Abgleich; lokal geaenderte Kopien werden nie stillschweigend
ueberschrieben). /dtb:project-health meldet Drift nebenbei als eigenen Check.
# Global (von Claude Code in allen Projekten geladen)
cp -r skills/* ~/.claude/skills/
cp -r agents/* ~/.claude/agents/
cp -r commands/* ~/.claude/commands/
# Optional: Settings ins Zielprojekt
cp settings.json <dein-projekt>/.claude/settings.json
# Pro Projekt initialisieren (verteilt auch die Statusableitungs-Regeln)
cd <dein-projekt>
# /dtb:project-init ausfuehren- Skills werden von Claude Code automatisch erkannt
- Aufruf per Slash-Command (
/dtb:idea) oder natuerliche Sprache ("Session speichern") /dtb:project-initist der erste Schritt — danach sind alle anderen Skills einsatzbereit
| Skill | Purpose |
|---|---|
/dtb:workflow-checkpoint |
Log session progress + update status dashboard |
/dtb:workflow-resume |
Resume after a break |
/dtb:idea |
Quick-capture an idea into the inbox |
/dtb:idea-review |
Review and triage open ideas |
/dtb:bug-report |
Capture bug report with severity and reproduction steps |
/dtb:debug-plan |
Root-cause analysis and fix strategy for an existing bug |
/dtb:feature-discover |
Analyze idea, scan codebase, gather requirements before spec writing |
/dtb:feature-plan |
Create structured feature specifications (with inbox integration) |
/dtb:feature-start |
Start a planned feature from the backlog |
/dtb:impl-plan |
Create implementation plan from feature spec |
/dtb:plan-review |
Structured review with Architekt, Pragmatiker + Senior Dev agents |
/dtb:build-check |
Build verification |
/dtb:code-review |
Review code changes against project-specific rules |
/dtb:generate-rules |
Generate coding rules/guidelines from codebase analysis |
/dtb:workflow-status |
Pipeline visualization and queue analysis |
/dtb:workflow-next |
Show next concrete action per active feature |
/dtb:session-summary |
Compact recap of work done (active session, a given day, or last 7 days) |
/dtb:backlog-status |
Backlog overview |
/dtb:archive |
Archive completed/discarded items from workflow files |
/dtb:repo-sync |
Git status across configured project repos (not kit distribution) |
/dtb:kit-sync |
Install/update kit copies under ~/.claude/ with lock-based drift detection |
/dtb:project-init |
Initialize DTB workflow in a project |
/dtb:project-health |
Project linting and consistency checks |
/dtb:project-team |
Team documentation |
/dtb:opportunity-map |
Classify recurring friction into build/buy/complement/wait before building; recommends one candidate, writes OPPORTUNITY-MAP.md |
/dtb:greenfield-prd |
Two-mode: author PRD-MVP.md via a product interview when missing, else summarize it |
/dtb:greenfield-roadmap |
Two-mode: author ROADMAP.md (+TECH-STACK.md) from the PRD via a lean interview, else summarize it |
/dtb:docs-extract |
Scan input/ folder, extract facts from PDFs/docs, create thematic MDs |
/dtb:lesson |
Capture a reusable lesson append-only into lessons.md, read as a prior by plan/review skills |
/dtb:pipeline-graph |
Generate interactive HTML overview of entire skill pipeline |
Commands (commands/) are slash-command definitions for workflow shortcuts. They use YAML
frontmatter (description) and may pull files into context via @-references.
The kit currently ships no command. The commands/dtb-*.md class-A pattern stays registered in
dtb:kit-sync, so a newly added command is picked up and distributed without further setup.
Personas are not part of this kit. Role definitions that work with the human over an event
(a pitch, a kick-off) — as opposed to agent roles, which work on a code artifact — live in the
separate oma-personas repository. The kit carries only distillates of them: dtb:impl-review
embeds the principled and torvalds reviewer lenses inline as evaluation criteria, without voice
or persona identity.
Install commands by copying into the target project's .claude/ directory:
cp -r commands/* <dein-projekt>/.claude/commands/skills/ # Skill definitions (primary — auto-detected by Claude Code)
agents/ # Reusable agent role definitions (work on code artifacts)
commands/ # Slash-command definitions (workflow shortcuts — none shipped currently)
workflow.config.yaml # Project-specific config (template — filled by /dtb:project-init)
settings.json # Claude Code project settings
CLAUDE.md # Project instructions for Claude Code
- Skills and documentation are in German; code and file names are in English
- Skills are markdown-based prompt templates with YAML frontmatter, not executable code
- Skills support natural language triggers (e.g. "Session speichern" activates
dtb:workflow-checkpoint) - Generated session data goes to
dtb-project/(gitignored) - Derived State: feature status is derived from artifacts (
## Progresscheckboxes inPLAN_*.md), not maintained in status fields — rules indtb-project/project-rules/DERIVED_STATE_RULES.md
MIT