claudify-agent 1.0.10 → 1.0.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude/commands/spec-apply.md +1 -0
- package/CLAUDE.md +2 -0
- package/package.json +1 -1
|
@@ -7,6 +7,7 @@ Implement spec change: $ARGUMENTS
|
|
|
7
7
|
|
|
8
8
|
1. Read `spec/changes/<change-name>.md`; respect the Invariants in `BACKBONE.md`. Nothing else up front; read code only as each task needs it.
|
|
9
9
|
2. Take the requested task, or the first unchecked `- [ ]` task. Work one task at a time.
|
|
10
|
+
Business-rule guard: money amounts, limits, fees, refunds, permissions, status transitions, legal/compliance rules MUST come from an AC, the Invariants or a linked doc. If the task needs one that is not written down, stop and ask me; never pick a "reasonable" value. Add my answer to the spec before coding it.
|
|
10
11
|
3. Implement it with tests for the ACs it covers. Each test name contains the full AC ID, e.g. `describe("refund/AC-2: expired QR is refunded", ...)` or `func TestRefund_AC2` with a `// refund/AC-2` comment. Use the Domain glossary terms for names. Then run its DoD. Fix until it passes (max 5 attempts, then stop and report).
|
|
11
12
|
4. Tick it `- [x]` in the change file. If reality differs from the spec, update the spec (Requirements/Design) in the same step and tell me.
|
|
12
13
|
5. If I ask you to commit: `feat(<change-name>): <what>` and list the AC IDs covered in the body.
|
package/CLAUDE.md
CHANGED
|
@@ -9,6 +9,7 @@
|
|
|
9
9
|
|
|
10
10
|
If it still holds `<placeholders>`, suggest `/backbone-init`. Follow its Invariants on every task.
|
|
11
11
|
If you finish work without a spec that changes structure, docs, commands or capabilities, suggest `/backbone-sync`.
|
|
12
|
+
Never invent business rules (money, limits, refunds, permissions, status transitions, legal): if no spec, invariant or doc states it, ask.
|
|
12
13
|
|
|
13
14
|
## 1. 🛑 Context & Token Preservation (Sub-20 Line Core)
|
|
14
15
|
- Keep responses concise and targeted. Never dump entire files when diffs suffice.
|
|
@@ -21,6 +22,7 @@ If you finish work without a spec that changes structure, docs, commands or capa
|
|
|
21
22
|
## 2. 📋 Plan First Protocol (Anti-Drift)
|
|
22
23
|
- For tasks touching **>= 2 files** or core architecture:
|
|
23
24
|
- Generate a concise Plan before modifying files.
|
|
25
|
+
- Inside `/spec-apply`, the approved spec Tasks are the plan; do not write another one.
|
|
24
26
|
- Research protocol: `.claude/rules/plan-mode-research.md`
|
|
25
27
|
- Execution checklist: `.claude/rules/plan-mode-execution.md`
|
|
26
28
|
- Validation steps: `.claude/rules/plan-mode-validation.md`
|
package/package.json
CHANGED