@thierrynakoa/fire-flow 10.0.0

package/hooks/session-end.sh

@@ -0,0 +1,90 @@
+#!/bin/bash
+# MIT License - Copyright (c) 2026 ThierryN - https://github.com/ThierryN/dominion-flow
+#
+# Dominion Flow Plugin - Session End Hook
+#
+# WHAT THIS DOES:
+#   When a Claude Code session ends, this script runs automatically.
+#   It tries to consolidate session memory into a vector database (Qdrant)
+#   so future sessions can search past experiences semantically.
+#
+# HOW IT WORKS:
+#   1. Checks if the your-memory-repo project exists on this machine
+#   2. Checks if Qdrant (vector database) is running on port 6335
+#   3. Checks if Ollama (local embedding model) is running on port 11434
+#   4. If all three are ready, runs "npm run consolidate" to index new files
+#
+# THIS IS OPTIONAL:
+#   If Qdrant or Ollama are not running, this script exits silently (no error).
+#   The flat .md handoff files in ~/.claude/warrior-handoffs/ are always intact
+#   and used as the fallback. Memory consolidation is a bonus, not a requirement.
+#
+# NOTE FOR NEW USERS:
+#   The MEMORY_PROJECT path below points to a local project that handles
+#   vector indexing. If you do not have this project set up, this hook
+#   will skip silently — your session will still work normally.
+#   To set up vector memory, see: https://github.com/ThierryN/dominion-flow
+
+echo "=============================================="
+echo "  DOMINION FLOW - Session End Consolidation"
+echo "=============================================="
+echo ""
+
+MEMORY_PROJECT="$HOME/repos/your-memory-repo"
+
+# =============================================
+# 1. Check if your-memory-repo project exists
+# =============================================
+if [ ! -d "$MEMORY_PROJECT" ]; then
+    echo "[SKIP] your-memory-repo project not found at $MEMORY_PROJECT"
+    echo "       Memory consolidation skipped."
+    exit 0
+fi
+
+# =============================================
+# 2. Check if Qdrant is running (port 6335)
+# =============================================
+if ! curl -s http://localhost:6335/healthz > /dev/null 2>&1; then
+    echo "[SKIP] Qdrant not running on port 6335."
+    echo "       Memory consolidation skipped (no vector DB)."
+    echo "       Flat .md files are still available."
+    exit 0
+fi
+
+# =============================================
+# 3. Check if Ollama is running
+# =============================================
+if ! curl -s http://localhost:11434/api/tags > /dev/null 2>&1; then
+    echo "[SKIP] Ollama not running."
+    echo "       Memory consolidation skipped (no embeddings)."
+    exit 0
+fi
+
+# =============================================
+# 4. Run light consolidation (index new files only)
+# =============================================
+echo ">>> Running light memory consolidation..."
+echo "    (Index new/changed files only — fast, <30s)"
+echo ""
+
+cd "$MEMORY_PROJECT" || exit 0
+
+# Run the consolidate command (indexes new files + extracts facts)
+npm run consolidate 2>&1 | tail -20
+
+CONSOLIDATE_EXIT=$?
+
+if [ $CONSOLIDATE_EXIT -eq 0 ]; then
+    echo ""
+    echo ">>> Memory consolidation complete."
+else
+    echo ""
+    echo "[WARN] Consolidation exited with code $CONSOLIDATE_EXIT"
+    echo "       This is non-fatal. Memory files are still intact."
+fi
+
+echo ""
+echo "=============================================="
+echo "  SESSION END CONSOLIDATION COMPLETE"
+echo "=============================================="
+echo ""

package/hooks/session-start.sh

