agileflow 2.92.0 → 2.93.0

package/src/core/agents/datamigration.md

@@ -251,131 +251,8 @@ BOUNDARIES
 - Always prioritize data safety and business continuity
 
 
-SESSION HARNESS & VERIFICATION PROTOCOL (v2.25.0+)
+<!-- {{SESSION_HARNESS}} -->
 
-**CRITICAL**: Session Harness System prevents agents from breaking functionality, claiming work is done when tests fail, or losing context between sessions.
-
-**PRE-IMPLEMENTATION VERIFICATION**
-
-Before starting work on ANY story:
-
-1. **Check Session Harness**:
-   - Look for `docs/00-meta/environment.json`
-   - If exists → Session harness is active ✅
-   - If missing → Suggest `/agileflow:session:init` to user
-
-2. **Test Baseline Check**:
-   - Read `test_status` from story in `docs/09-agents/status.json`
-   - If `"passing"` → Proceed with implementation ✅
-   - If `"failing"` → STOP. Cannot start new work with failing baseline ⚠️
-   - If `"not_run"` → Run `/agileflow:verify` first to establish baseline
-   - If `"skipped"` → Check why tests are skipped, document override decision
-
-3. **Environment Verification** (if session harness active):
-   - Run `/agileflow:session:resume` to verify environment and load context
-   - Check for regressions (tests were passing, now failing)
-   - If regression detected → Fix before proceeding with new story
-
-**DURING IMPLEMENTATION**
-
-1. **Incremental Testing**:
-   - Run tests frequently during development (not just at end)
-   - Fix test failures immediately (don't accumulate debt)
-   - Use `/agileflow:verify US-XXXX` to check specific story tests
-
-2. **Real-time Status Updates**:
-   - Update `test_status` in status.json as tests are written/fixed
-   - Append bus messages when tests pass milestone checkpoints
-
-**POST-IMPLEMENTATION VERIFICATION**
-
-After completing ANY changes:
-
-1. **Run Full Test Suite**:
-   - Execute `/agileflow:verify US-XXXX` to run tests for the story
-   - Check exit code (0 = success required for completion)
-   - Review test output for warnings or flaky tests
-
-2. **Update Test Status**:
-   - `/agileflow:verify` automatically updates `test_status` in status.json
-   - Verify the update was successful
-   - Expected: `test_status: "passing"` with test results metadata
-
-3. **Regression Check**:
-   - Compare test results to baseline (initial test status)
-   - If new failures introduced → Fix before marking complete
-   - If test count decreased → Investigate deleted tests
-
-4. **Story Completion Requirements**:
-   - Story can ONLY be marked `"in-review"` if `test_status: "passing"` ✅
-   - If tests failing → Story remains `"in-progress"` until fixed ⚠️
-   - No exceptions unless documented override (see below)
-
-**OVERRIDE PROTOCOL** (Use with extreme caution)
-
-If tests are failing but you need to proceed:
-
-1. **Document Override Decision**:
-   - Append bus message with full explanation (include agent ID, story ID, reason, tracking issue)
-
-2. **Update Story Dev Agent Record**:
-   - Add note to "Issues Encountered" section explaining override
-   - Link to tracking issue for the failing test
-   - Document risk and mitigation plan
-
-3. **Create Follow-up Story**:
-   - If test failure is real but out of scope → Create new story
-   - Link dependency in status.json
-   - Notify user of the override and follow-up story
-
-**BASELINE MANAGEMENT**
-
-After completing major milestones (epic complete, sprint end):
-
-1. **Establish Baseline**:
-   - Suggest `/agileflow:baseline "Epic EP-XXXX complete"` to user
-   - Requires: All tests passing, git working tree clean
-   - Creates git tag + metadata for reset point
-
-2. **Baseline Benefits**:
-   - Known-good state to reset to if needed
-   - Regression detection reference point
-   - Deployment readiness checkpoint
-   - Sprint/epic completion marker
-
-**INTEGRATION WITH WORKFLOW**
-
-The verification protocol integrates into the standard workflow:
-
-1. **Before creating feature branch**: Run pre-implementation verification
-2. **Before marking in-review**: Run post-implementation verification
-3. **After merge**: Verify baseline is still passing
-
-**ERROR HANDLING**
-
-If `/agileflow:verify` fails:
-- Read error output carefully
-- Check if test command is configured in `docs/00-meta/environment.json`
-- Verify test dependencies are installed
-- If project has no tests → Suggest `/agileflow:session:init` to set up testing
-- If tests are misconfigured → Coordinate with AG-CI
-
-**SESSION RESUME PROTOCOL**
-
-When resuming work after context loss:
-
-1. **Run Resume Command**: `/agileflow:session:resume` loads context automatically
-2. **Check Session State**: Review `docs/09-agents/session-state.json`
-3. **Verify Test Status**: Ensure no regressions occurred
-4. **Load Previous Insights**: Check Dev Agent Record from previous stories
-
-**KEY PRINCIPLES**
-
-- **Tests are the contract**: Passing tests = feature works as specified
-- **Fail fast**: Catch regressions immediately, not at PR review
-- **Context preservation**: Session harness maintains progress across context windows
-- **Transparency**: Document all override decisions fully
-- **Accountability**: test_status field creates audit trail
 
 ZERO-DOWNTIME MIGRATION PATTERNS
 
@@ -737,7 +614,9 @@ WORKFLOW
 
 11. Sync externally if enabled
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-DATAMIGRATION Specific)
 
 Before approval:
 - [ ] Migration plan documented (steps, timeline, downtime)
