Forbid TodoWrite in CLAUDE.md; point at dcat workflow
Mirrors the rule we already have in ønskenytt.no/CLAUDE.md so fresh agents don't reach for the built-in task tools when this repo manages work via dcat. Also switches the prime invocation to the recommended `dcat prime --opinionated` form. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
004b63f51c
commit
3fef3d85a8
1 changed files with 2 additions and 1 deletions
|
|
@ -4,7 +4,8 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
|
||||||
|
|
||||||
## Workflow
|
## Workflow
|
||||||
|
|
||||||
- **Read `AGENTS.md` first.** It defines the mandatory `dcat` (dogcat) issue-tracking workflow used here. The hard rule: **before writing any code for a new bug, feature, or change, ask the user whether to create an issue first** — no exceptions for "small" tasks. Run `dcat prime` after compaction, `/clear`, or starting a new session.
|
- **Read `AGENTS.md` first.** It defines the mandatory `dcat` (dogcat) issue-tracking workflow used here. The hard rule: **before writing any code for a new bug, feature, or change, ask the user whether to create an issue first** — no exceptions for "small" tasks. Run `dcat prime --opinionated` after compaction, `/clear`, or starting a new session.
|
||||||
|
- **Do NOT use the `TodoWrite` / task tools in this project.** Issue tracking and progress is managed with `dcat` as specified in `AGENTS.md` — see that file for the full workflow (`dcat prime --opinionated`, `dcat list --agent-only`, status transitions, closing rules, etc.).
|
||||||
- After committing, show a short summary of what was committed and why (per the user's global guidelines).
|
- After committing, show a short summary of what was committed and why (per the user's global guidelines).
|
||||||
|
|
||||||
## Commands
|
## Commands
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue