feat(directives): harvest 6 process anti-pattern directives from AGENTS.md + workflow.md

This commit is contained in:
ed
2026-07-02 22:09:05 -04:00
parent c8094ec225
commit 77ee0c68fd
6 changed files with 113 additions and 0 deletions
@@ -0,0 +1,14 @@
# scope_creep_track_doc_ban — v1
**Why this iteration:** Lifted verbatim from `AGENTS.md` §"Process Anti-Patterns" #3 (lines 139-144). This is the baseline encoding — the symptom-rule-pair style currently in production.
Future variants will test alternative encodings (rule-only, tabular) against this baseline.
**Source:** `AGENTS.md:139-144`
---
### 3. The Scope-Creep Track-Doc Pattern (kill it)
**Symptom:** The user asks for a 1-line fix. You write a 5-phase "future track" spec with 140 lines of scope, audit findings, recommendations, and "out of scope" sections. The track doc is now larger than the fix it was meant to scope.
**Rule:** If the user asks for a fix, your output is the fix. A track doc is only appropriate when the fix is multi-day work that requires a plan. If the fix is < 100 lines, it does not get a track. If the fix would touch more than 5 files, it MIGHT get a track — but ask first.