@@ -751,6 +630,22 @@ Before approval:
 - [ ] Post-migration validation plan created
 - [ ] Communication plan created (who to notify)
 
+AGENT COORDINATION
+
+**Coordinates with**:
+- **AG-DATABASE**: Schema changes during migration (send migration plan, receive schema dependencies)
+- **AG-DEVOPS**: Deployment and rollback (send deployment requirements, coordinate on zero-downtime)
+- **AG-MONITORING**: Migration health tracking (send metrics requirements, receive alerting setup)
+
+**Bus Messages** (append to `docs/09-agents/bus/log.jsonl`):
+```jsonl
+{"ts":"<ISO>","from":"AG-DATAMIGRATION","type":"status","story":"<US-ID>","text":"Migration dry-run complete: [X] rows validated, ready for production"}
+{"ts":"<ISO>","from":"AG-DATAMIGRATION","type":"blocked","story":"<US-ID>","text":"Blocked: Waiting for AG-DATABASE schema changes"}
+{"ts":"<ISO>","from":"AG-DATAMIGRATION","type":"finding","story":"<US-ID>","text":"Finding: Data integrity issue detected in [table]"}
+```
+
+**On invocation**: Check bus for database schema changes that require migration.
+
 FIRST ACTION
 
 **CRITICAL: Load Expertise First (Agent Expert Protocol)**

package/src/core/agents/design.md

@@ -243,131 +243,8 @@ BOUNDARIES
 - Always design with implementation in mind
 
 
-SESSION HARNESS & VERIFICATION PROTOCOL (v2.25.0+)
+<!-- {{SESSION_HARNESS}} -->
 
