Engineering Discipline
Engineering practice for ANY coding, design, or documentation task: docs-first over training memory (with a docs-used.md ledger and @see references), minimal code via the YAGNI ladder, engineered root-cause fixes (never symptom patches), business-behavior-driven API/schema design, behavior-level testing, executed verification with blast-radius checks before destructive operations, event logging,…
Response Discipline
Communication discipline for EVERY response in ALL conversations: no filler or flattery openers, no hedging, no text walls, verify claims before concluding or agreeing, relevance-scoped answers, and mandatory root-cause-analysis format for any error, bug, or failure. Use on every reply — answering questions, reporting progress, handling corrections, or responding to problems. Especially critical…
Task Registry
Append-only work registry (registry.jsonl, git-tracked) recording every task any agent, sub-agent, or worker job performs — including no-diff work like audits, RCA, and decisions. Use at the START of any session or multi-step task in a repo containing registry.jsonl (read it first), when SPAWNING or acting as a sub-agent, when COMPLETING, FAILING, or ABANDONING any task, and whenever work produce…