devflow-kit 1.4.0 → 1.6.0

package/plugins/devflow-specify/.claude-plugin/plugin.json

@@ -4,7 +4,7 @@
   "author": {
     "name": "Dean0x"
   },
-  "version": "1.4.0",
+  "version": "1.6.0",
   "homepage": "https://github.com/dean0x/devflow",
   "repository": "https://github.com/dean0x/devflow",
   "license": "MIT",

package/plugins/devflow-specify/agents/skimmer.md

@@ -1,6 +1,7 @@
 ---
 name: Skimmer
 description: Codebase orientation using skim to identify relevant files, functions, and patterns for a feature or task
+skills: knowledge-persistence
 model: inherit
 ---
 
@@ -20,6 +21,7 @@ You receive from orchestrator:
 3. **Search for task-relevant code** - Find files matching task keywords
 4. **Identify integration points** - Exports, entry points, import patterns
 5. **Generate orientation summary** - Structured output for implementation planning
+6. **Check project knowledge** - If `.memory/knowledge/decisions.md` exists, read its `<!-- TL;DR: ... -->` first-line comment and include active decision count in orientation under "### Active Decisions". Only the TL;DR is read here (not full entries) — this is intentional for token efficiency; agents that need full entries read the file themselves.
 
 ## Tool Invocation
 
@@ -64,6 +66,9 @@ Always invoke skim via `npx rskim`. This works whether or not skim is globally i
 ### Patterns Observed
 {Existing patterns to follow}
 