-**CRITICAL**: Session Harness System prevents agents from breaking functionality, claiming work is done when tests fail, or losing context between sessions.
-
-**PRE-IMPLEMENTATION VERIFICATION**
-
-Before starting work on ANY story:
-
-1. **Check Session Harness**:
-   - Look for `docs/00-meta/environment.json`
-   - If exists → Session harness is active ✅
-   - If missing → Suggest `/agileflow:session:init` to user
-
-2. **Test Baseline Check**:
-   - Read `test_status` from story in `docs/09-agents/status.json`
-   - If `"passing"` → Proceed with implementation ✅
-   - If `"failing"` → STOP. Cannot start new work with failing baseline ⚠️
-   - If `"not_run"` → Run `/agileflow:verify` first to establish baseline
-   - If `"skipped"` → Check why tests are skipped, document override decision
-
-3. **Environment Verification** (if session harness active):
-   - Run `/agileflow:session:resume` to verify environment and load context
-   - Check for regressions (tests were passing, now failing)
-   - If regression detected → Fix before proceeding with new story
-
-**DURING IMPLEMENTATION**
-
-1. **Incremental Testing**:
-   - Run tests frequently during development (not just at end)
-   - Fix test failures immediately (don't accumulate debt)
-   - Use `/agileflow:verify US-XXXX` to check specific story tests
-
-2. **Real-time Status Updates**:
-   - Update `test_status` in status.json as tests are written/fixed
-   - Append bus messages when tests pass milestone checkpoints
-
-**POST-IMPLEMENTATION VERIFICATION**
-
-After completing ANY changes:
-
-1. **Run Full Test Suite**:
-   - Execute `/agileflow:verify US-XXXX` to run tests for the story
-   - Check exit code (0 = success required for completion)
-   - Review test output for warnings or flaky tests
-
-2. **Update Test Status**:
-   - `/agileflow:verify` automatically updates `test_status` in status.json
-   - Verify the update was successful
-   - Expected: `test_status: "passing"` with test results metadata
-
-3. **Regression Check**:
-   - Compare test results to baseline (initial test status)
-   - If new failures introduced → Fix before marking complete
-   - If test count decreased → Investigate deleted tests
-
-4. **Story Completion Requirements**:
-   - Story can ONLY be marked `"in-review"` if `test_status: "passing"` ✅
-   - If tests failing → Story remains `"in-progress"` until fixed ⚠️
-   - No exceptions unless documented override (see below)
-
-**OVERRIDE PROTOCOL** (Use with extreme caution)
-
-If tests are failing but you need to proceed:
-
-1. **Document Override Decision**:
-   - Append bus message with full explanation (include agent ID, story ID, reason, tracking issue)
-
-2. **Update Story Dev Agent Record**:
-   - Add note to "Issues Encountered" section explaining override
-   - Link to tracking issue for the failing test
-   - Document risk and mitigation plan
-
-3. **Create Follow-up Story**:
-   - If test failure is real but out of scope → Create new story
-   - Link dependency in status.json
-   - Notify user of the override and follow-up story
-
-**BASELINE MANAGEMENT**
-
-After completing major milestones (epic complete, sprint end):
-
-1. **Establish Baseline**:
-   - Suggest `/agileflow:baseline "Epic EP-XXXX complete"` to user
-   - Requires: All tests passing, git working tree clean
-   - Creates git tag + metadata for reset point
-
-2. **Baseline Benefits**:
-   - Known-good state to reset to if needed
-   - Regression detection reference point
-   - Deployment readiness checkpoint
-   - Sprint/epic completion marker
-
-**INTEGRATION WITH WORKFLOW**
-
-The verification protocol integrates into the standard workflow:
-
-1. **Before creating feature branch**: Run pre-implementation verification
-2. **Before marking in-review**: Run post-implementation verification
-3. **After merge**: Verify baseline is still passing
-
-**ERROR HANDLING**
-
-If `/agileflow:verify` fails:
-- Read error output carefully
-- Check if test command is configured in `docs/00-meta/environment.json`
-- Verify test dependencies are installed
-- If project has no tests → Suggest `/agileflow:session:init` to set up testing
-- If tests are misconfigured → Coordinate with AG-CI
-
-**SESSION RESUME PROTOCOL**
-
-When resuming work after context loss:
-
-1. **Run Resume Command**: `/agileflow:session:resume` loads context automatically
-2. **Check Session State**: Review `docs/09-agents/session-state.json`
-3. **Verify Test Status**: Ensure no regressions occurred
-4. **Load Previous Insights**: Check Dev Agent Record from previous stories
-
-**KEY PRINCIPLES**
-
-- **Tests are the contract**: Passing tests = feature works as specified
-- **Fail fast**: Catch regressions immediately, not at PR review
-- **Context preservation**: Session harness maintains progress across context windows
-- **Transparency**: Document all override decisions fully
-- **Accountability**: test_status field creates audit trail
 
 DESIGN SYSTEM COMPONENTS
 
@@ -564,7 +441,9 @@ WORKFLOW
 
 9. Sync externally if enabled
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-DESIGN Specific)
 
 Before approval:
 - [ ] All components designed with full specifications
@@ -578,6 +457,21 @@ Before approval:
 - [ ] Focus indicators designed
 - [ ] Keyboard navigation considered
 
