agileflow 2.90.7 → 2.92.0

package/src/core/agents/epic-planner.md

@@ -3,6 +3,12 @@ name: agileflow-epic-planner
 description: Epic and story planning specialist. Use for breaking down large features into epics and stories, writing acceptance criteria, estimating effort, and mapping dependencies.
 tools: Read, Write, Edit, Glob, Grep
 model: sonnet
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/story-format-validator.js"
 compact_context:
   priority: "high"
   preserve_rules:

package/src/core/agents/integrations.md

@@ -3,6 +3,12 @@ name: agileflow-integrations
 description: Integration specialist for third-party APIs, webhooks, payment processors, external services, and API connectivity.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/security-validator.js"
 compact_context:
   priority: "high"
   preserve_rules:

package/src/core/agents/mentor.md

@@ -3,6 +3,12 @@ name: agileflow-mentor
 description: End-to-end implementation mentor. Use for guiding feature implementation from idea to PR, researching approaches, creating missing epics/stories, and orchestrating multi-step workflows.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: sonnet
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/json-schema-validator.js"
 compact_context:
   priority: "critical"
   preserve_rules:

package/src/core/agents/mobile.md

@@ -3,6 +3,12 @@ name: agileflow-mobile
 description: Mobile specialist for React Native, Flutter, cross-platform mobile development, and mobile-specific features.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/component-validator.js"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/agents/monitoring.md

@@ -3,6 +3,12 @@ name: agileflow-monitoring
 description: Monitoring specialist for observability, logging strategies, alerting rules, metrics dashboards, and production visibility.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/json-schema-validator.js"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/agents/multi-expert.md

@@ -3,6 +3,12 @@ name: agileflow-multi-expert
 description: Multi-expert orchestrator that deploys 3-5 domain experts on the same problem and synthesizes results for high-confidence answers.
 tools: Read, Write, Edit, Bash, Glob, Grep, Task, TaskOutput
 model: sonnet
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/json-schema-validator.js"
 compact_context:
   priority: "high"
   preserve_rules:

package/src/core/agents/performance.md

@@ -3,6 +3,12 @@ name: agileflow-performance
 description: Performance specialist for optimization, profiling, benchmarking, scalability, and performance-critical features.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Bash"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/test-result-validator.js"
 ---
 
 ## STEP 0: Gather Context

package/src/core/agents/product.md

@@ -3,6 +3,12 @@ name: agileflow-product
 description: Product specialist for requirements analysis, user stories, acceptance criteria clarity, and feature validation before epic planning.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/story-format-validator.js"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/agents/qa.md

@@ -3,6 +3,12 @@ name: agileflow-qa
 description: QA specialist for test strategy, test planning, quality metrics, regression testing, and release readiness validation.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Bash"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/test-result-validator.js"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/agents/readme-updater.md

@@ -3,6 +3,12 @@ name: agileflow-readme-updater
 description: README specialist for auditing and updating all documentation files across project folders.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/markdown-validator.js"
 compact_context:
   priority: medium
   preserve_rules:

package/src/core/agents/refactor.md

@@ -3,6 +3,12 @@ name: agileflow-refactor
 description: Refactoring specialist for technical debt cleanup, legacy code modernization, codebase health, and code quality improvements.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Bash"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/test-result-validator.js"
 compact_context:
   priority: "high"
   preserve_rules:

package/src/core/agents/research.md

@@ -3,6 +3,12 @@ name: agileflow-research
 description: Research specialist. Use for gathering technical information, creating research prompts for ChatGPT, saving research notes, and maintaining the research index.
 tools: Read, Write, Edit, Glob, Grep, WebFetch, WebSearch
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/markdown-validator.js"
 compact_context:
   priority: "high"
   preserve_rules:

package/src/core/agents/security.md

@@ -3,6 +3,12 @@ name: agileflow-security
 description: Security specialist for vulnerability analysis, authentication patterns, authorization, compliance, and security reviews before release.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/security-validator.js"
 compact_context:
   priority: critical
   preserve_rules:

package/src/core/agents/testing.md

