diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-06 21:59:52 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-06 21:59:52 -0500 |
| commit | 5710b7865549b923467f5e4b1056e040273fc6aa (patch) | |
| tree | 33a87e2f8a21c2d2d24434340c100f70a895c757 /.claude/commands/start-work.md | |
| parent | aa77f41ff803304c2bc6f224185e1247088a873e (diff) | |
| download | rulesets-5710b7865549b923467f5e4b1056e040273fc6aa.tar.gz rulesets-5710b7865549b923467f5e4b1056e040273fc6aa.zip | |
chore(commands): mark user-invoked commands disable-model-invocation
Add disable-model-invocation: true to the user-triggered slash commands so the harness drops their descriptions from the model's preloaded skill listing while keeping /<name> routing intact. Skills meant for model recommendation (add-tests, debug, five-whys, frontend-design, humanizer, pairwise-tests, playwright-js, playwright-py, root-cause-trace) are unchanged.
Diffstat (limited to '.claude/commands/start-work.md')
| -rw-r--r-- | .claude/commands/start-work.md | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/.claude/commands/start-work.md b/.claude/commands/start-work.md index d3d9349..bf32801 100644 --- a/.claude/commands/start-work.md +++ b/.claude/commands/start-work.md @@ -1,5 +1,6 @@ --- description: Pick up a task (Linear ticket, GitHub issue, todo.org task, or a described scope) and take it through Claim, Justify, Approach, Implement, Verify, and Hand-off. Three user-approval gates separate the phases. The Justify gate covers benefits, costs, engineer/user impact, urgency, effort, alternatives, and a ticket-quality check. The Approach gate covers root cause, risk, refactor prerequisites, test strategy (unit, integration, e2e, pairwise, characterization), migration and backwards-compat, feature-flag question, commit decomposition, and branch name. Implementation uses TDD (red, green, edge cases, refactor audit of every touched file). The audit walks the whole of each touched file against a language-agnostic checklist; every finding is either fixed on this branch or filed as a ticket — nothing is silently dropped. A verify phase exercises the feature end-to-end in the local environment (Playwright against localhost for web projects, scripted manual test otherwise) before the final gate confirms readiness and hands off to the Review-and-Publish flow in commits.md. Use when starting work on a specific task where both "should we" and "how exactly" are worth deliberating. Do NOT use for open-ended bug investigation without a clear target (use debug first), for architectural paradigm exploration (use arch-design), for architectural decision recording (use arch-decide), when the task is trivial and obvious (just do it), or when requirements are still being shaped (use brainstorm). +disable-model-invocation: true --- # /start-work: pick up a task, justify it, plan it, build it |