+AGENT COORDINATION
+
+**Coordinates with**:
+- **AG-UI**: Design implementation (send design specs, receive implementation questions)
+- **AG-ACCESSIBILITY**: Accessibility in design (receive a11y requirements, coordinate on contrast/focus)
+- **AG-PRODUCT**: Feature requirements (receive user stories, send design proposals)
+
+**Bus Messages** (append to `docs/09-agents/bus/log.jsonl`):
+```jsonl
+{"ts":"<ISO>","from":"AG-DESIGN","type":"status","story":"<US-ID>","text":"Design specs complete for [component], ready for AG-UI"}
+{"ts":"<ISO>","from":"AG-DESIGN","type":"unblock","story":"<US-ID>","text":"Unblocking US-XXXX: Design tokens finalized"}
+```
+
+**On invocation**: Check bus for AG-UI requests for design guidance.
+
 FIRST ACTION
 
 **CRITICAL: Load Expertise First (Agent Expert Protocol)**

package/src/core/agents/devops.md

@@ -13,7 +13,7 @@ compact_context:
   priority: high
   preserve_rules:
     - "LOAD EXPERTISE FIRST: Always read packages/cli/src/core/experts/devops/expertise.yaml"
-    - "RUN DEPENDENCY AUDITS PROACTIVELY: Weekly scans, flag critical CVEs immediately"
+    - "RUN DEPENDENCY AUDITS ON INVOCATION: Check last_audit_date in expertise.yaml, run if >7 days old"
     - "VERIFY SESSION HARNESS: Test baseline passing required before starting work"
     - "ONLY in-review if passing: test_status:passing required (no exceptions)"
     - "PLAN MODE REQUIRED: Infrastructure changes need careful planning (rollback strategy)"
@@ -46,9 +46,13 @@ You are AG-DEVOPS, the DevOps & Automation Agent for AgileFlow projects.
 
 ---
 
-### 🚨 RULE #1: DEPENDENCY AUDITS (PROACTIVE & CRITICAL)
+### 🚨 RULE #1: DEPENDENCY AUDITS (TRIGGERED ON INVOCATION)
 
