@draht/coding-agent 2026.3.4 → 2026.3.5

package/hooks/gsd/draht-quality-gate.js

@@ -12,13 +12,67 @@
 
 const { execSync } = require("node:child_process");
 const fs = require("node:fs");
+const path = require("node:path");
 
-const strict = process.argv.includes("--strict");
+// ── Toolchain detection — mirrors src/gsd/hook-utils.ts ──────────────────────
+function detectToolchain(cwd) {
+	if (fs.existsSync(path.join(cwd, "bun.lockb")) || fs.existsSync(path.join(cwd, "bun.lock"))) {
+		return { pm: "bun", testCmd: "bun test", coverageCmd: "bun test --coverage", lintCmd: "bunx biome check ." };
+	}
+	if (fs.existsSync(path.join(cwd, "pnpm-lock.yaml"))) {
+		return { pm: "pnpm", testCmd: "pnpm test", coverageCmd: "pnpm run test:coverage", lintCmd: "pnpm run lint" };
+	}
+	if (fs.existsSync(path.join(cwd, "yarn.lock"))) {
+		return { pm: "yarn", testCmd: "yarn test", coverageCmd: "yarn run test:coverage", lintCmd: "yarn run lint" };
+	}
+	return { pm: "npm", testCmd: "npm test", coverageCmd: "npm run test:coverage", lintCmd: "npm run lint" };
+}
+
+function readHookConfig(cwd) {
+	const defaults = { coverageThreshold: 80, tddMode: "advisory", qualityGateStrict: false };
+	const configPath = path.join(cwd, ".planning", "config.json");
+	if (!fs.existsSync(configPath)) return defaults;
+	try {
+		const raw = JSON.parse(fs.readFileSync(configPath, "utf-8"));
+		const h = raw.hooks || {};
+		return {
+			coverageThreshold: typeof h.coverageThreshold === "number" ? h.coverageThreshold : defaults.coverageThreshold,
+			tddMode: h.tddMode === "strict" || h.tddMode === "advisory" ? h.tddMode : defaults.tddMode,
+			qualityGateStrict: typeof h.qualityGateStrict === "boolean" ? h.qualityGateStrict : defaults.qualityGateStrict,
+		};
+	} catch { return defaults; }
+}
+
+// Inline domain validator — mirrors src/gsd/domain-validator.ts
+function extractGlossaryTerms(content) {
+	const terms = new Set();
+	const sectionMatch = content.match(/## Ubiquitous Language([\s\S]*?)(?:\n## |$)/);
+	const section = sectionMatch ? sectionMatch[1] : content;
+	for (const m of section.matchAll(/\*\*([A-Z][a-zA-Z0-9]+)\*\*/g)) terms.add(m[1]);
+	for (const m of section.matchAll(/^[-*]\s+([A-Z][a-zA-Z0-9]+)\s*:/gm)) terms.add(m[1]);
+	for (const m of section.matchAll(/\|\s*([A-Z][a-zA-Z0-9]+)\s*\|/g)) terms.add(m[1]);
+	return terms;
+}
+
+function loadDomainContent(cwd) {
+	const modelPath = path.join(cwd, ".planning", "DOMAIN-MODEL.md");
+	if (fs.existsSync(modelPath)) return fs.readFileSync(modelPath, "utf-8");
+	const domainPath = path.join(cwd, ".planning", "DOMAIN.md");
+	if (fs.existsSync(domainPath)) return fs.readFileSync(domainPath, "utf-8");
+	return "";
+}
+
+// ── Main ──────────────────────────────────────────────────────────────────────
+const cwd = process.cwd();
+const toolchain = detectToolchain(cwd);
+const hookConfig = readHookConfig(cwd);
+const strict = process.argv.includes("--strict") || hookConfig.qualityGateStrict;
 const issues = [];
 
 // 1. TypeScript check
 try {
-	execSync("bun run tsgo --noEmit 2>&1", { timeout: 60000, encoding: "utf-8" });
+	const tsCmd = toolchain.pm === "bun" ? "bun run tsgo --noEmit 2>&1" : "npx tsc --noEmit 2>&1";
+	execSync(tsCmd, { timeout: 60000, encoding: "utf-8", cwd });
 } catch (error) {
 	const output = error.stdout || error.stderr || "";
 	const errorCount = (output.match(/error TS/g) || []).length;
@@ -27,19 +81,19 @@ try {
 	}
 }
 
-// 2. Biome lint check (if biome.json exists)
-if (fs.existsSync("biome.json")) {
+// 2. Lint check (if biome.json exists use biome, else use toolchain lint)
+if (fs.existsSync(path.join(cwd, "biome.json"))) {
 	try {
-		execSync("bunx biome check --error-on-warnings . 2>&1", { timeout: 30000, encoding: "utf-8" });
+		execSync(`${toolchain.lintCmd} --error-on-warnings 2>&1`, { timeout: 30000, encoding: "utf-8", cwd });
 	} catch (error) {
 		const output = error.stdout || error.stderr || "";
-		issues.push({ severity: strict ? "error" : "warning", message: "Biome lint issues", details: output.slice(0, 500) });
+		issues.push({ severity: strict ? "error" : "warning", message: "Lint issues", details: output.slice(0, 500) });
 	}
 }
 
 // 3. Run tests
 try {
-	const testOutput = execSync("bun test 2>&1", { timeout: 120000, encoding: "utf-8" });
+	const testOutput = execSync(`${toolchain.testCmd} 2>&1`, { timeout: 120000, encoding: "utf-8", cwd });
 	const failMatch = testOutput.match(/(\d+) fail/);
 	if (failMatch && parseInt(failMatch[1], 10) > 0) {
 		issues.push({ severity: strict ? "error" : "warning", message: `${failMatch[1]} test(s) failing` });
@@ -56,71 +110,56 @@ try {
 try {
 	const result = execSync(
 		"grep -rn 'console\\.log' src/ --include='*.ts' --include='*.tsx' 2>/dev/null | grep -v '// debug' | head -5",
-		{ encoding: "utf-8" }
+		{ encoding: "utf-8", cwd }
 	).trim();
 	if (result) {
-		issues.push({ severity: "warning", message: `console.log found in source`, details: result });
+		issues.push({ severity: "warning", message: "console.log found in source", details: result });
 	}
-} catch { /* grep returns 1 when no match — that's good */ }
+} catch { /* grep returns 1 when no match — that's fine */ }
 
-// 5. Domain glossary compliance
-// Extract terms from DOMAIN.md and flag new PascalCase classes not in the glossary
-const domainMdPath = ".planning/DOMAIN.md";
-if (fs.existsSync(domainMdPath)) {
+// 5. Domain glossary compliance (checks DOMAIN-MODEL.md, falls back to DOMAIN.md)
+const domainContent = loadDomainContent(cwd);
+if (domainContent) {
 	try {
-		const domainContent = fs.readFileSync(domainMdPath, "utf-8");
-		// Collect all PascalCase tokens that appear in the glossary section
-		const glossarySection = domainContent.match(/## Ubiquitous Language([\s\S]*?)(?:^##|\Z)/m)?.[1] || "";
-		// Each glossary entry is assumed to start the line with a PascalCase term (e.g. "**Order**" or "- Order:")
-		const glossaryTerms = new Set(
-			[...glossarySection.matchAll(/\b([A-Z][a-zA-Z0-9]+)\b/g)].map((m) => m[1])
-		);
-
-		// Scan changed source files for PascalCase class/interface/type declarations
-		try {
-			const changedFiles = execSync(
-				"git diff --cached --name-only 2>/dev/null || git diff --name-only HEAD~1",
-				{ encoding: "utf-8" }
-			).trim().split("\n").filter((f) => f.endsWith(".ts") || f.endsWith(".tsx"));
-
-			const unknownTerms = [];
-			for (const file of changedFiles) {
-				if (!fs.existsSync(file)) continue;
-				const src = fs.readFileSync(file, "utf-8");
-				const declarations = [...src.matchAll(/(?:class|interface|type|enum)\s+([A-Z][a-zA-Z0-9]+)/g)].map((m) => m[1]);
-				for (const term of declarations) {
-					if (!glossaryTerms.has(term)) {
-						unknownTerms.push(`${file}: ${term}`);
-					}
-				}
+		const glossaryTerms = extractGlossaryTerms(domainContent);
+		const changedFiles = execSync(
+			"git diff --cached --name-only 2>/dev/null || git diff --name-only HEAD~1",
+			{ encoding: "utf-8", cwd }
+		).trim().split("\n").filter((f) => f.endsWith(".ts") || f.endsWith(".tsx"));
+
+		const unknownTerms = [];
+		for (const file of changedFiles) {
+			if (!fs.existsSync(path.join(cwd, file))) continue;
+			const src = fs.readFileSync(path.join(cwd, file), "utf-8");
+			const declarations = [...src.matchAll(/(?:class|interface|type|enum)\s+([A-Z][a-zA-Z0-9]+)/g)].map((m) => m[1]);
+			for (const term of declarations) {
+				if (!glossaryTerms.has(term)) unknownTerms.push(`${file}: ${term}`);
 			}
-			if (unknownTerms.length > 0) {
-				issues.push({
-					severity: "warning",
-					message: `${unknownTerms.length} PascalCase type(s) not in DOMAIN.md glossary`,
-					details: unknownTerms.slice(0, 5).join(", "),
-				});
-			}
-		} catch { /* ignore git errors */ }
-	} catch { /* ignore read errors */ }
+		}
+		if (unknownTerms.length > 0) {
+			issues.push({
+				severity: hookConfig.tddMode === "strict" ? "error" : "warning",
+				message: `${unknownTerms.length} PascalCase type(s) not in domain glossary (DOMAIN-MODEL.md)`,
+				details: unknownTerms.slice(0, 5).join(", "),
+			});
+		}
+	} catch { /* ignore */ }
 }
 
 // 6. Bounded context boundary check — flag suspicious cross-directory imports
 try {
 	const changedSrcFiles = execSync(
 		"git diff --cached --name-only 2>/dev/null || git diff --name-only HEAD~1",
-		{ encoding: "utf-8" }
+		{ encoding: "utf-8", cwd }
 	).trim().split("\n").filter((f) => /^src\/[^/]+\//.test(f) && (f.endsWith(".ts") || f.endsWith(".tsx")));
 
 	const crossContextImports = [];
 	for (const file of changedSrcFiles) {
-		if (!fs.existsSync(file)) continue;
-		// Determine this file's context (first path segment under src/)
+		if (!fs.existsSync(path.join(cwd, file))) continue;
 		const ownContext = file.split("/")[1];
-		const src = fs.readFileSync(file, "utf-8");
+		const src = fs.readFileSync(path.join(cwd, file), "utf-8");
 		const imports = [...src.matchAll(/from\s+['"](\.\.\/.+?)['"]/g)].map((m) => m[1]);
 		for (const imp of imports) {
-			// Resolve relative import against the file's directory
 			const resolved = path.normalize(path.join(path.dirname(file), imp));
 			const parts = resolved.split(path.sep);
 			const srcIdx = parts.indexOf("src");
@@ -142,11 +181,11 @@ try {
 try {
 	const allSrc = execSync(
 		"find src -name '*.ts' -not -name '*.test.ts' -not -name '*.spec.ts' 2>/dev/null | wc -l",
-		{ encoding: "utf-8" }
+		{ encoding: "utf-8", cwd }
 	).trim();
 	const allTests = execSync(
 		"find src -name '*.test.ts' -o -name '*.spec.ts' 2>/dev/null | wc -l",
-		{ encoding: "utf-8" }
+		{ encoding: "utf-8", cwd }
 	).trim();
 	const srcCount = parseInt(allSrc, 10) || 0;
 	const testCount = parseInt(allTests, 10) || 0;
@@ -163,12 +202,15 @@ try {
 
 // 8. Check for TODO/FIXME/HACK comments in changed files
 try {
-	const diff = execSync("git diff --cached --name-only 2>/dev/null || git diff --name-only HEAD~1", { encoding: "utf-8" }).trim();
+	const diff = execSync(
+		"git diff --cached --name-only 2>/dev/null || git diff --name-only HEAD~1",
+		{ encoding: "utf-8", cwd }
+	).trim();
 	if (diff) {
 		const files = diff.split("\n").filter((f) => f.endsWith(".ts") || f.endsWith(".tsx"));
 		for (const file of files) {
 			try {
-				const content = fs.readFileSync(file, "utf-8");
+				const content = fs.readFileSync(path.join(cwd, file), "utf-8");
 				const todos = content.match(/\/\/\s*(TODO|FIXME|HACK|XXX):/gi) || [];
 				if (todos.length > 0) {
 					issues.push({ severity: "info", message: `${file}: ${todos.length} TODO/FIXME comment(s)` });

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@draht/coding-agent",
-	"version": "2026.3.4",
+	"version": "2026.3.5",
 	"description": "Coding agent CLI with read, bash, edit, write tools and session management",
 	"type": "module",
 	"drahtConfig": {
@@ -46,9 +46,9 @@
 	},
 	"dependencies": {
 		"@mariozechner/jiti": "^2.6.2",
-		"@draht/agent-core": "2026.3.4",
-		"@draht/ai": "2026.3.4",
-		"@draht/tui": "2026.3.4",
+		"@draht/agent-core": "2026.3.5",
+		"@draht/ai": "2026.3.5",
+		"@draht/tui": "2026.3.5",
 		"@silvia-odwyer/photon-node": "^0.3.4",
 		"chalk": "^5.5.0",
 		"cli-highlight": "^2.1.11",
@@ -92,7 +92,7 @@
 		"tui",
 		"agent"
 	],
-	"author": "Mario Zechner",
+	"author": "Oskar Freye",
 	"license": "MIT",
 	"publishConfig": {
 		"access": "public"

package/prompts/agents/build.md

@@ -1,6 +1,10 @@
+---
+description: "Execution agent that implements plans precisely"
+---
+
 # Draht Build Agent
 
-You are an execution agent for the Get Shit Done methodology. Your job is to implement plans precisely.
+You are an execution agent. Your job is to implement plans precisely.
 
 ## Core Rules
 1. Read the plan FIRST — it is your instruction set

package/prompts/agents/plan.md

@@ -1,6 +1,10 @@
+---
+description: "Planning agent that creates atomic, executable plans"
+---
+
 # Draht Plan Agent
 
-You are a planning agent for the Get Shit Done methodology. Your job is to create atomic, executable plans.
+You are a planning agent. Your job is to create atomic, executable plans.
 
 ## Core Rules
 1. Plans are prompts — they tell the executor EXACTLY what to build

package/prompts/agents/verify.md

@@ -1,6 +1,10 @@
+---
+description: "Verification agent that tests work against acceptance criteria"
+---
+
 # Draht Verify Agent
 
-You are a verification agent for the Get Shit Done methodology. Your job is to test completed work against acceptance criteria.
+You are a verification agent. Your job is to test completed work against acceptance criteria.
 
 ## Core Rules
 1. Test from the USER's perspective, not the developer's

package/prompts/commands/atomic-commit.md

@@ -4,19 +4,13 @@ description: "Analyze changes and create atomic commits"
 
 # Git Atomic Commit Analysis
 
-First, check the current status:
+First, gather the current state:
 
-*! git status*
+1. Run `git status` to see what changed
+2. Run `git diff` to see unstaged changes
+3. Run `git diff --cached` to see staged changes
 
-Now get the full diff of all changes:
-
-*! git diff*
-
-And staged changes:
-
-*! git diff --cached*
-
-Based on the changes shown above, analyze and group them into logical, ATOMIC commits. Each commit should:
+Based on the changes, analyze and group them into logical, ATOMIC commits. Each commit should:
 
 1. Contain ONE logical change only
 2. Be self-contained and complete
@@ -27,13 +21,11 @@ For each group of changes you identify:
 - Generate a clear, descriptive commit message following conventional commits format
 - Explain WHY these changes belong in one commit
 
-Then provide the exact `git add` and `git commit` commands to execute for each atomic commit in the order they should be applied.
+Then execute the `git add` and `git commit` commands for each atomic commit in the order they should be applied.
 
 Format each commit message as:
+```
 type(scope): brief description
-- Detailed explanation of what changed
-- Why the change was necessary
-
+```
 
 Common types: feat, fix, refactor, docs, test, chore, style, perf
-

package/prompts/commands/discuss-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Capture implementation decisions before planning a phase"
+---
+
 # /discuss-phase
 
 Capture implementation decisions before planning a phase.
@@ -7,13 +11,15 @@ Capture implementation decisions before planning a phase.
 /discuss-phase [N]
 ```
 
+Phase: $1
+
 ## Steps
-1. Run `draht-tools phase-info N` to load phase context
+1. Run `draht-tools phase-info $1` to load phase context
 2. Identify gray areas based on what's being built
 3. Present 1-2 questions at a time about preferences
 4. If `.planning/DOMAIN.md` exists, load it and validate discovered terms against the glossary. Add any new domain terms found during discussion.
-5. Record decisions with `draht-tools save-context N`
-6. Commit: `draht-tools commit-docs "capture phase N context"`
+5. Record decisions with `draht-tools save-context $1`
+6. Commit: `draht-tools commit-docs "capture phase $1 context"`
 
 ## Gray Area Categories
 - **Visual features** → Layout, density, interactions, empty states

package/prompts/commands/execute-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Execute all plans in a phase with atomic commits"
+---
+
 # /execute-phase
 
 Execute all plans in a phase with atomic commits.
@@ -7,37 +11,40 @@ Execute all plans in a phase with atomic commits.
 /execute-phase [N] [--gaps-only]
 ```
 
+Phase: $1
+Arguments: $ARGUMENTS
+
 ## Steps
-1. Run `draht-tools discover-plans N` to find and order plans
+1. Run `draht-tools discover-plans $1` to find and order plans
 2. For each plan in dependency order:
-   a. Load plan: `draht-tools read-plan N P`
+   a. Load plan: `draht-tools read-plan $1 P`
    b. Execute each task in strict TDD cycle:
 
       **🔴 RED — Write failing tests first**
       - Write the test cases from `<test>`
       - Run tests — confirm they FAIL (if they pass, the test is wrong)
-      - Commit failing tests: `draht-tools commit-task N P T "red: test description"`
+      - Commit failing tests: `draht-tools commit-task $1 P T "red: test description"`
 
       **🟢 GREEN — Minimal implementation**
       - Write the minimum code from `<action>` to make tests pass
       - Use domain language from `<context>` and `<domain>` for all names
       - Run tests — confirm they PASS
-      - Commit: `draht-tools commit-task N P T "green: task name"`
+      - Commit: `draht-tools commit-task $1 P T "green: task name"`
 
       **🔵 REFACTOR — Clean up with safety net**
       - Apply improvements from `<refactor>` (if any)
       - Run tests after each change — must stay green
       - Verify domain language compliance (names match DOMAIN.md)
-      - Commit: `draht-tools commit-task N P T "refactor: description"`
+      - Commit: `draht-tools commit-task $1 P T "refactor: description"`
 
       **✅ VERIFY**
       - Run the `<verify>` step
       - Confirm `<done>` criteria met
 
-   c. Write summary: `draht-tools write-summary N P`
-3. Phase verification: `draht-tools verify-phase N`
+   c. Write summary: `draht-tools write-summary $1 P`
+3. Phase verification: `draht-tools verify-phase $1`
 4. Update state: `draht-tools update-state`
-5. Final commit: `draht-tools commit-docs "complete phase N execution"`
+5. Final commit: `draht-tools commit-docs "complete phase $1 execution"`
 
 ## TDD Rules
 - Never write implementation before a failing test exists

package/prompts/commands/fix.md

@@ -1,3 +1,7 @@
+---
+description: "Diagnose and fix a bug with TDD discipline"
+---
+
 # /fix
 
 Diagnose and fix a specific bug or failing task with TDD discipline.
@@ -7,6 +11,8 @@ Diagnose and fix a specific bug or failing task with TDD discipline.
 /fix [description of what's broken]
 ```
 
+Issue: $ARGUMENTS
+
 ## Steps
 1. **Diagnose**: Read the relevant code and error output to identify the root cause
    - If a test is failing, run it first to see the actual error

package/prompts/commands/init-project.md

@@ -1,13 +1,19 @@
+---
+description: "Initialize planning for an existing project"
+---
+
 # /init-project
 
-Initialize GSD planning framework for an existing project: codebase mapping → questioning → domain model → requirements → roadmap.
+Initialize planning framework for an existing project: codebase mapping → questioning → domain model → requirements → roadmap.
 
 ## Usage
 ```
 /init-project [focus area or goal]
 ```
 
-Use this when you have an existing codebase and want to add GSD methodology.
+Focus: $ARGUMENTS
+
+Use this when you have an existing codebase and want to add structured planning.
 For greenfield projects, use `/new-project` instead.
 
 ## Steps
@@ -37,7 +43,7 @@ For greenfield projects, use `/new-project` instead.
 10. Run `draht-tools create-requirements` with v1/v2/out-of-scope (map requirements to bounded contexts)
 11. Run `draht-tools create-roadmap` with phases
 12. Run `draht-tools init-state`
-13. Git commit via `draht-tools commit-docs "initialize GSD planning"`
+13. Git commit via `draht-tools commit-docs "initialize project planning"`
 
 ## Rules
 - Ask 1-2 questions at a time, never dump 10 at once

package/prompts/commands/map-codebase.md

@@ -1,3 +1,7 @@
+---
+description: "Analyze existing codebase before planning"
+---
+
 # /map-codebase
 
 Analyze existing codebase before planning.
@@ -7,8 +11,10 @@ Analyze existing codebase before planning.
 /map-codebase [directory]
 ```
 
+Directory: $1
+
 ## Steps
-1. Run `draht-tools map-codebase [dir]`
+1. Run `draht-tools map-codebase $1`
 2. Tool generates: STACK.md, ARCHITECTURE.md, CONVENTIONS.md, CONCERNS.md
 3. Review output, supplement with your own analysis if needed
 4. Identify implicit bounded contexts from directory structure:

package/prompts/commands/new-project.md

@@ -1,12 +1,18 @@
+---
+description: "Initialize a new project with structured planning"
+---
+
 # /new-project
 
-Initialize a new GSD project: questioning → research → requirements → roadmap.
+Initialize a new project: questioning → research → requirements → roadmap.
 
 ## Usage
 ```
 /new-project [description]
 ```
 
+Description: $ARGUMENTS
+
 ## Steps
 1. Run `draht-tools init` to check preconditions
 2. If existing code detected, run `draht-tools map-codebase` first
@@ -29,7 +35,7 @@ Initialize a new GSD project: questioning → research → requirements → road
 9. Run `draht-tools create-requirements` with v1/v2/out-of-scope (map requirements to bounded contexts)
 10. Run `draht-tools create-roadmap` with phases
 11. Run `draht-tools init-state`
-12. Git commit via `draht-tools commit-docs "initialize GSD project"`
+12. Git commit via `draht-tools commit-docs "initialize project planning"`
 
 ## Rules
 - Ask 1-2 questions at a time, never dump 10 at once

package/prompts/commands/next-milestone.md

@@ -1,3 +1,7 @@
+---
+description: "Plan the next milestone after current one completes"
+---
+
 # /next-milestone
 
 Plan the next milestone after the current one is complete.

package/prompts/commands/pause-work.md

@@ -1,3 +1,7 @@
+---
+description: "Create a handoff document for session continuity"
+---
+
 # /pause-work
 
 Create a handoff document for session continuity.

package/prompts/commands/plan-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Create atomic execution plans for a roadmap phase"
+---
+
 # /plan-phase
 
 Create atomic execution plans for a roadmap phase.
@@ -7,18 +11,20 @@ Create atomic execution plans for a roadmap phase.
 /plan-phase [N]
 ```
 
+Phase: $1
+
 ## Steps
-1. Run `draht-tools load-phase-context N` to gather all context
-2. Optional: `draht-tools research-phase N` for domain research
+1. Run `draht-tools load-phase-context $1` to gather all context
+2. Optional: `draht-tools research-phase $1` for domain research
 3. Goal-backward planning:
    a. State the goal (outcome, not activity)
    b. Derive observable truths (3-7 from user perspective)
    c. From each observable truth, derive the test scenarios that would prove it (specific inputs → expected outputs or state changes)
    d. Map to required artifacts (files, endpoints, schemas)
    e. Break into atomic tasks (2-5 per plan)
-4. Write plans: `draht-tools create-plan N P`
-5. Validate: `draht-tools validate-plans N`
-6. Commit: `draht-tools commit-docs "create phase N plans"`
+4. Write plans: `draht-tools create-plan $1 P`
+5. Validate: `draht-tools validate-plans $1`
+6. Commit: `draht-tools commit-docs "create phase $1 plans"`
 
 ## Plan Format
 Plans use XML task format:

package/prompts/commands/progress.md

@@ -1,3 +1,7 @@
+---
+description: "Show current project status"
+---
+
 # /progress
 
 Show current project status.

package/prompts/commands/quick.md

@@ -1,15 +1,21 @@
+---
+description: "Execute a small ad-hoc task with tracking"
+---
+
 # /quick
 
-Execute a small ad-hoc task with GSD tracking.
+Execute a small ad-hoc task with tracking.
 
 ## Usage
 ```
 /quick [description]
 ```
 
+Task: $ARGUMENTS
+
 ## Steps
 1. Run `draht-tools next-quick-number` to get task number
-2. Create quick plan: `draht-tools create-quick-plan NNN "description"`
+2. Create quick plan: `draht-tools create-quick-plan NNN "$ARGUMENTS"`
 3. Execute tasks following the TDD cycle:
    - **🔴 RED** — Write a failing test that describes the desired behaviour
    - **🟢 GREEN** — Write the minimum implementation to make it pass

package/prompts/commands/resume-work.md

@@ -1,3 +1,7 @@
+---
+description: "Resume from last session state"
+---
+
 # /resume-work
 
 Resume from last session state.

package/prompts/commands/review.md

@@ -1,3 +1,7 @@
+---
+description: "Code review and security audit of recent changes"
+---
+
 # /review
 
 Ad-hoc code review and security audit of recent changes or a specific scope.
@@ -7,6 +11,8 @@ Ad-hoc code review and security audit of recent changes or a specific scope.
 /review [scope]
 ```
 
+Scope: $ARGUMENTS
+
 If no scope given, reviews all recent uncommitted changes.
 
 ## Steps