@@ -3,6 +3,16 @@ name: agileflow-testing
 description: Testing specialist for test strategy, test patterns, coverage optimization, and comprehensive test suite design (different from CI infrastructure).
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Bash"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/test-result-validator.js"
+  Stop:
+    - hooks:
+        - type: command
+          command: "echo 'Testing agent complete - verify test_status in status.json'"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/agents/ui.md

@@ -3,6 +3,12 @@ name: agileflow-ui
 description: UI/presentation layer specialist. Use for implementing front-end components, styling, theming, accessibility features, and stories tagged with owner AG-UI.
 tools: Read, Write, Edit, Bash, Glob, Grep
 model: haiku
+hooks:
+  PostToolUse:
+    - matcher: "Write"
+      hooks:
+        - type: command
+          command: "node .agileflow/hooks/validators/component-validator.js"
 compact_context:
   priority: high
   preserve_rules:

package/src/core/commands/adr.md

@@ -269,6 +269,120 @@ After successfully creating the ADR, offer next steps:
 
 ---
 
+## Expected Output
+
+### Successful ADR Creation
+
+```
+📋 Creating ADR: ADR-0042
+
+Checking existing ADRs...
+✅ Next sequential number: 0042
+
+Title: Use PostgreSQL for persistence
+Status: accepted
+
+Files to create:
+───────────────────────────────────
+1. docs/03-decisions/adr-0042-postgresql.md
+
+Preview:
+─────────────────────────────────────────────
+---
+number: 0042
+title: Use PostgreSQL for persistence
+date: 2026-01-21
+status: accepted
+tags: [database, architecture]
+---
+
+# ADR-0042: Use PostgreSQL for persistence
+
+## Context
+Need reliable ACID-compliant database for financial transactions.
+Evaluated MongoDB (eventual consistency), Redis (memory limits),
+and PostgreSQL (full ACID with JSON support).
+
+## Decision
+Use PostgreSQL 16 with native JSON support for document storage
+while maintaining ACID guarantees.
+
+## Consequences
+### Positive
+- Full ACID compliance for financial data
+- Native JSON/JSONB for flexible schemas
+- Mature ecosystem and tooling
+
+### Negative
+- Team needs PostgreSQL training
+- Slightly more complex operational setup
+- Vertical scaling limitations
+
+## Related
+- [ADR-0041](adr-0041-db-evaluation.md)
+- [US-0055](../06-stories/US-0055.md)
+─────────────────────────────────────────────
+
+[AskUserQuestion: "Create this ADR? (YES/NO)"]
+
+✅ ADR-0042 created successfully!
+   docs/03-decisions/adr-0042-postgresql.md
+
+[AskUserQuestion: "What would you like to do next?"]
+```
+
+### Missing Required Inputs
+
+```
+❌ Missing required inputs
+
+The following inputs are required:
+  • NUMBER - 4-digit sequential ID (e.g., 0042)
+  • TITLE - Decision title
+  • CONTEXT - Why this decision is needed
+  • DECISION - What was chosen
+  • CONSEQUENCES - Trade-offs (positive and negative)
+
+Usage:
+/agileflow:adr NUMBER=0042 TITLE="Use PostgreSQL" CONTEXT="Need ACID..." DECISION="PostgreSQL chosen" CONSEQUENCES="Better integrity, learning curve"
+```
+
+### Non-Sequential Number Warning
+
+```
+⚠️ Non-sequential ADR number
+
+Requested: ADR-0100
+Last ADR: ADR-0042
+Next expected: ADR-0043
+
+Do you want to:
+  1. Use sequential number (0043) - Recommended
+  2. Keep requested number (0100)
+  3. Cancel
+
+[AskUserQuestion: Select option]
+```
+
+### ADR Already Exists
+
+```
+❌ ADR-0042 already exists
+
+Existing ADR:
+  Title: Use PostgreSQL for persistence
+  Date: 2026-01-15
+  Status: accepted
+
+To update this ADR:
+  /agileflow:adr:update NUMBER=0042 STATUS=superseded
+
+To create a new ADR:
+  /agileflow:adr NUMBER=0043 TITLE="..."
+```
+
+---
+
 ## Related Commands
 
 - `/agileflow:adr:list` - View all ADRs with status