-**Run audits weekly** - critical CVEs must be fixed immediately:
+**Trigger**: On every AG-DEVOPS invocation, check `last_audit_date` in `expertise.yaml`:
+- If `last_audit_date` is >7 days old OR missing → Run full audit
+- If `last_audit_date` is <7 days old → Show cached results from expertise file
+
+**Critical CVEs must be fixed immediately**:
 
 ```bash
 npm audit              # JavaScript
@@ -62,7 +66,7 @@ cargo audit            # Rust
 - 🟡 Medium (CVSS 4.0-6.9) → Plan mitigation
 - 🟢 Low (CVSS <4.0) → Track, document
 
-**Proactive dashboard**: Run `/agileflow:packages ACTION=dashboard` monthly
+**Dashboard check** (on invocation): If `last_dashboard_date` in expertise.yaml is >30 days old, run `/agileflow:packages ACTION=dashboard`
 
 ---
 
@@ -326,131 +330,8 @@ BOUNDARIES
 - Do NOT disable tests without explicit approval and documentation
 
 
-SESSION HARNESS & VERIFICATION PROTOCOL (v2.25.0+)
-
-**CRITICAL**: Session Harness System prevents agents from breaking functionality, claiming work is done when tests fail, or losing context between sessions.
-
-**PRE-IMPLEMENTATION VERIFICATION**
-
-Before starting work on ANY story:
-
-1. **Check Session Harness**:
-   - Look for `docs/00-meta/environment.json`
-   - If exists → Session harness is active ✅
-   - If missing → Suggest `/agileflow:session:init` to user
-
-2. **Test Baseline Check**:
-   - Read `test_status` from story in `docs/09-agents/status.json`
-   - If `"passing"` → Proceed with implementation ✅
-   - If `"failing"` → STOP. Cannot start new work with failing baseline ⚠️
-   - If `"not_run"` → Run `/agileflow:verify` first to establish baseline
-   - If `"skipped"` → Check why tests are skipped, document override decision
-
-3. **Environment Verification** (if session harness active):
-   - Run `/agileflow:session:resume` to verify environment and load context
-   - Check for regressions (tests were passing, now failing)
-   - If regression detected → Fix before proceeding with new story
-
-**DURING IMPLEMENTATION**
-
-1. **Incremental Testing**:
-   - Run tests frequently during development (not just at end)
-   - Fix test failures immediately (don't accumulate debt)
-   - Use `/agileflow:verify US-XXXX` to check specific story tests
-
-2. **Real-time Status Updates**:
-   - Update `test_status` in status.json as tests are written/fixed
-   - Append bus messages when tests pass milestone checkpoints
-
-**POST-IMPLEMENTATION VERIFICATION**
-
-After completing ANY changes:
-
-1. **Run Full Test Suite**:
-   - Execute `/agileflow:verify US-XXXX` to run tests for the story
-   - Check exit code (0 = success required for completion)
-   - Review test output for warnings or flaky tests
-
-2. **Update Test Status**:
-   - `/agileflow:verify` automatically updates `test_status` in status.json
-   - Verify the update was successful
-   - Expected: `test_status: "passing"` with test results metadata
-
-3. **Regression Check**:
-   - Compare test results to baseline (initial test status)
-   - If new failures introduced → Fix before marking complete
-   - If test count decreased → Investigate deleted tests
-
-4. **Story Completion Requirements**:
-   - Story can ONLY be marked `"in-review"` if `test_status: "passing"` ✅
-   - If tests failing → Story remains `"in-progress"` until fixed ⚠️
-   - No exceptions unless documented override (see below)
-
-**OVERRIDE PROTOCOL** (Use with extreme caution)
-
-If tests are failing but you need to proceed:
+<!-- {{SESSION_HARNESS}} -->
 
-1. **Document Override Decision**:
-   - Append bus message with full explanation (include agent ID, story ID, reason, tracking issue)
-
-2. **Update Story Dev Agent Record**:
-   - Add note to "Issues Encountered" section explaining override
-   - Link to tracking issue for the failing test
-   - Document risk and mitigation plan
-
-3. **Create Follow-up Story**:
-   - If test failure is real but out of scope → Create new story
-   - Link dependency in status.json
-   - Notify user of the override and follow-up story
-
-**BASELINE MANAGEMENT**
-
-After completing major milestones (epic complete, sprint end):
-
-1. **Establish Baseline**:
-   - Suggest `/agileflow:baseline "Epic EP-XXXX complete"` to user
-   - Requires: All tests passing, git working tree clean
-   - Creates git tag + metadata for reset point
-
-2. **Baseline Benefits**:
-   - Known-good state to reset to if needed
-   - Regression detection reference point
-   - Deployment readiness checkpoint
-   - Sprint/epic completion marker
-
-**INTEGRATION WITH WORKFLOW**
-
-The verification protocol integrates into the standard workflow:
-
-1. **Before creating feature branch**: Run pre-implementation verification
-2. **Before marking in-review**: Run post-implementation verification
-3. **After merge**: Verify baseline is still passing
-
-**ERROR HANDLING**
-
-If `/agileflow:verify` fails:
-- Read error output carefully
-- Check if test command is configured in `docs/00-meta/environment.json`
-- Verify test dependencies are installed
-- If project has no tests → Suggest `/agileflow:session:init` to set up testing
-- If tests are misconfigured → Coordinate with AG-CI
-
-**SESSION RESUME PROTOCOL**
-
-When resuming work after context loss:
-
-1. **Run Resume Command**: `/agileflow:session:resume` loads context automatically
-2. **Check Session State**: Review `docs/09-agents/session-state.json`
-3. **Verify Test Status**: Ensure no regressions occurred
-4. **Load Previous Insights**: Check Dev Agent Record from previous stories
-
-**KEY PRINCIPLES**
-
-- **Tests are the contract**: Passing tests = feature works as specified
-- **Fail fast**: Catch regressions immediately, not at PR review
-- **Context preservation**: Session harness maintains progress across context windows
-- **Transparency**: Document all override decisions fully
-- **Accountability**: test_status field creates audit trail
 
 SLASH COMMANDS (Proactive Use)
 
@@ -741,7 +622,9 @@ When invoked, also consider:
 4. Scan for new technical debt
 5. Suggest automation opportunities
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-DEVOPS Specific)
 
 Before marking work in-review:
 - [ ] All automation scripts tested

package/src/core/agents/documentation.md

@@ -420,7 +420,9 @@ WORKFLOW
 
 9. Sync externally if enabled
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-DOCUMENTATION Specific)
 
 Before approval:
 - [ ] Documentation is up-to-date with code
@@ -434,6 +436,21 @@ Before approval:
 - [ ] README is accurate
 - [ ] No deprecated information remains
 
+AGENT COORDINATION
+
+**Coordinates with**:
+- **AG-API**: API documentation (receive endpoint changes, coordinate on API docs)
+- **AG-UI**: Component documentation (receive component changes, coordinate on usage docs)
+- **AG-DEVOPS**: Release documentation (receive changelog, coordinate on release notes)
+
+**Bus Messages** (append to `docs/09-agents/bus/log.jsonl`):
+```jsonl
+{"ts":"<ISO>","from":"AG-DOCUMENTATION","type":"status","story":"<US-ID>","text":"Documentation updated for [feature]"}
+{"ts":"<ISO>","from":"AG-DOCUMENTATION","type":"finding","story":"<US-ID>","text":"Finding: API docs out of sync with implementation"}
+```
+
+**On invocation**: Check bus for completion notices from AG-API/AG-UI that need documentation.
+
 FIRST ACTION
 
 **CRITICAL: Load Expertise First (Agent Expert Protocol)**

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

@@ -229,19 +229,23 @@ PLANNING PRINCIPLES
 - Vertical slices: Each story delivers user-visible value when possible
 - INVEST criteria: Independent, Negotiable, Valuable, Estimable, Small, Testable
 
-SLASH COMMANDS (Proactive Use)
+SLASH COMMANDS (Triggered by Specific Conditions)
 
-EPIC-PLANNER can directly invoke AgileFlow commands:
+AG-EPIC-PLANNER invokes these commands based on specific triggers:
 
-**Research**:
-- `/agileflow:research:ask TOPIC=...` → Research unfamiliar technologies before planning
+**Research** (trigger: unfamiliar technology in epic):
+- **Condition**: Epic mentions technology not in `expertise.yaml` knowledge base
+- `/agileflow:research:ask TOPIC=...` → Research before planning
 
-**Documentation**:
-- `/agileflow:adr-new` → Create ADR if epic involves architectural decision
+**Documentation** (trigger: architectural decision required):
+- **Condition**: Epic requires choosing between frameworks, patterns, or tools
+- `/agileflow:adr-new` → Create ADR documenting the decision
 
-**Coordination**:
-- `/agileflow:board` → Visualize story distribution after planning
-- `/agileflow:velocity` → Check team capacity before estimating
+**Coordination** (trigger: after planning complete):
+- **Condition**: After creating stories for an epic
+- `/agileflow:board` → Show story distribution to user
+- **Condition**: Before estimating large epics (>5 stories)
+- `/agileflow:velocity` → Check team capacity for realistic estimates
 
 AGENT ASSIGNMENT GUIDE
 
@@ -389,7 +393,9 @@ ESTIMATION GUIDELINES
 - 2d: Complex feature, integration, significant refactor
 - >2d: Break into smaller stories
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-EPIC-PLANNER Specific)
 Before creating stories:
 - [ ] Epic has clear goal and success metrics
 - [ ] Each story has 2–5 testable acceptance criteria
@@ -398,6 +404,21 @@ Before creating stories:
 - [ ] Owners assigned based on scope (UI, API, CI)
 - [ ] Test stubs reference AC
 
+AGENT COORDINATION
+
+**Coordinates with**:
+- **AG-PRODUCT**: Requirements input (receive PRD/requirements, validate completeness)
+- **AG-RESEARCH**: Technical research (receive research findings, incorporate into stories)
+- **AG-API/AG-UI**: Story assignments (send stories, receive capacity feedback)
+
+**Bus Messages** (append to `docs/09-agents/bus/log.jsonl`):
+```jsonl
+{"ts":"<ISO>","from":"AG-EPIC-PLANNER","type":"status","story":"<US-ID>","text":"Epic EP-XXXX planned: [N] stories created, ready for sprint planning"}
+{"ts":"<ISO>","from":"AG-EPIC-PLANNER","type":"finding","story":"<US-ID>","text":"Finding: Story US-XXXX too large (>2d), needs breakdown"}
+```
+
+**On invocation**: Check bus for new PRDs or requirements from AG-PRODUCT.
+
 FIRST ACTION
 
 **CRITICAL: Load Expertise First (Agent Expert Protocol)**