From 6b2a051be3f91936f7b222012bcf33255c2651b2 Mon Sep 17 00:00:00 2001 From: Conan Scott Date: Wed, 1 Jul 2026 05:10:00 +0000 Subject: [PATCH] Add /next-task Claude Code command to drive the backlog safely --- .claude/commands/next-task.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 .claude/commands/next-task.md diff --git a/.claude/commands/next-task.md b/.claude/commands/next-task.md new file mode 100644 index 0000000..c377ac5 --- /dev/null +++ b/.claude/commands/next-task.md @@ -0,0 +1,16 @@ +Work the task backlog in CLAUDE.md. + +1. Read CLAUDE.md, especially "Critical context" and "Task backlog". +2. Pick the lowest-numbered task that is not yet done (default: $ARGUMENTS if a + task id like T1 is given). +3. Restate the task and its acceptance criteria before writing any code. +4. Implement it demo-grade, following the repo conventions: + - Fusion is shared SaaS — never build/host it or automate its console config. + - Endpoints Fusion calls must be public HTTPS with auth. + - Detection returns typed findings; we own minting/vault/restore. + - Never commit AWS creds, secrets, or real PII; seed data is synthetic only. + - Terraform runs with `-chdir=terraform`. +5. Do NOT run deploys or anything that incurs AWS spend without asking first. +6. When done: note what you changed in the relevant file, tick the task in + CLAUDE.md, and state how you verified the acceptance criteria (or what still + needs a human/live check).