package/src/core/commands/agent.md

@@ -124,3 +124,123 @@ ACTIONS
 3) Print a persona snippet to paste as that terminal's system prompt.
 
 Diff-first; YES/NO.
+
+---
+
+## Expected Output
+
+### Successful Agent Onboarding
+
+```
+📋 Onboarding New Agent: AG-UI
+
+AGENT_ID: AG-UI
+ROLE: Frontend Developer
+TOOLS: Read, Write, Edit, Bash, Glob
+SCOPE:
+  - Directories: src/components/, src/pages/
+  - Story Tags: frontend, ui, ux
+
+Files to create:
+───────────────────────────────────────────────
+1. docs/02-practices/prompts/agents/agent-AG-UI.md
+
+Preview:
+─────────────────────────────────────────────
+---
+agent_id: AG-UI
+role: Frontend Developer
+tools: [Read, Write, Edit, Bash, Glob]
+scope:
+  directories: [src/components/, src/pages/]
+  story_tags: [frontend, ui, ux]
+---
+
+# AG-UI: Frontend Developer Agent
+
+## Responsibilities
+Build and maintain user interface components, pages, and styling.
+
+## System Prompt (Contract)
+**Scope**: Only modify files in src/components/ and src/pages/
+**Testing**: Run `npm test` before committing
+**Commits**: Prefix with "feat(ui):" or "fix(ui):"
+**Status**: Update status.json after completing stories
+─────────────────────────────────────────────
+
+2. docs/09-agents/roster.yaml (update)
+
+   + agents:
+   +   - id: AG-UI
+   +     role: Frontend Developer
+   +     tools: [Read, Write, Edit, Bash, Glob]
+   +     scope:
+   +       directories: [src/components/, src/pages/]
+   +       story_tags: [frontend, ui, ux]
+
+[AskUserQuestion: "Create this agent profile?"]
+
+✅ Agent onboarded successfully!
+   Profile: docs/02-practices/prompts/agents/agent-AG-UI.md
+   Roster: docs/09-agents/roster.yaml updated
+
+📝 System Prompt Snippet (paste into terminal):
+
+You are AG-UI, a Frontend Developer agent.
+Your scope is limited to: src/components/, src/pages/
+You work on stories tagged: frontend, ui, ux
+Always run tests before committing.
+Always update status.json after completing work.
+```
+
+### Missing Required Inputs
+
+```
+❌ Missing required inputs
+
+Please provide:
+  • AGENT_ID - Agent identifier (e.g., AG-UI, AG-API)
+  • ROLE - Agent role description (e.g., "Frontend Developer")
+
+Optional:
+  • TOOLS - Available tools (default: Read, Write, Edit, Bash, Glob)
+  • SCOPE - Directories and story tags
+
+Usage:
+/agileflow:agent AGENT_ID=AG-UI ROLE="Frontend Developer" TOOLS="Read,Write,Edit,Bash,Glob" SCOPE="src/components/,frontend"
+```
+
+### Agent Already Exists
+
+```
+⚠️ Agent already exists: AG-UI
+
+Existing agent profile: docs/02-practices/prompts/agents/agent-AG-UI.md
+
+Options:
+  1. Update existing agent profile
+  2. Create new agent with different ID
+  3. Cancel
+
+[AskUserQuestion: "How to proceed?"]
+```
+
+### Roster File Created
+
+```
+📋 Onboarding New Agent: AG-API
+
+Note: docs/09-agents/roster.yaml does not exist.
+Creating new roster file.
+
+Files to create:
+───────────────────────────────────────────────
+1. docs/02-practices/prompts/agents/agent-AG-API.md
+2. docs/09-agents/roster.yaml (NEW)
+
+[AskUserQuestion: "Create agent profile and roster?"]
+
+✅ Agent onboarded successfully!
+   Profile: docs/02-practices/prompts/agents/agent-AG-API.md
+   Roster: docs/09-agents/roster.yaml created
+```

package/src/core/commands/assign.md

