wogiflow 1.0.17 → 1.0.18

package/.workflow/specs/architecture.md.template

@@ -0,0 +1,24 @@
+# Architecture
+
+## Pattern
+
+<!-- Detected during onboarding -->
+<!-- Examples: MVC, Clean Architecture, DDD, Microservices, Monolith -->
+
+## Structure
+
+<!-- Project structure overview -->
+<!-- Key directories and their purposes -->
+
+## Key Decisions
+
+<!-- Architecture decisions made for this project -->
+<!-- Trade-offs and rationale -->
+
+## Dependencies
+
+<!-- Major dependencies and their purposes -->
+
+---
+
+*This file is auto-populated during `flow onboard`. Update manually as architecture evolves.*

package/.workflow/specs/stack.md.template

@@ -0,0 +1,33 @@
+# Tech Stack
+
+## Framework
+
+<!-- Primary framework (e.g., Next.js, NestJS, FastAPI) -->
+
+## Language
+
+<!-- Primary language (e.g., TypeScript, Python, Go) -->
+
+## Database
+
+<!-- Database system if applicable (e.g., PostgreSQL, MongoDB) -->
+
+## Package Manager
+
+<!-- npm, yarn, pnpm, pip, etc. -->
+
+## Build Tools
+
+<!-- Build and bundling tools (e.g., Vite, Webpack, esbuild) -->
+
+## Testing
+
+<!-- Test frameworks (e.g., Jest, Vitest, pytest) -->
+
+## Other Tools
+
+<!-- Linters, formatters, CI/CD tools -->
+
+---
+
+*This file is auto-populated during `flow onboard`. Update manually as stack evolves.*

package/.workflow/specs/testing.md.template

@@ -0,0 +1,36 @@
+# Testing
+
+## Test Framework
+
+<!-- Primary test framework (e.g., Jest, Vitest, pytest) -->
+
+## Test Commands
+
+```bash
+# Run all tests
+npm test
+
+# Run tests in watch mode
+npm run test:watch
+
+# Run specific test file
+npm test -- path/to/test.ts
+```
+
+## Test Structure
+
+<!-- Where tests are located -->
+<!-- Naming conventions -->
+
+## Coverage
+
+<!-- Coverage requirements if any -->
+<!-- Coverage commands -->
+
+## E2E Testing
+
+<!-- E2E framework if used (e.g., Playwright, Cypress) -->
+
+---
+
+*This file is auto-populated during `flow onboard`. Update manually as testing strategy evolves.*

package/.workflow/templates/api-map.md.template

@@ -0,0 +1,37 @@
+# API Registry
+
+Quick reference of API calls and endpoints. **Check before creating anything new.**
+
+> Run `flow api-index scan` to populate this file.
+
+---
+
+## User Endpoints
+
+| Endpoint | Method | Purpose | File |
+|----------|--------|---------|------|
+| `/api/users` | GET | Fetch all users | `src/api/users.ts` |
+| `/api/users/:id` | GET | Fetch single user | `src/api/users.ts` |
+
+---
+
+## API Client Functions
+
+### Users
+
+| Function | Method | Endpoint | File |
+|----------|--------|----------|------|
+| `fetchUsers` | GET | /api/users | `src/api/users.ts` |
+| `createUser` | POST | /api/users | `src/api/users.ts` |
+
+---
+
+## Rules
+
+1. **Before creating** → Search this file for existing API calls
+2. **If similar exists** → Extend with parameter or options
+3. **After creating** → Run `flow api-index scan` to update
+
+---
+
+Last scanned: _Not yet scanned_

package/.workflow/templates/claude-md.hbs

@@ -37,16 +37,25 @@ Check `.workflow/state/ready.json` for existing tasks.
 
 ### Step 3: Assess task size
 
-| Size | Criteria | Action |
-|------|----------|--------|
-| **Small** | < {{config.enforcement.taskSizeThresholds.small.maxFiles}} files, < {{config.enforcement.taskSizeThresholds.small.maxHours}} hour, obvious scope | Create task inline, proceed with `/wogi-start` |
-| **Medium** | {{config.enforcement.taskSizeThresholds.small.maxFiles}}-{{config.enforcement.taskSizeThresholds.medium.maxFiles}} files, {{config.enforcement.taskSizeThresholds.small.maxHours}}-{{config.enforcement.taskSizeThresholds.medium.maxHours}} hours, some complexity | **STOP** - Create story first |
-| **Large** | > {{config.enforcement.taskSizeThresholds.medium.maxFiles}} files, > {{config.enforcement.taskSizeThresholds.medium.maxHours}} hours, new feature | **STOP** - Create story first |
+| Level | Type | Files | Criteria | Action |
+|-------|------|-------|----------|--------|
+| L3 | **Subtask** | 1 | Atomic operation, trivial | Execute inline |
+| L2 | **Task** | 1-5 | Single concern, 1-3 AC | Create task, proceed with `/wogi-start` |
+| L1 | **Story** | 5-15 | Multi-component, 3-10 AC | **STOP** - Create story first |
+| L0 | **Epic** | 15+ | New subsystem, 3+ stories | **STOP** - Create epic, decompose to stories |
 
