feat(skill): update red flags

Author: codeaholicguy

skills/agent-orchestration/SKILL.md

@@ -15,6 +15,14 @@ You are the **team lead**. You own the orchestration loop. You do NOT ask the us
 - **Track what you sent.** Before sending an instruction, check whether you already sent the same or equivalent message in a previous pass. Never re-send duplicate instructions.
 - **Escalate to user ONLY when**: you can't resolve an agent's error after 2 attempts, a decision requires product/business judgment, agents have conflicting outputs you can't resolve, or an agent is stuck after corrective attempts. Include: which agent, what happened, your recommendation, what you need. After the user responds, **resume the loop immediately**.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "The agent said it's done" | Agents claim done without evidence | Check the diff and run tests |
+| "I'll check on it later" | You are the loop — no one else will | Check now, act now |
+| "Both agents can edit that file" | Parallel edits cause conflicts | Sequence or assign non-overlapping scopes |
+
 ## Approval Guardrails
 
 You may approve autonomously: code style changes, test results, routine clarifications, and non-destructive progress steps.

skills/capture-knowledge/SKILL.md

@@ -37,6 +37,14 @@ Build structured understanding of code entry points with an analysis-first workf
 - Create `docs/ai/implementation/knowledge-{name}.md` using the Output Template.
 - Include mermaid diagrams when they clarify flows or relationships.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "I already understand this code" | Understanding ≠ documented understanding | Write it down, then verify |
+| "The code is self-documenting" | Future readers lack your current context | Capture the why, not just the what |
+| "Dependencies are obvious" | Implicit dependencies cause surprises | Map them explicitly to depth 3 |
+
 ## Validation
 - Documentation covers all Output Template sections.
 - Summarize key insights, open questions, and related areas for deeper dives.

skills/debug/SKILL.md

@@ -36,6 +36,14 @@ For each hypothesis, include:
 - Confirm post-fix success using the `verify` skill — including regression verification for bug fixes.
 - Summarize remaining risks and follow-ups.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "I already know the cause" | Assumptions skip evidence | Reproduce and prove it first |
+| "This is urgent, just fix it" | A wrong fix wastes more time | 10 minutes of diagnosis saves hours |
+| "The fix is obvious from the stack trace" | Stack traces show symptoms, not causes | Trace backward to the root cause |
+
 ## Output Template
 Use this response structure:
 - Observed vs Expected

skills/dev-lifecycle/SKILL.md

@@ -75,6 +75,15 @@ Use `npx ai-devkit@latest memory` CLI in any phase that involves clarification q
 1. **Before asking questions**: `npx ai-devkit@latest memory search --query "<topic>"`. Apply matches; only ask about uncovered gaps.
 2. **After clarification**: `npx ai-devkit@latest memory store --title "<title>" --content "<knowledge>" --tags "<tags>"`.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "Skip to coding, requirements are clear" | Ambiguity hides in assumptions | Run Phase 1-3 first |
+| "Design hasn't changed, skip Phase 6" | Code drifts from design during implementation | Check implementation against design |
+| "Tests slow us down, ship first" | Bugs in production are slower | Write tests in Phase 4 and 7 |
+| "Just a small change, no review needed" | Small changes cause big outages | Phase 8 applies to all changes |
+
 ## Rules
 
 - Read existing `docs/ai/` before changes. Keep diffs minimal.

skills/simplify-implementation/SKILL.md

@@ -36,6 +36,14 @@ For each issue, apply a pattern:
 5. Prioritize and Plan
 - Rank by impact/risk. Present plan with before/after snippets. Request approval.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "While I'm here, let me refactor this too" | Scope creep breaks things | Only simplify what was requested |
+| "This abstraction will help later" | Predicted reuse rarely materializes | Remove it unless used twice today |
+| "Shorter is simpler" | Brevity can hide complexity | Optimize for readability, not line count |
+
 ## Validation
 - Verify no regressions, add tests for new helpers, update docs if interfaces changed.
 

skills/technical-writer/SKILL.md

@@ -22,6 +22,14 @@ Review documentation as a novice would experience it. Suggest concrete improveme
 - **Medium**: Causes confusion but workaround exists.
 - **Low**: Polish and nice-to-have.
 
+## Red Flags and Rationalizations
+
+| Rationalization | Why It's Wrong | Do Instead |
+|---|---|---|
+| "Developers will figure it out" | Novice users won't | Write for the least experienced reader |
+| "The code example speaks for itself" | Examples without context confuse | Add what it does and when to use it |
+| "Too much detail clutters the doc" | Missing detail blocks users | Include prerequisites and edge cases |
+
 ## Output Template
 
 ```