@@ -0,0 +1,111 @@
+#!/bin/bash
+# MIT License - Copyright (c) 2026 ThierryN - https://github.com/ThierryN/dominion-flow
+#
+# Dominion Flow Plugin - Session Start Hook
+#
+# WHAT THIS DOES:
+#   Every time a Claude Code session starts, this script runs automatically.
+#   It looks for two things and prints them into the session context:
+#     1. The project's CONSCIENCE.md — a living summary of where the project is right now
+#     2. The most recent WARRIOR handoff file — Claude's notes from the last session
+#
+# WHY THIS MATTERS:
+#   Claude has no memory between sessions by default. This hook is what gives
+#   Claude its "memory" — it re-injects the previous session's context so Claude
+#   can pick up exactly where it left off without you having to explain anything.
+
+echo "=============================================="
+echo "  DOMINION FLOW - Session Context Injection"
+echo "=============================================="
+echo ""
+
+# Get the current working directory (project root)
+PROJECT_ROOT="$(pwd)"
+
+# Define WARRIOR handoffs directory
+WARRIOR_HANDOFFS="$HOME/.claude/warrior-handoffs"
+
+# =============================================
+# 1. Check for .planning/CONSCIENCE.md in project
+# =============================================
+STATE_FILE="$PROJECT_ROOT/.planning/CONSCIENCE.md"
+
+if [ -f "$STATE_FILE" ]; then
+    echo ">>> PROJECT STATE DETECTED <<<"
+    echo "Location: $STATE_FILE"
+    echo "----------------------------------------------"
+    cat "$STATE_FILE"
+    echo ""
+    echo "----------------------------------------------"
+    echo ""
+else
+    echo "[INFO] No .planning/CONSCIENCE.md found in current project."
+    echo "       Path checked: $STATE_FILE"
+    echo ""
+fi
+
+# =============================================
+# 2. Check for WARRIOR Handoffs
+# =============================================
+echo ">>> WARRIOR HANDOFF CONTEXT <<<"
+echo "Location: $WARRIOR_HANDOFFS"
+echo ""
+
+if [ -d "$WARRIOR_HANDOFFS" ]; then
+    # List recent handoff files (last 5, most recent first)
+    HANDOFF_FILES=$(ls -t "$WARRIOR_HANDOFFS"/*.md 2>/dev/null | head -5)
+
+    if [ -n "$HANDOFF_FILES" ]; then
+        echo "Recent handoff files:"
+        echo "----------------------------------------------"
+        for file in $HANDOFF_FILES; do
+            FILENAME=$(basename "$file")
+            MODIFIED=$(stat -c '%Y' "$file" 2>/dev/null || stat -f '%m' "$file" 2>/dev/null)
+            if [ -n "$MODIFIED" ]; then
+                # Convert timestamp to readable date
+                DATE=$(date -d "@$MODIFIED" '+%Y-%m-%d %H:%M' 2>/dev/null || date -r "$MODIFIED" '+%Y-%m-%d %H:%M' 2>/dev/null || echo "unknown")
+                echo "  - $FILENAME ($DATE)"
+            else
+                echo "  - $FILENAME"
+            fi
+        done
+        echo ""
+
+        # Get the most recent handoff file
+        LATEST_HANDOFF=$(echo "$HANDOFF_FILES" | head -1)
+
+        if [ -f "$LATEST_HANDOFF" ]; then
+            LATEST_NAME=$(basename "$LATEST_HANDOFF")
+            echo ">>> LATEST HANDOFF: $LATEST_NAME <<<"
+            echo "----------------------------------------------"
+
+            # Output first 100 lines or full file if shorter
+            head -100 "$LATEST_HANDOFF"
+
+            # Check if file was truncated
+            TOTAL_LINES=$(wc -l < "$LATEST_HANDOFF")
+            if [ "$TOTAL_LINES" -gt 100 ]; then
+                echo ""
+                echo "... [Truncated - $TOTAL_LINES total lines] ..."
+                echo "Use: Read tool on $LATEST_HANDOFF for full content"
+            fi
+            echo ""
+            echo "----------------------------------------------"
+        fi
+    else
+        echo "[INFO] No handoff files found in $WARRIOR_HANDOFFS"
+    fi
+else
+    echo "[INFO] WARRIOR handoffs directory not found: $WARRIOR_HANDOFFS"
+fi
+
+echo ""
+echo "=============================================="
+echo "  SESSION CONTEXT INJECTION COMPLETE"
+echo "=============================================="
+echo ""
+echo "RECOMMENDED ACTIONS:"
+echo "  1. Review CONSCIENCE.md for current project phase"
+echo "  2. Check latest WARRIOR handoff for pending tasks"
+echo "  3. Use /fire-dashboard to see project status"
+echo ""

package/package.json

@@ -0,0 +1,52 @@
+{
+  "name": "@thierrynakoa/fire-flow",
+  "version": "10.0.0",
+  "description": "Structured workflow orchestration for Claude Code — 42 commands, 13 agents, 90+ skills. Plan → Execute → Verify → Handoff with parallel execution, session memory, and circuit breaker safety.",
+  "keywords": [
+    "claude-code",
+    "plugin",
+    "workflow",
+    "orchestration",
+    "ai-agent",
+    "parallel-execution",
+    "session-memory",
+    "debugging",
+    "skills-library"
+  ],
+  "author": "ThierryN",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/ThierryN/fire-flow.git"
+  },
+  "homepage": "https://github.com/ThierryN/fire-flow#readme",
+  "bugs": {
+    "url": "https://github.com/ThierryN/fire-flow/issues"
+  },
+  "bin": {
+    "fire-flow": "./bin/cli.js"
+  },
+  "files": [
+    "bin/",
+    "agents/",
+    "commands/",
+    "hooks/",
+    "skills-library/",
+    "templates/",
+    "references/",
+    "workflows/",
+    "plugin.json",
+    ".claude-plugin/",
+    "README.md",
+    "QUICK-START.md",
+    "COMMAND-REFERENCE.md",
+    "DOMINION-FLOW-OVERVIEW.md",
+    "ARCHITECTURE-DIAGRAM.md",
+    "TROUBLESHOOTING.md",
+    "validation-config.yml",
+    "version.json"
+  ],
+  "engines": {
+    "node": ">=16.0.0"
+  }
+}

package/plugin.json

@@ -0,0 +1,7 @@
+{
+  "name": "dominion-flow",
+  "version": "10.0.0",
+  "description": "Dominion Flow is a comprehensive orchestration platform that empowers your Claude agent. It gives Claude a complete, structured workflow for taking projects from idea to production — with parallel execution, 190+ reusable skills, session memory across handoffs, 70-point quality verification, autonomous mode, E2E testing, and a circuit breaker to prevent stuck loops. Includes 39 slash commands organized into 7 tiers covering planning, execution, verification, debugging, skills management, and milestone tracking.",
+  "commands": "commands/",
+  "agents": "agents/"
+}

package/references/auto-skill-extraction.md

@@ -0,0 +1,136 @@
+# Auto-Skill Extraction System
+
+## Overview
+
+Automatically detects novel patterns from completed work and prompts for skill library contribution. Triggers after phase transitions and plan completions.
+
+## How It Works
+
+### Trigger Points
+
+1. **After `/fire-transition`** — Scans all RECORD.md files from completed phase
+2. **After `/fire-4-verify` PASSED** — Scans verification report for novel patterns
+3. **After `/fire-5-handoff`** — Scans handoff for skills_applied and new patterns
+
+### Detection Patterns
+
+The system scans for these signals in RECORD.md and handoff files:
+
+```markdown
+## Signal 1: Explicit Skill Markers
+Look for: /* SKILL: name */ ... /* END SKILL */
+Action: Extract marked block, prompt to save as skill
+
+## Signal 2: Honesty Checkpoints with Research
+Look for: "Research Conducted:", "Resolution:", "Confidence After Research: High"
+Action: The gap + resolution combo is a potential skill
+
+## Signal 3: Novel Decisions
+Look for: "Decision:" or "Assumption:" with "Rationale:"
+Action: Decision patterns that could help future phases
+
+## Signal 4: Repeated Patterns
+Look for: Same file modification pattern across 2+ plans
+Action: Recurring pattern = candidate for abstraction into skill
+
+## Signal 5: Bug Fix Patterns
+Look for: "Root Cause:", "Fix:", "Prevention:"
+Action: Bug patterns with prevention strategies = high-value skills
+```
+
+### Extraction Process
+
+```
+1. SCAN completed work artifacts (RECORD.md, handoff, verification)
+2. DETECT skill candidates using patterns above
+3. CLASSIFY by category:
+   - database-solutions/
+   - patterns-standards/
+   - deployment-security/
+   - integrations/
+   - video-media/
+   - ecommerce/
+   - form-solutions/
+   - advanced-features/
+   - automation/
+   - document-processing/
+   - methodology/
+   - [new: react/, nodejs/, postgresql/, stripe/]
+4. PROMPT user:
+   "Detected potential skill: [name]
+    Category: [category]
+    Source: [file:lines]
+    Save to skills library? (y/n/edit)"
+5. If yes: Write skill file using standard template
+6. UPDATE skills-library/SKILLS_LIBRARY_INDEX.md
+```
+
+### Skill File Template
+
+```markdown
+# [Skill Name]
+
+**Category:** [category]
+**Difficulty:** [1-5 stars]
+**Date Added:** [auto]
+**Source:** [phase/plan that generated it]
+
+## Problem
+[What problem this solves]
+
+## Why It's Difficult
+[Why this isn't obvious]
+
+## Solution
+[Complete solution with code examples]
+
+## Before/After
+```code
+// Before (broken/inefficient)
+[code]
+
+// After (fixed/optimized)
+[code]
+```
+
+## Prevention
+[How to avoid this problem in future]
+
+## Testing
+[How to verify the fix works]
+```
+
+### Integration with .claude Init
+
+The auto-extraction is referenced in Dominion Flow's session hooks. When a phase completes:
+
+1. Dominion Flow `/fire-transition` command includes extraction step
+2. The transition workflow scans artifacts
+3. Detected skills are presented to user
+4. Approved skills are written to library
+5. SKILLS_LIBRARY_INDEX.md is updated
+
+No external hooks needed — it's built into the workflow commands themselves.
+
+### Configuration
+
+In project `.planning/config.json`:
+```json
+{
+  "auto_skill_extraction": {
+    "enabled": true,
+    "auto_prompt": true,
+    "min_confidence": "medium",
+    "categories_enabled": "all",
+    "skip_patterns": ["console.log", "TODO", "FIXME"]
+  }
+}
+```
+
+### Manual Trigger
+
+```
+/fire-search --extract-from .planning/phases/[phase]/
+```
+
+Scans a specific phase directory for skill candidates.