diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-26 13:03:48 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-26 13:03:48 -0500 |
| commit | fa4f8d62887325b49176e0a9bcc016b35678057d (patch) | |
| tree | 9b110e8eebd0303618810097dbaa58e8d1340fee | |
| parent | 9bfb13aced68e9e0778f9d46b0eeb939cef05a30 (diff) | |
| download | rulesets-fa4f8d62887325b49176e0a9bcc016b35678057d.tar.gz rulesets-fa4f8d62887325b49176e0a9bcc016b35678057d.zip | |
feat(start-work): let the agent invoke it, not just the user
I dropped disable-model-invocation from start-work's frontmatter. The flag made it user-only, so the agent couldn't run it as a workflow step and I had to type /start-work by hand every time. Removing the line makes it invocable by the agent through the Skill tool while /start-work still works for me. Its description already carries strong "Do NOT use for..." triggers, so the auto-invoke risk stays low. The other 16 commands still carry the flag.
| -rw-r--r-- | .claude/commands/start-work.md | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/.claude/commands/start-work.md b/.claude/commands/start-work.md index d99a9dc..abbee3e 100644 --- a/.claude/commands/start-work.md +++ b/.claude/commands/start-work.md @@ -1,6 +1,5 @@ --- description: Pick up a task (Linear ticket, GitHub issue, todo.org task, or a described scope) and take it through Pre-work, Claim, Justify, Approach, Implement, Verify, and Hand-off. Three user-approval gates separate the phases. Pre-work covers eligibility, a fetch-and-reconcile against the base branch, and a source-code check that the problem the ticket describes still exists in the tree. 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 |