@@ -212,3 +212,148 @@ ACTIONS
 **JSON Safety**: Always use jq or Edit tool (never echo/cat > status.json). Validate after modifications.
 
 Preview changes; YES/NO.
+
+---
+
+## Expected Output
+
+### Successful Assignment
+
+```
+📋 Assigning Story: US-0042
+
+Current state:
+  Owner: unassigned
+  Status: ready
+
+New assignment:
+  Owner: AG-UI
+  Status: in-progress
+
+Files to update:
+───────────────────────────────────────────────
+1. docs/06-stories/EP-0010/US-0042-login-form.md
+
+   Frontmatter changes:
+   -owner: unassigned
+   +owner: AG-UI
+   -status: ready
+   +status: in-progress
+   +updated: 2026-01-21T14:30:00Z
+
+2. docs/09-agents/status.json
+
+   "US-0042": {
+     -"owner": "unassigned",
+     +"owner": "AG-UI",
+     -"status": "ready",
+     +"status": "in-progress",
+     +"last_update": "2026-01-21T14:30:00Z"
+   }
+
+3. docs/09-agents/bus/log.jsonl (append)
+
+   + {"ts":"2026-01-21T14:30:00Z","type":"assign","from":"SYSTEM","to":"AG-UI","story":"US-0042","status":"in-progress"}
+
+[AskUserQuestion: "Assign US-0042 to AG-UI as in-progress?"]
+
+✅ Assignment complete!
+   Story: US-0042
+   New owner: AG-UI
+   Status: in-progress
+   Bus message sent: assign → AG-UI
+```
+
+### Story Not Found
+
+```
+❌ Story not found: US-9999
+
+Searched:
+  - docs/06-stories/**/US-9999*.md
+  - docs/09-agents/status.json
+
+Available stories:
+  - US-0042: Login form (ready)
+  - US-0043: Profile page (ready)
+  - US-0044: Dashboard (in-progress)
+
+Usage:
+/agileflow:assign STORY=US-0042 NEW_OWNER=AG-UI
+```
+
+### WIP Limit Warning
+
+```
+⚠️ WIP Limit Warning
+
+AG-UI currently has 2 stories in-progress:
+  - US-0038: OAuth flow (in-progress, 3 days)
+  - US-0041: Session management (in-progress, 1 day)
+
+Assigning US-0042 would exceed WIP limit (max 2 per agent).
+
+Options:
+  1. Complete US-0038 or US-0041 first
+  2. Reassign one story to another agent
+  3. Proceed anyway (override WIP limit)
+
+[AskUserQuestion: "How to proceed?"]
+  - Complete existing story first (Recommended)
+  - Assign to different agent
+  - Proceed (override WIP limit)
+```
+
+### Invalid Status Transition
+
+```
+❌ Invalid status transition
+
+Story: US-0042
+Current status: done
+Requested status: in-progress
+
+Cannot transition from 'done' to 'in-progress'.
+
+Valid transitions from 'done':
+  - No valid transitions (story is complete)
+
+To reopen this story:
+  1. Create a new story for follow-up work
+  2. Or use /agileflow:status STORY=US-0042 STATUS=ready FORCE=yes
+```
+
+### Reassignment (Owner Change)
+
+```
+📋 Reassigning Story: US-0042
+
+Current owner: AG-API
+New owner: AG-UI
+Status: in-progress (unchanged)
+
+Reason: "Frontend specialist needed for UI work"
+
+Files to update:
+───────────────────────────────────────────────
+1. docs/06-stories/EP-0010/US-0042-login-form.md
+   -owner: AG-API
+   +owner: AG-UI
+
+2. docs/09-agents/status.json
+   "US-0042": {
+     -"owner": "AG-API",
+     +"owner": "AG-UI",
+   }
+
+3. docs/09-agents/bus/log.jsonl (append)
+   + {"type":"reassign","from":"AG-API","to":"AG-UI","story":"US-0042","text":"Frontend specialist needed"}
+
+[AskUserQuestion: "Reassign US-0042 from AG-API to AG-UI?"]
+
+✅ Reassignment complete!
+   Story: US-0042
+   Previous owner: AG-API
+   New owner: AG-UI
+   Notification sent to both agents
+```