+### Active Decisions
+{Count and key decisions from `.memory/knowledge/decisions.md` TL;DR, or "None found" if file missing}
+
 ### Suggested Approach
 {Brief recommendation based on codebase structure}
 ```

package/plugins/devflow-specify/agents/synthesizer.md

@@ -128,10 +128,14 @@ Analyze 3 axes to determine strategy:
 Synthesize outputs from multiple Reviewer agents. Apply strict merge rules.
 
 **Process:**
-1. Read all review reports from `${REVIEW_BASE_DIR}/*-report.*.md`
-2. Categorize issues into 3 buckets (from review-methodology)
-3. Count by severity (CRITICAL, HIGH, MEDIUM, LOW)
-4. Determine merge recommendation based on blocking issues
+1. Read all review reports from `${REVIEW_BASE_DIR}/*.md` (exclude your own output `review-summary.*.md`)
+2. Extract confidence percentages from each finding
+3. Apply confidence-aware aggregation: when multiple reviewers flag the same file:line, boost confidence by 10% per additional reviewer (cap at 100%)
+<!-- Confidence threshold also in: shared/agents/reviewer.md, plugins/devflow-code-review/commands/code-review.md -->
+4. Maintain ≥80% confidence threshold in final output
+5. Categorize issues into 3 buckets (from review-methodology)
+6. Count by severity (CRITICAL, HIGH, MEDIUM, LOW)
+7. Determine merge recommendation based on blocking issues
 
 **Issue Categories:**
 - **Blocking** (Category 1): Issues in YOUR changes - CRITICAL/HIGH must block
@@ -172,7 +176,10 @@ Report format:
 | Pre-existing | - | - | {n} | {n} | {n} |
 
 ## Blocking Issues
-{List with file:line and suggested fix}
+{List with file:line, confidence %, and suggested fix}
+
+## Suggestions (Lower Confidence)
+{Max 5 items across all reviewers with 60-79% confidence. Brief descriptions only.}
 
 ## Action Plan
 1. {Priority fix}

package/plugins/devflow-specify/commands/specify-teams.md

@@ -57,7 +57,11 @@ Find: project structure, similar features, patterns, integration points
 Return: codebase context for requirements (not implementation details)"
 ```
 
-### Phase 3: Explore Requirements (Agent Teams)
+### Phase 3: Load Project Knowledge
+
+Read `.memory/knowledge/decisions.md` and `.memory/knowledge/pitfalls.md`. Pass their content as context to the exploration team below — prior decisions constrain requirements, known pitfalls inform failure modes.
+
+### Phase 4: Explore Requirements (Agent Teams)
 
 Create an agent team for collaborative requirements exploration:
 
@@ -122,7 +126,7 @@ Max 2 debate rounds, then submit consensus requirements findings.
 
 **Exploration team output**: Consensus findings on user needs, similar features, constraints, failure modes.
 
-**Team Shutdown Protocol** (must complete before Phase 5):
+**Team Shutdown Protocol** (must complete before Phase 6):
 
 ```
 Step 1: Shutdown each teammate
@@ -139,9 +143,9 @@ Step 3: GATE — Verify TeamDelete succeeded
   If retry failed → HALT and report: "Exploration team cleanup failed. Cannot create planning team."
 ```
 
-### Phase 4: Synthesize Exploration
+### Phase 5: Synthesize Exploration
 
-**WAIT** for Phase 3, then spawn Synthesizer:
+**WAIT** for Phase 4, then spawn Synthesizer:
 
 ```
 Task(subagent_type="Synthesizer"):
@@ -151,7 +155,7 @@ Explorer consensus: {team exploration consensus output}
 Combine into: user needs, similar features, constraints, failure modes"
 ```
 
-### Phase 5: Plan Scope (Agent Teams)
+### Phase 6: Plan Scope (Agent Teams)
 
 Create an agent team for collaborative scope planning:
 
@@ -164,7 +168,7 @@ Spawn planning teammates with self-contained prompts:
   Prompt: |
     You are planning scope for feature: {feature}
     Exploration synthesis (what we know):
-    {synthesis output from Phase 4}
+    {synthesis output from Phase 5}
 
     Your deliverable: User stories in "As X, I want Y, so that Z" format.
     Cover all actors, actions, and outcomes identified in exploration.
@@ -175,7 +179,7 @@ Spawn planning teammates with self-contained prompts:
   Prompt: |
     You are planning scope for feature: {feature}
     Exploration synthesis (what we know):
-    {synthesis output from Phase 4}
+    {synthesis output from Phase 5}
 
     Your deliverable: v1 MVP scope, v2 deferred items, explicitly out of scope,
     and dependencies on other features or systems.
@@ -186,7 +190,7 @@ Spawn planning teammates with self-contained prompts:
   Prompt: |
     You are planning scope for feature: {feature}
     Exploration synthesis (what we know):
-    {synthesis output from Phase 4}
+    {synthesis output from Phase 5}
 
     Your deliverable: Testable acceptance criteria for success cases,
     failure cases, and edge cases. Every criterion must be verifiable.
@@ -221,9 +225,9 @@ Step 3: GATE — Verify TeamDelete succeeded
   If retry failed → HALT and report: "Planning team cleanup failed. Cannot proceed to Gate 1."
 ```
 
-### Phase 6: Synthesize Planning
+### Phase 7: Synthesize Planning
 
-**WAIT** for Phase 5, then spawn Synthesizer:
+**WAIT** for Phase 6, then spawn Synthesizer:
 
 ```
 Task(subagent_type="Synthesizer"):
@@ -233,7 +237,7 @@ Planner consensus: {team planning consensus output}
 Combine into: user stories, scope breakdown, acceptance criteria, open questions"
 ```
 
-### Phase 7: Gate 1 - Validate Scope
+### Phase 8: Gate 1 - Validate Scope
 
 Use AskUserQuestion to validate:
 - Primary problem being solved
@@ -241,14 +245,14 @@ Use AskUserQuestion to validate:
 - v1 scope selection (minimal/medium/full)
 - Explicit exclusions
 
-### Phase 8: Gate 2 - Confirm Criteria
+### Phase 9: Gate 2 - Confirm Criteria
 
 Present specification summary, then use AskUserQuestion for final confirmation:
 - Success UX pattern
 - Error handling approach
 - Ready to create issue / Needs changes / Cancel
 
-### Phase 9: Create Issue
+### Phase 10: Create Issue
 
 Create GitHub issue with `gh issue create`:
 - Title: feature name
@@ -268,32 +272,35 @@ Report issue number and URL.
 ├─ Phase 2: Orient
 │  └─ Skimmer agent (codebase context via skim)
 │
-├─ Phase 3: Explore Requirements (Agent Teams)
+├─ Phase 3: Load Project Knowledge
+│  └─ Read decisions.md + pitfalls.md
+│
+├─ Phase 4: Explore Requirements (Agent Teams)
 │  ├─ User Perspective Explorer (teammate)
 │  ├─ Similar Features Explorer (teammate)
 │  ├─ Constraints Explorer (teammate)
 │  ├─ Failure Mode Explorer (teammate)
 │  └─ Debate → consensus requirements findings
 │
-├─ Phase 4: Synthesize Exploration
+├─ Phase 5: Synthesize Exploration
 │  └─ Synthesizer agent (mode: exploration)
 │
-├─ Phase 5: Plan Scope (Agent Teams)
+├─ Phase 6: Plan Scope (Agent Teams)
 │  ├─ User Stories Planner (teammate)
 │  ├─ Scope Boundaries Planner (teammate)
 │  ├─ Acceptance Criteria Planner (teammate)
 │  └─ Debate → consensus scope plan
 │
-├─ Phase 6: Synthesize Planning
+├─ Phase 7: Synthesize Planning
 │  └─ Synthesizer agent (mode: planning)
 │
-├─ Phase 7: GATE 1 - Validate Scope ⛔ MANDATORY
+├─ Phase 8: GATE 1 - Validate Scope ⛔ MANDATORY
 │  └─ AskUserQuestion: Confirm scope and priorities
 │
-├─ Phase 8: GATE 2 - Confirm Criteria ⛔ MANDATORY
+├─ Phase 9: GATE 2 - Confirm Criteria ⛔ MANDATORY
 │  └─ AskUserQuestion: Final spec approval
 │
-├─ Phase 9: Create Issue
+├─ Phase 10: Create Issue
 │  └─ gh issue create
 │
 └─ Report: Issue number, URL, /implement command

package/plugins/devflow-specify/commands/specify.md

@@ -57,20 +57,24 @@ Find: project structure, similar features, patterns, integration points
 Return: codebase context for requirements (not implementation details)"
 ```
 
-### Phase 3: Explore Requirements (Parallel)
+### Phase 3: Load Project Knowledge
 
-Spawn 4 Explore agents **in a single message**, each with Skimmer context:
+Read `.memory/knowledge/decisions.md` and `.memory/knowledge/pitfalls.md`. Pass their content as context to the Explore agents below — prior decisions constrain requirements, known pitfalls inform failure modes.
+
+### Phase 4: Explore Requirements (Parallel)
+
+Spawn 4 Explore agents **in a single message**, each with Skimmer context and project knowledge (if loaded):
 
 | Focus | Thoroughness | Find |
 |-------|-------------|------|
 | User perspective | medium | Target users, goals, pain points, user journeys |
 | Similar features | medium | Comparable features, scope patterns, edge cases |
-| Constraints | quick | Dependencies, business rules, security, performance |
-| Failure modes | quick | Error states, edge cases, validation needs |
+| Constraints | quick | Dependencies, business rules, security, performance, **prior architectural decisions** |
+| Failure modes | quick | Error states, edge cases, validation needs, **known pitfalls** |
 
-### Phase 4: Synthesize Exploration
+### Phase 5: Synthesize Exploration
 
-**WAIT** for Phase 3, then spawn Synthesizer:
+**WAIT** for Phase 4, then spawn Synthesizer:
 
 ```
 Task(subagent_type="Synthesizer"):
@@ -79,7 +83,7 @@ Mode: exploration
 Combine into: user needs, similar features, constraints, failure modes"
 ```
 
-### Phase 5: Plan Scope (Parallel)
+### Phase 6: Plan Scope (Parallel)
 
 Spawn 3 Plan agents **in a single message**, each with exploration synthesis:
 
@@ -89,9 +93,9 @@ Spawn 3 Plan agents **in a single message**, each with exploration synthesis:
 | Scope boundaries | v1 MVP, v2 deferred, out of scope, dependencies |
 | Acceptance criteria | Success/failure/edge case criteria (testable) |
 
-### Phase 6: Synthesize Planning
+### Phase 7: Synthesize Planning
 
-**WAIT** for Phase 5, then spawn Synthesizer:
+**WAIT** for Phase 6, then spawn Synthesizer:
 
 ```
 Task(subagent_type="Synthesizer"):
@@ -100,7 +104,7 @@ Mode: planning
 Combine into: user stories, scope breakdown, acceptance criteria, open questions"
 ```
 
-### Phase 7: Gate 1 - Validate Scope
+### Phase 8: Gate 1 - Validate Scope
 
 Use AskUserQuestion to validate:
 - Primary problem being solved
@@ -108,14 +112,14 @@ Use AskUserQuestion to validate:
 - v1 scope selection (minimal/medium/full)
 - Explicit exclusions
 
-### Phase 8: Gate 2 - Confirm Criteria
+### Phase 9: Gate 2 - Confirm Criteria
 
 Present specification summary, then use AskUserQuestion for final confirmation:
 - Success UX pattern
 - Error handling approach
 - Ready to create issue / Needs changes / Cancel
 
-### Phase 9: Create Issue
+### Phase 10: Create Issue
 
 Create GitHub issue with `gh issue create`:
 - Title: feature name
@@ -135,30 +139,33 @@ Report issue number and URL.
 ├─ Phase 2: Orient
 │  └─ Skimmer agent (codebase context via skim)
 │
-├─ Phase 3: Explore Requirements (PARALLEL)
+├─ Phase 3: Load Project Knowledge
+│  └─ Read decisions.md + pitfalls.md
+│
+├─ Phase 4: Explore Requirements (PARALLEL)
 │  ├─ Explore: User perspective
 │  ├─ Explore: Similar features
 │  ├─ Explore: Constraints
 │  └─ Explore: Failure modes
 │
-├─ Phase 4: Synthesize Exploration
+├─ Phase 5: Synthesize Exploration
 │  └─ Synthesizer agent (mode: exploration)
 │
-├─ Phase 5: Plan Scope (PARALLEL)
+├─ Phase 6: Plan Scope (PARALLEL)
 │  ├─ Plan: User stories
 │  ├─ Plan: Scope boundaries
 │  └─ Plan: Acceptance criteria
 │
-├─ Phase 6: Synthesize Planning
+├─ Phase 7: Synthesize Planning
 │  └─ Synthesizer agent (mode: planning)
 │
-├─ Phase 7: GATE 1 - Validate Scope ⛔ MANDATORY
+├─ Phase 8: GATE 1 - Validate Scope ⛔ MANDATORY
 │  └─ AskUserQuestion: Confirm scope and priorities
 │
-├─ Phase 8: GATE 2 - Confirm Criteria ⛔ MANDATORY
+├─ Phase 9: GATE 2 - Confirm Criteria ⛔ MANDATORY
 │  └─ AskUserQuestion: Final spec approval
 │
-├─ Phase 9: Create Issue
+├─ Phase 10: Create Issue
 │  └─ gh issue create
 │
 └─ Report: Issue number, URL, /implement command

package/plugins/devflow-typescript/.claude-plugin/plugin.json

@@ -4,7 +4,7 @@
   "author": {
     "name": "Dean0x"
   },
-  "version": "1.4.0",
+  "version": "1.6.0",
   "homepage": "https://github.com/dean0x/devflow",
   "repository": "https://github.com/dean0x/devflow",
   "license": "MIT",

package/scripts/hooks/ambient-prompt

@@ -30,15 +30,16 @@ if [ "$WORD_COUNT" -lt 2 ]; then
   exit 0
 fi
 
-# Inject classification preamble
-PREAMBLE="AMBIENT MODE ACTIVE: Before responding, silently classify this prompt:
-Intent: BUILD | DEBUG | REVIEW | PLAN | EXPLORE | CHAT
-Depth: QUICK (no overhead) | GUIDED (load skills) | ELEVATE (suggest /command)
+# Normalize to lowercase for matching
+PROMPT_LOWER=$(echo "$PROMPT" | tr '[:upper:]' '[:lower:]')
 
-If GUIDED+: Use the ambient-router skill already in your session context for classification details and skill selection matrix. Then Read the selected skills from ~/.claude/skills/<name>/SKILL.md and apply their patterns. For BUILD tasks, also load test-driven-development skill and enforce RED-GREEN-REFACTOR.
+# Fast-path: git operations are always QUICK — skip preamble
+if echo "$PROMPT_LOWER" | grep -qE '^(commit|push|pull|merge|rebase|cherry-pick|squash|tag|stash)|create (a )?pr|open (a )?pr'; then
+  exit 0
+fi
 
-If QUICK: Respond normally without stating classification.
-Only state classification aloud for GUIDED/ELEVATE."
+# Inject classification preamble
+PREAMBLE="AMBIENT MODE ACTIVE: Before responding, silently classify this prompt using the ambient-router skill already in your session context. If QUICK, respond normally without stating classification."
 
 jq -n --arg ctx "$PREAMBLE" '{
   "hookSpecificOutput": {

package/scripts/hooks/session-start-memory

@@ -119,6 +119,31 @@ ${COMPACT_NOTE}"
   fi
 fi
 
+# --- Section 1.5: Project Knowledge TL;DR ---
+KNOWLEDGE_DIR="$CWD/.memory/knowledge"
+if [ -d "$KNOWLEDGE_DIR" ]; then
+  KNOWLEDGE_TLDR=""
+  for kf in "$KNOWLEDGE_DIR"/decisions.md "$KNOWLEDGE_DIR"/pitfalls.md; do
+    if [ -f "$kf" ]; then
+      TLDR_LINE=$(sed -n '1s/<!-- TL;DR: \(.*\) -->/\1/p' "$kf")
+      if [ -n "$TLDR_LINE" ]; then
+        KNOWLEDGE_TLDR="${KNOWLEDGE_TLDR}${TLDR_LINE}\n"
+      fi
+    fi
+  done
+  if [ -n "$KNOWLEDGE_TLDR" ]; then
+    KNOWLEDGE_SECTION="--- PROJECT KNOWLEDGE (TL;DR) ---
+$(printf '%b' "$KNOWLEDGE_TLDR")"
+    if [ -n "$CONTEXT" ]; then
+      CONTEXT="${CONTEXT}
+
+${KNOWLEDGE_SECTION}"
+    else
+      CONTEXT="$KNOWLEDGE_SECTION"
+    fi
+  fi
+fi
+
 # --- Section 2: Ambient Skill Injection ---
 
 # Inject ambient-router SKILL.md directly into context so Claude doesn't need a Read call.
@@ -129,10 +154,15 @@ AMBIENT_SKILL_PATH="$HOME/.claude/skills/ambient-router/SKILL.md"
 SETTINGS_FILE="$HOME/.claude/settings.json"
 if [ -f "$AMBIENT_SKILL_PATH" ] && [ -f "$SETTINGS_FILE" ] && grep -q "ambient-prompt" "$SETTINGS_FILE" 2>/dev/null; then
   AMBIENT_SKILL_CONTENT=$(cat "$AMBIENT_SKILL_PATH")
-  CONTEXT="${CONTEXT}
-
---- AMBIENT ROUTER (auto-loaded) ---
+  AMBIENT_SECTION="--- AMBIENT ROUTER (auto-loaded) ---
 ${AMBIENT_SKILL_CONTENT}"
+  if [ -n "$CONTEXT" ]; then
+    CONTEXT="${CONTEXT}
+
+${AMBIENT_SECTION}"
+  else
+    CONTEXT="$AMBIENT_SECTION"
+  fi
 fi
 
 # --- Output ---

package/shared/agents/coder.md

@@ -2,7 +2,7 @@
 name: Coder
 description: Autonomous task implementation on feature branch. Implements, tests, and commits.
 model: inherit
-skills: core-patterns, git-safety, implementation-patterns, git-workflow, test-patterns, input-validation
+skills: core-patterns, git-safety, implementation-patterns, git-workflow, test-patterns, test-driven-development, search-first, input-validation
 ---
 
 # Coder Agent
@@ -29,11 +29,16 @@ You receive from orchestrator:
 
 ## Responsibilities
 
-1. **Orient on branch state**: Check git log for commits from previous Coders (if sequential). Read files created by prior phases - **do not trust summaries alone**. Identify patterns from actual code: naming conventions, error handling approach, testing style.
+1. **Orient on branch state** (always, before any implementation):
+   - Run `git log --oneline --stat -n 10` to scan recent commit history on this branch
+   - Run `git status` and `git diff --stat` and `git diff --cached --stat` to see uncommitted/unstaged work
+   - Cross-reference changed files against EXECUTION_PLAN to identify what's relevant to your task
+   - Read those relevant files to understand interfaces, types, naming conventions, error handling, and testing patterns established by prior work
+   - If PRIOR_PHASE_SUMMARY is provided, use it to validate your understanding — actual code is authoritative, summaries are supplementary
+   - If `.memory/knowledge/decisions.md` exists, read it. Apply prior architectural decisions relevant to this task. Avoid contradicting accepted decisions without documenting a new ADR.
+   - If `.memory/knowledge/pitfalls.md` exists, scan for pitfalls in files you're about to modify.
 
-2. **Reference handoff** (if PRIOR_PHASE_SUMMARY provided): Use summary to validate your understanding of prior work, not as the sole source of truth. The actual code is authoritative.
-
-3. **Load domain skills**: Based on DOMAIN hint and files in scope, dynamically load relevant language/ecosystem skills by reading their SKILL.md. Only load skills that are installed:
+2. **Load domain skills**: Based on DOMAIN hint and files in scope, dynamically load relevant language/ecosystem skills by reading their SKILL.md. Only load skills that are installed:
    - `backend` (TypeScript): Read `~/.claude/skills/typescript/SKILL.md`, `~/.claude/skills/input-validation/SKILL.md`
    - `backend` (Go): Read `~/.claude/skills/go/SKILL.md`
    - `backend` (Java): Read `~/.claude/skills/java/SKILL.md`
@@ -44,22 +49,22 @@ You receive from orchestrator:
    - `fullstack`: Combine backend + frontend skills
    - If a Read fails (skill not installed), skip it silently and continue.
 
-4. **Implement the plan**: Work through execution steps systematically, creating and modifying files. Follow existing patterns. Type everything. Use Result types if codebase uses them.
+3. **Implement the plan**: Work through execution steps systematically, creating and modifying files. Follow existing patterns. Type everything. Use Result types if codebase uses them.
 
-5. **Write tests**: Add tests for new functionality. Cover happy path, error cases, and edge cases. Follow existing test patterns.
+4. **Write tests**: Add tests for new functionality. Cover happy path, error cases, and edge cases. Follow existing test patterns.
 
-6. **Run tests**: Execute the test suite. Fix any failures. All tests must pass before proceeding.
+5. **Run tests**: Execute the test suite. Fix any failures. All tests must pass before proceeding.
 
-7. **Commit and push**: Create atomic commits with clear messages. Reference TASK_ID. Push to remote.
+6. **Commit and push**: Create atomic commits with clear messages. Reference TASK_ID. Push to remote.
 
-8. **Create PR** (if CREATE_PR=true): Create pull request against BASE_BRANCH with summary and testing notes.
+7. **Create PR** (if CREATE_PR=true): Create pull request against BASE_BRANCH with summary and testing notes.
 
-9. **Generate handoff** (if HANDOFF_REQUIRED=true): Include implementation summary for next Coder (see Output section).
+8. **Generate handoff** (if HANDOFF_REQUIRED=true): Include implementation summary for next Coder (see Output section).
 
 ## Principles
 
 1. **Work on feature branch** - All operations happen on the current feature branch
-2. **Branch orientation first** - In sequential execution, read actual files before trusting handoff summaries
+2. **Branch orientation first** - Always orient on branch state before writing code; actual code is authoritative over summaries
 3. **Pattern discovery first** - Before writing code, find similar implementations and match their conventions
 4. **Be decisive** - Make confident implementation choices. Don't present alternatives or ask permission for tactical decisions
 5. **Follow existing patterns** - Match codebase style, don't invent new conventions
@@ -86,6 +91,9 @@ Return structured completion status:
 ### PR (if created)
 - URL: {pr_url}
 
+### Key Decisions (if any)
+- {Decision}: {rationale}
+
 ### Blockers (if any)
 {Description of blocker or failure with recommendation}
 ```
@@ -124,4 +132,4 @@ Return structured completion status:
 - Switch branches during implementation
 - Push to branches other than your feature branch
 - Merge PRs (orchestrator handles this)
-- Trust handoff summaries without reading actual code (in sequential execution)
+- Trust handoff summaries without reading actual code

package/shared/agents/reviewer.md

@@ -42,12 +42,38 @@ The orchestrator provides:
 ## Responsibilities
 
 1. **Load focus skill** - Read the pattern skill file for your focus area from the table above. This gives you detection rules and patterns specific to your review type.
-2. **Identify changed lines** - Get diff against base branch (main/master/develop)
-3. **Apply 3-category classification** - Sort issues by where they occur
-4. **Apply focus-specific analysis** - Use pattern skill detection rules from the loaded skill file
-5. **Assign severity** - CRITICAL, HIGH, MEDIUM, LOW based on impact
-6. **Generate report** - File:line references with suggested fixes
-7. **Determine merge recommendation** - Based on blocking issues
+2. **Check known pitfalls** - If `.memory/knowledge/pitfalls.md` exists, read it. Check if any pitfall Areas overlap with files in the current diff. Verify the Resolution was applied. Flag if a known pitfall pattern is being reintroduced.
+3. **Identify changed lines** - Get diff against base branch (main/master/develop)
+4. **Apply 3-category classification** - Sort issues by where they occur
+5. **Apply focus-specific analysis** - Use pattern skill detection rules from the loaded skill file
+6. **Assign severity** - CRITICAL, HIGH, MEDIUM, LOW based on impact
+7. **Assess confidence** - Assign 0-100% confidence to each finding (see Confidence Scale below)
+8. **Filter by confidence** - Only report findings ≥80% in main sections; lower-confidence items go to Suggestions
+9. **Consolidate similar issues** - Group related findings to reduce noise (see Consolidation Rules)
+10. **Generate report** - File:line references with suggested fixes
+11. **Determine merge recommendation** - Based on blocking issues
+
+## Confidence Scale
+
+Assess how certain you are that each finding is a real issue (not a false positive):
+
+| Range | Label | Meaning |
+|-------|-------|---------|
+| 90-100% | Certain | Clearly a bug, vulnerability, or violation — no ambiguity |
+| 80-89% | High | Very likely an issue, but minor chance of false positive |
+| 60-79% | Medium | Plausible issue, but depends on context you may not fully see |
+| < 60% | Low | Possible concern, but likely a matter of style or interpretation |
+
+<!-- Confidence threshold also in: shared/agents/synthesizer.md, plugins/devflow-code-review/commands/code-review.md -->
+**Threshold**: Only report findings with ≥80% confidence in Blocking, Should-Fix, and Pre-existing sections. Findings with 60-79% confidence go to the Suggestions section. Findings < 60% are dropped entirely.
+
+## Consolidation Rules
+
+Before writing your report, apply these noise reduction rules:
+
+1. **Group similar issues** — If 3+ instances of the same pattern appear (e.g., "missing error handling" in multiple functions), consolidate into 1 finding listing all locations rather than N separate findings
+2. **Skip stylistic preferences** — Do not flag formatting, naming style, or code organization choices unless they violate explicit project conventions found in CLAUDE.md, .editorconfig, or linter configs
+3. **Skip issues in unchanged code** — Pre-existing issues in lines you did NOT change should only be reported if CRITICAL severity (security vulnerabilities, data loss risks)
 
 ## Issue Categories (from review-methodology)
 
@@ -76,17 +102,29 @@ Report format for `{output_path}`:
 
 ### CRITICAL
 **{Issue}** - `file.ts:123`
+**Confidence**: {n}%
 - Problem: {description}
 - Fix: {suggestion with code}
 
+**{Issue Title} ({N} occurrences)** — Confidence: {n}%
+- `file1.ts:12`, `file2.ts:45`, `file3.ts:89`
+- Problem: {description of the shared pattern}
+- Fix: {suggestion that applies to all occurrences}
+
 ### HIGH
-{issues...}
+{issues with **Confidence**: {n}% each...}
 
 ## Issues in Code You Touched (Should Fix)
-{issues with file:line...}
+{issues with file:line and **Confidence**: {n}% each...}
 
 ## Pre-existing Issues (Not Blocking)
-{informational issues...}
+{informational issues with **Confidence**: {n}% each...}
+
+## Suggestions (Lower Confidence)
+
+{Max 3 items with 60-79% confidence. Brief description only — no code fixes.}
+
+- **{Issue}** - `file.ts:456` (Confidence: {n}%) — {brief description}
 
 ## Summary
 | Category | CRITICAL | HIGH | MEDIUM | LOW |

package/shared/agents/simplifier.md

@@ -1,6 +1,7 @@
 ---
 name: Simplifier
 description: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise.
+skills: core-patterns
 model: inherit
 ---
 
@@ -59,4 +60,34 @@ Your refinement process:
 5. Verify the refined code is simpler and more maintainable
 6. Document only significant changes that affect understanding
 
-You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.
+You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.
+
+## Output
+
+Return structured completion status:
+
+```markdown
+## Simplification Report
+
+### Changes Applied
+- {file}: {description of simplification}
+
+### Changes Skipped
+- {reason not simplified — would change behavior / already clean}
+
+### Files Modified
+- {file} ({change description})
+```
+
+## Boundaries
+
+**Escalate to orchestrator:**
+- Changes that would alter observable behavior or break tests
+- Simplifications requiring new dependencies or architectural changes
+- Files outside the recently modified scope (unless instructed)
+
+**Handle autonomously:**
+- Naming improvements, dead code removal, nesting reduction
+- Import sorting and organization
+- Redundant abstraction elimination
+- Comment cleanup (remove obvious, keep non-obvious)

package/shared/agents/skimmer.md

@@ -1,6 +1,7 @@
 ---
 name: Skimmer
 description: Codebase orientation using skim to identify relevant files, functions, and patterns for a feature or task
+skills: knowledge-persistence
 model: inherit
 ---
 
@@ -20,6 +21,7 @@ You receive from orchestrator:
 3. **Search for task-relevant code** - Find files matching task keywords
 4. **Identify integration points** - Exports, entry points, import patterns
 5. **Generate orientation summary** - Structured output for implementation planning
+6. **Check project knowledge** - If `.memory/knowledge/decisions.md` exists, read its `<!-- TL;DR: ... -->` first-line comment and include active decision count in orientation under "### Active Decisions". Only the TL;DR is read here (not full entries) — this is intentional for token efficiency; agents that need full entries read the file themselves.
 
 ## Tool Invocation
 
@@ -64,6 +66,9 @@ Always invoke skim via `npx rskim`. This works whether or not skim is globally i
 ### Patterns Observed
 {Existing patterns to follow}
 
+### Active Decisions
+{Count and key decisions from `.memory/knowledge/decisions.md` TL;DR, or "None found" if file missing}
+
 ### Suggested Approach
 {Brief recommendation based on codebase structure}
 ```