diff options
| author | Craig Jennings <c@cjennings.net> | 2026-06-02 21:20:07 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-06-02 21:20:07 -0500 |
| commit | 8ab5ec135a3846972f9eaad5ab67104b2ff19232 (patch) | |
| tree | 078eb05fa04ec2b4f8e546b67a9e75c6f0966a67 /.claude | |
| parent | 6a4b619de45d2151ddc89ed08fbfb44dd530796e (diff) | |
| download | rulesets-8ab5ec135a3846972f9eaad5ab67104b2ff19232.tar.gz rulesets-8ab5ec135a3846972f9eaad5ab67104b2ff19232.zip | |
feat(start-work): add "reasons not to do this" to the Justify gate
The Justify gate covered Downsides and Alternatives but had no forced verdict on whether the work should happen at all. Added item 9: surface the top three objections when real ones exist, or say so in one line when none rise to a genuine objection, rather than manufacturing three. Building the case against the work is cheapest at this gate.
Diffstat (limited to '.claude')
| -rw-r--r-- | .claude/commands/start-work.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/.claude/commands/start-work.md b/.claude/commands/start-work.md index abbee3e..0143a1f 100644 --- a/.claude/commands/start-work.md +++ b/.claude/commands/start-work.md @@ -159,7 +159,8 @@ Then produce a justification that covers all of these, concisely: 6. **Urgency and priority fit.** Does this align with current goals or an upcoming deadline? If the project has committed deadlines, explicitly check this against them. Anything not obviously on the critical path should be called out as "deferrable." 7. **Effort estimate.** S (under 1 hour), M (1 hour to 1 day), L (over 1 day). Rough is fine. 8. **Alternatives considered.** Is there a cheaper way? Can we defer? Can we address the root cause via a different path? -9. **Ticket quality check.** Is scope clear, are acceptance criteria concrete, are reproduction steps present for bugs? If **not clear**, stop and ask the user to choose one of: +9. **Reasons not to do this.** A forced devil's-advocate verdict on whether the work should happen at all — distinct from Downsides (what the change costs) and Alternatives (cheaper paths). Surface the top three objections if real ones exist; when none rise to a genuine objection, say so in one line rather than manufacturing three (e.g. "Nothing material argues against this. No reason to defer or drop it."). Building the case against the work is cheapest at this gate, which is its purpose. +10. **Ticket quality check.** Is scope clear, are acceptance criteria concrete, are reproduction steps present for bugs? If **not clear**, stop and ask the user to choose one of: - (a) Bounce to `/brainstorm` to refine the ticket first. - (b) Ping the ticket author for clarification. - (c) Supply the missing info themselves right now, if it is easy for them to do so. |