draht

Loop-driven development discipline — run agents in cycles of work gated by deterministic checks until a stop condition is met. Use when work needs iteration until a measurable criterion holds, when designing retry or verification loops, when a task is too large for one context window, or when choosing between one-shot orchestration and a loop. Triggers on "loop", "iterate until", "keep going until", "run until it passes", "ralph loop", "long-running", or any moment the agent is about to retry work without a defined stop condition.

Cost-efficient model tiering — the advisor pattern (a cheap executor consults a stronger model rarely) and the orchestrator pattern (a strong model plans while cheaper workers execute). Use when choosing which model runs a session vs its subagents, when cost matters on long agentic work, or when the user mentions "Fable", "advisor", "model tiering", "token cost", "cheaper model", or asks which model should drive a workflow.

Draht command prompt wrapper for orchestrate-loop. Use when the user selects the Draht orchestrate-loop workflow or wants to run a verification-gated loop of fresh subagent iterations until a deterministic check passes.

Draht's Get Shit Done workflow — how to use /new-project, /discuss-phase, /plan-phase, /execute-phase, /verify-work, /next-milestone, /pause-work, /resume-work, /progress, /fix, /quick and the .planning/ directory structure to drive a project from idea to shipping. Use when the user asks how to plan work, structure a project, set up milestones, track progress, or wants to start using draht's workflow.

Draht's Get Shit Done workflow — how to use /new-project, /discuss-phase, /plan-phase, /execute-phase, /verify-work, /next-milestone, /pause-work, /resume-work, /progress, /fix, /quick and the .planning/ directory structure to drive a project from idea to shipping. Use when the user asks how to plan work, structure a project, set up milestones, track progress, or wants to start using draht's workflow.

Decompose work into atomic reasoning units before acting — state the logical component, validate independence, verify correctness. The discipline that opens every draht slash command. Use whenever planning, designing, refactoring, breaking down a feature, structuring a commit, or scoping work. Triggers on "plan", "decompose", "break down", "scope", "split", "atomic", "how should I structure", or any moment Codex is about to spawn many parallel changes without first carving the work into independently-verifiable units.

Four-phase systematic debugging — root cause investigation → pattern analysis → single-hypothesis testing → reproducing-test-first implementation. Use whenever investigating a bug, test failure, error, stack trace, regression, build break, or unexpected behaviour. Auto-triggers on phrases like "broken", "doesn't work", "failing", "error", "bug", "regression", "why is X", "what's wrong with". The same protocol that `/fix` enforces, available transversally.

Evidence before claims — before stating that work is done, fixed, passing, working, ready, complete, or successful, run the command that proves it and read the output. Triggers on language like "done", "fixed", "should work", "looks good", "passing", "ready to ship", "complete", or whenever Codex is about to assert positive state. Applies everywhere — feature work, bug fixes, refactors, infra, docs that depend on code state.

Decompose work into atomic reasoning units before acting — state the logical component, validate independence, verify correctness. The discipline that opens every draht slash command. Use whenever planning, designing, refactoring, breaking down a feature, structuring a commit, or scoping work. Triggers on "plan", "decompose", "break down", "scope", "split", "atomic", "how should I structure", or any moment Claude is about to spawn many parallel changes without first carving the work into independently-verifiable units.

Socratic ideation gate before any project work begins. Use when the user has a fuzzy idea, vague project intent, or asks "what should I build", "I'm thinking about X", "I want to make a Y" without a clear spec. Runs BEFORE /new-project, /init-project, or any code. Refuses to plan or code until the design has been refined through dialogue and written to .planning/specs/. Triggers on phrases like "brainstorm", "idea", "what about", "I'm thinking", "design", "should I", "help me figure out", "let's discuss".

Four-phase systematic debugging — root cause investigation → pattern analysis → single-hypothesis testing → reproducing-test-first implementation. Use whenever investigating a bug, test failure, error, stack trace, regression, build break, or unexpected behaviour. Auto-triggers on phrases like "broken", "doesn't work", "failing", "error", "bug", "regression", "why is X", "what's wrong with". The same protocol that `/fix` enforces, available transversally.

Evidence before claims — before stating that work is done, fixed, passing, working, ready, complete, or successful, run the command that proves it and read the output. Triggers on language like "done", "fixed", "should work", "looks good", "passing", "ready to ship", "complete", or whenever Claude is about to assert positive state. Applies everywhere — feature work, bug fixes, refactors, infra, docs that depend on code state.

Domain-driven design discipline — bounded contexts, ubiquitous language, aggregates, domain events, context maps, and how the .planning/DOMAIN.md file drives code structure and naming. Use whenever the user is modelling a new domain, extracting domain concepts from existing code, deciding where code should live, or naming things.

Test-driven development discipline — red→green→refactor cycle, commit conventions (red:, green:, refactor:), TDD cycle violations, reproducing tests before fixes, and how to write tests that actually drive design. Use whenever the user is writing code that has testable behaviour, fixing bugs, or asks about TDD.

Draht command prompt wrapper for atomic-commit. Use when the user selects the Draht atomic-commit workflow or asks to analyze uncommitted changes and create atomic conventional commits.

Draht command prompt wrapper for discuss-phase. Use when the user selects the Draht discuss-phase workflow or wants to capture implementation decisions before planning a phase.

Draht command prompt wrapper for execute-phase. Use when the user selects the Draht execute-phase workflow or wants to execute phase plans with atomic commits, TDD, and review gates.

Draht command prompt wrapper for fix. Use when the user selects the Draht fix workflow or wants systematic root-cause debugging with TDD discipline.

Draht command prompt wrapper for init-project. Use when the user selects the Draht init-project workflow or wants to initialize GSD planning for an existing codebase.

Draht command prompt wrapper for map-codebase. Use when the user selects the Draht map-codebase workflow or wants architecture, domain, and test strategy extracted from an existing codebase.

Draht command prompt wrapper for new-project. Use when the user selects the Draht new-project workflow or wants greenfield GSD planning from questioning through roadmap.

Draht command prompt wrapper for next-milestone. Use when the user selects the Draht next-milestone workflow or wants to plan the next milestone after all current phases are complete.

Draht command prompt wrapper for orchestrate. Use when the user selects the Draht orchestrate workflow or wants to decompose a task and coordinate specialist subagents.

Draht command prompt wrapper for pause-work. Use when the user selects the Draht pause-work workflow or wants to create a CONTINUE-HERE handoff document.

Draht command prompt wrapper for plan-phase. Use when the user selects the Draht plan-phase workflow or wants to create atomic execution plans for a roadmap phase.

Draht command prompt wrapper for progress. Use when the user selects the Draht progress workflow or wants current GSD project status.

Draht command prompt wrapper for quick. Use when the user selects the Draht quick workflow or wants to execute a small ad-hoc task with tracking and review discipline.

Draht command prompt wrapper for resume-work. Use when the user selects the Draht resume-work workflow or wants to resume from a CONTINUE-HERE handoff document.

Draht command prompt wrapper for review. Use when the user selects the Draht review workflow or wants code review and security audit of recent changes.

Draht command prompt wrapper for verify-work. Use when the user selects the Draht verify-work workflow or wants acceptance testing of completed phase work.