-### For Medium/Large Tasks:
+**Classification Keywords:**
+- Epic indicators: system, architecture, migration, redesign, platform
+- Story indicators: feature, flow, integration, module, workflow
+- Task indicators: add, fix, update, change, remove
 
+Note: WogiFlow can auto-classify requests. If unsure, default to creating a story for medium+ requests.
+
+### For Story/Epic Requests:
+
+**For Stories (L1):**
 ```
-This looks like a medium/large task.
+This looks like a story-level feature (5-15 files).
 
 Before I start implementing, I need to create a story with acceptance criteria.
 
@@ -60,6 +69,22 @@ Then:
 2. **WAIT for user approval** on the story
 3. Only then proceed with `/wogi-start`
 
+**For Epics (L0):**
+```
+This is a large feature that qualifies as an Epic (15+ files, multiple stories).
+
+I'll need to decompose this into stories first.
+
+**Proposed epic:** "[title based on request]"
+
+Should I create this epic and decompose it into stories for your approval?
+```
+
+Then:
+1. Run `/wogi-epic "[title]"` to create the epic with story breakdown
+2. **WAIT for user approval** on the epic structure
+3. Start with the first story using `/wogi-start`
+
 **This is NON-NEGOTIABLE when strict mode is enabled.**
 
 ---
@@ -175,6 +200,29 @@ After EVERY request that changes files:
 2. Search codebase for existing
 3. Priority: Use existing → Add variant → Extend → Create new (last resort)
 
+## Function & API Reuse
+
+**Before creating ANY new utility function or API call:**
+
+1. **Check `function-map.md`** for existing utilities
+   - Search by purpose (date formatting, validation, parsing)
+   - Check if extending an existing function makes sense
+
+2. **Check `api-map.md`** for existing API endpoints
+   - Search by entity type (users, products, orders)
+   - Check if existing endpoint can be parameterized
+
+3. **Evaluate**: Can you extend an existing item instead of creating new?
+   - Same intent? → Extend with variant/parameter
+   - Similar but different? → Create new, reference existing
+   - Completely new? → Create and register
+
+**Decision criteria**: Does extending require LESS effort AND make logical sense?
+
+**After creating new functions/APIs:**
+- Run `flow function-index scan` to update the function registry
+- Run `flow api-index scan` to update the API registry
+
 {{#if skills}}
 ## Installed Skills
 
@@ -193,6 +241,8 @@ Check `.claude/skills/[name]/skill.md` for skill-specific guidance.
 | Tasks | `.workflow/state/ready.json` |
 | Logs | `.workflow/state/request-log.md` |
 | Components | `.workflow/state/app-map.md` |
+| Functions | `.workflow/state/function-map.md` |
+| APIs | `.workflow/state/api-map.md` |
 | Rules | `.workflow/state/decisions.md` |
 | Progress | `.workflow/state/progress.md` |
 | Roadmap | `.workflow/roadmap.md` |

package/.workflow/templates/function-map.md.template

@@ -0,0 +1,33 @@
+# Function Registry
+
+Quick reference of utility functions. **Check before creating anything new.**
+
+> Run `flow function-index scan` to populate this file.
+
+---
+
+## Utilities
+
+| Function | Purpose | File | Parameters |
+|----------|---------|------|------------|
+| _Example_ | Format dates for display | `src/utils/date.ts` | date: Date, format?: string |
+
+---
+
+## Helpers
+
+| Function | Purpose | File | Parameters |
+|----------|---------|------|------------|
+| _Example_ | Validate email format | `src/helpers/validation.ts` | email: string |
+
+---
+
+## Rules
+
+1. **Before creating** → Search this file
+2. **If similar exists** → Extend with parameter, don't create new
+3. **After creating** → Run `flow function-index scan` to update
+
+---
+
+Last scanned: _Not yet scanned_

package/lib/installer.js

@@ -254,7 +254,9 @@ function createWorkflowStructure(projectRoot, config) {
     { name: 'request-log.md', content: '# Request Log\n\nAutomatic log of all requests that changed files.\n\n---\n' },
     { name: 'decisions.md', content: '# Project Decisions\n\nKey decisions and patterns for this project.\n\n---\n' },
     { name: 'app-map.md', content: '# Application Map\n\nComponent registry for this project.\n\n---\n' },
-    { name: 'progress.md', content: '# Progress Notes\n\nSession handoff notes.\n\n---\n' }
+    { name: 'progress.md', content: '# Progress Notes\n\nSession handoff notes.\n\n---\n' },
+    { name: 'function-map.md', content: '# Function Registry\n\nUtility function registry. Run `flow function-index scan` to populate.\n\n---\n' },
+    { name: 'api-map.md', content: '# API Registry\n\nAPI calls registry. Run `flow api-index scan` to populate.\n\n---\n' }
   ];
 
   for (const file of stateFiles) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wogiflow",
-  "version": "1.0.17",
+  "version": "1.0.18",
   "description": "AI-powered development workflow management system with multi-model support",
   "main": "lib/index.js",
   "bin": {

package/scripts/flow

@@ -92,8 +92,17 @@ show_help() {
     echo "  map-index scan       Rescan codebase"
     echo "  map-sync             Compare index with app-map"
     echo ""
+    echo "Functions & APIs:"
+    echo "  function-index scan  Scan for utility functions"
+    echo "  function-index show  Show function details"
+    echo "  function-index map   Regenerate function-map.md"
+    echo "  api-index scan       Scan for API calls"
+    echo "  api-index show       Show API function or endpoint"
+    echo "  api-index map        Regenerate api-map.md"
+    echo ""
     echo "Skills & Learning:"
     echo "  skill-learn          Extract learnings from recent changes"
+    echo "  auto-learn           Auto-learn from session reviews and bug fixes"
     echo "  skill-create <name>  Create a new skill"
     echo "  skill-create --list  List existing skills"
     echo "  skill detect         Detect frameworks in project"
@@ -108,6 +117,22 @@ show_help() {
     echo "  correct list         List recent corrections"
     echo "  aggregate            Aggregate learnings across skills"
     echo "  aggregate --promote  Interactive promotion wizard"
+    echo "  pattern-enforce      Enforce patterns from decisions/app-map"
+    echo ""
+    echo "Code Analysis:"
+    echo "  code-intel analyze   Analyze imports/exports in codebase"
+    echo "  code-intel deps      Show dependency graph"
+    echo "  review               Code review with auto multi-pass detection"
+    echo "  review --multipass   Force multi-pass review mode"
+    echo ""
+    echo "Error Recovery:"
+    echo "  error-recovery analyze  Analyze error output hierarchically"
+    echo "  error-recovery status   Show recovery session status"
+    echo ""
+    echo "Epics:"
+    echo "  epic list            List all epics"
+    echo "  epic show <id>       Show epic details and progress"
+    echo "  epic create          Create a new epic"
     echo ""
     echo "Code Traces:"
     echo "  trace \"<prompt>\"     Generate task-focused code trace"
@@ -419,9 +444,33 @@ case "${1:-}" in
     map-sync)
         "$SCRIPT_DIR/flow-map-sync" "${@:2}"
         ;;
+    function-index)
+        node "$SCRIPT_DIR/flow-function-index.js" "${@:2}"
+        ;;
+    api-index)
+        node "$SCRIPT_DIR/flow-api-index.js" "${@:2}"
+        ;;
     skill-learn)
         node "$SCRIPT_DIR/flow-skill-learn.js" "${@:2}"
         ;;
+    auto-learn)
+        node "$SCRIPT_DIR/flow-auto-learn.js" "${@:2}"
+        ;;
+    code-intel|code-intelligence)
+        node "$SCRIPT_DIR/flow-code-intelligence.js" "${@:2}"
+        ;;
+    error-recovery)
+        node "$SCRIPT_DIR/flow-error-recovery.js" "${@:2}"
+        ;;
+    epic|epics)
+        node "$SCRIPT_DIR/flow-epics.js" "${@:2}"
+        ;;
+    pattern-enforce)
+        node "$SCRIPT_DIR/flow-pattern-enforcer.js" "${@:2}"
+        ;;
+    review)
+        node "$SCRIPT_DIR/flow-review.js" "${@:2}"
+        ;;
     correct)
         node "$SCRIPT_DIR/flow-correct.js" "${@:2}"
         ;;
@@ -486,13 +535,13 @@ case "${1:-}" in
     loop)
         case "${2:-status}" in
             status)
-                node "$SCRIPT_DIR/flow-loop-enforcer.js" status
+                node "$SCRIPT_DIR/flow-task-enforcer.js" status
                 ;;
             stats)
-                node "$SCRIPT_DIR/flow-loop-enforcer.js" stats
+                node "$SCRIPT_DIR/flow-task-enforcer.js" stats
                 ;;
             can-exit)
-                node "$SCRIPT_DIR/flow-loop-enforcer.js" can-exit
+                node "$SCRIPT_DIR/flow-task-enforcer.js" can-exit
                 ;;
             enable)
                 node "$SCRIPT_DIR/flow-config-set.js" loops.enforced true