agileflow 2.92.0 → 2.93.0

package/src/core/agents/security.md

@@ -120,7 +120,12 @@ grep -r "BEGIN PRIVATE KEY\|-----BEGIN" --include="*.txt" --include="*.env"
 
 ### 🚨 RULE #5: COORDINATION WITH ALL AGENTS
 
-**Security affects everything** - coordinate proactively:
+**Security affects everything** - coordinate with agents when their work touches security:
+
+**Coordination Triggers**:
+- **On story assignment**: Check if story involves auth, data handling, or external input
+- **After finding vulnerability**: Send bus message to affected agent(s)
+- **After completing security fix**: Send unblock message if other agents were waiting
 
 | Agent | Coordination |
 |-------|--------------|
@@ -237,131 +242,8 @@ BOUNDARIES
 - Always err on side of caution with security decisions
 
 
-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:
-
-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**
+<!-- {{SESSION_HARNESS}} -->
 
-- **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
 
 SECURITY CHECKLIST (Pre-Release MANDATORY)
 

package/src/core/agents/testing.md

@@ -249,131 +249,8 @@ BOUNDARIES
 - Always focus on behavior, not implementation
 
 
-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
 
 TEST CATEGORIES
 
@@ -564,7 +441,9 @@ WORKFLOW
 
 11. Sync externally if enabled
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-TESTING Specific)
 
 Before approval:
 - [ ] Test coverage ≥70% (critical paths 100%)
@@ -578,6 +457,22 @@ Before approval:
 - [ ] Test fixtures reusable and well-documented
 - [ ] Coverage report generated and reviewed
 
+AGENT COORDINATION
+
+**Coordinates with**:
+- **AG-CI**: Test infrastructure (send test requirements, receive CI pipeline status)
+- **AG-QA**: Test strategy (send coverage metrics, receive test plan requirements)
+- **AG-API/AG-UI**: Implementation testing (receive feature completions, send test results)
+
+**Bus Messages** (append to `docs/09-agents/bus/log.jsonl`):
+```jsonl
+{"ts":"<ISO>","from":"AG-TESTING","type":"status","story":"<US-ID>","text":"Tests complete: [X] passed, [Y] failed, [Z]% coverage"}
+{"ts":"<ISO>","from":"AG-TESTING","type":"finding","story":"<US-ID>","text":"Finding: Coverage gap in [module] - [critical path] not tested"}
+{"ts":"<ISO>","from":"AG-TESTING","type":"blocked","story":"<US-ID>","text":"Blocked: Test database not configured"}
+```
+
+**On invocation**: Check bus for feature completions that need test coverage.
+
 FIRST ACTION
 
 **CRITICAL: Load Expertise First (Agent Expert Protocol)**

package/src/core/agents/ui.md

@@ -278,134 +278,8 @@ BOUNDARIES
 - Do NOT commit credentials, tokens, or secrets
 - Do NOT reassign stories without explicit request
 
-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:
-   ```jsonl
-   {"ts":"2025-12-06T14:00:00Z","from":"AG-UI","type":"warning","story":"US-0043","text":"Override: Marking in-review with 1 failing test. Reason: Test is flaky and unrelated to this story. Tracked in US-0099."}
-   ```
-
-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 Step 7** (Create feature branch): Run pre-implementation verification
-2. **Before Step 13** (Update to in-review): Run post-implementation verification
-3. **After Step 17** (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 INITIALIZATION (Proactive - run before first UI story)
 
@@ -605,11 +479,11 @@ module.exports = {
    - Replace hardcoded values with design tokens
    - Test each component still renders correctly
 
-**When to Run This**:
-- ✅ First time implementing a UI story (proactive check)
-- ✅ When user explicitly requests design system
-- ✅ When you notice inconsistent styling across components
-- ✅ Before implementing theming/dark mode features
+**Trigger Conditions** (specific events that trigger design system check):
+- ✅ **First UI story of session**: Check expertise.yaml `last_design_system_check` - if missing or >7 days, run check
+- ✅ **User explicitly requests**: "design system", "design tokens", "styling setup"
+- ✅ **Inconsistent styling detected**: While implementing, find hardcoded colors/spacing not in tokens
+- ✅ **Theming story assigned**: Story title/AC mentions "dark mode", "theme", "branding"
 
 **Benefits to Communicate**:
 - ✅ Consistency: All components use same colors, spacing, fonts
@@ -619,7 +493,7 @@ module.exports = {
 - ✅ Developer Experience: Autocomplete for design tokens
 - ✅ Scalability: New components automatically match existing design
 
-CLAUDE.MD MAINTENANCE (Proactive - Update with UI patterns)
+CLAUDE.MD MAINTENANCE (Triggered After UI Pattern Changes)
 
 **CRITICAL**: CLAUDE.md is the AI assistant's system prompt - it should reflect current styling practices and design patterns.
 
@@ -718,7 +592,10 @@ README.MD MAINTENANCE (Proactive - CRITICAL PRIORITY for UI work)
 - Created icon library → Document icon component usage and available icons
 - Added responsive navigation → Update component catalog and mobile-specific notes
 
-**IMPORTANT**: Do NOT wait for user to ask - proactively suggest README updates after significant UI work, especially after design system changes or new component patterns.
+**README Update Trigger**:
+- **Condition**: After completing work that adds/changes design system, components, or UI patterns
+- **Detection**: Files modified in `components/`, `styles/`, or design token files
+- **Action**: Suggest README update with specific changes: "I noticed I modified [files]. Should I update the README to document [specific changes]?"
 
 SLASH COMMANDS (Proactive Use)
 
@@ -1074,7 +951,9 @@ UX LAWS & DESIGN FUNDAMENTALS
 - ✅ Case-insensitive email validation
 - Pattern: Auto-format as user types
 
-QUALITY CHECKLIST
+<!-- {{QUALITY_GATE_PRIORITIES}} -->
+
+QUALITY CHECKLIST (AG-UI Specific)
 Before marking in-review, verify:
 
 **Functionality**:

package/src/core/commands/adr/list.md

@@ -1,6 +1,18 @@
 ---
 description: List all Architecture Decision Records
 argument-hint: [STATUS=<status>]
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:adr:list - Lists all ADRs with status and quick actions"
+    - "MUST read docs/03-decisions/ directory for ADR files"
+    - "MUST parse frontmatter for status, date, tags"
+    - "MUST display table sorted by number with status indicators"
+    - "MUST offer actions: view details, create new, update status"
+    - "This is READ-ONLY - no file writes"
+  state_fields:
+    - status_filter
+    - adr_count
 ---
 
 # /agileflow:adr:list
@@ -21,6 +33,14 @@ Shows all ADRs from `docs/03-decisions/` with:
 
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node .agileflow/scripts/obtain-context.js adr:list
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 ## Compact Summary
 

package/src/core/commands/adr/update.md

@@ -1,6 +1,21 @@
 ---
 description: Update ADR status or content
-argument-hint: NUMBER=<4-digit> [STATUS=<status>] [REASON=<text>]
+argument-hint: NUMBER=<number> [STATUS=<status>] [REASON=<text>]
+compact_context:
+  priority: high
+  preserve_rules:
+    - "NUMBER is REQUIRED - always ask if missing"
+    - "Every status change MUST have documented reason"
+    - "Show preview of changes before writing (diff-first pattern)"
+    - "If superseded, MUST link to replacement ADR"
+    - "Never delete content - always append amendments"
+    - "Update timestamps in frontmatter when modifying"
+  state_fields:
+    - adr_number
+    - current_status
+    - new_status
+    - reason
+    - superseded_by
 ---
 
 # /agileflow:adr:update
@@ -19,6 +34,14 @@ Allows you to:
 
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node .agileflow/scripts/obtain-context.js adr:update
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 ## Compact Summary
 

package/src/core/commands/adr/view.md

@@ -1,6 +1,20 @@
 ---
 description: View ADR details with contextual actions
-argument-hint: NUMBER=<4-digit>
+argument-hint: NUMBER=<number>
+compact_context:
+  priority: medium
+  preserve_rules:
+    - "ACTIVE COMMAND: /agileflow:adr:view - Views ADR with context-aware actions"
+    - "MUST read ADR file from docs/03-decisions/adr-NUMBER-*.md"
+    - "MUST display full ADR content: context, decision, consequences, links"
+    - "MUST offer CONTEXT-AWARE actions based on ADR status"
+    - "STATUS=proposed → Accept, reject, request changes"
+    - "STATUS=accepted → Create stories, supersede, deprecate"
+    - "STATUS=deprecated/superseded → View history, replacement"
+    - "ALWAYS offer next steps via AskUserQuestion"
+  state_fields:
+    - selected_adr_number
+    - adr_status
 ---
 
 # /agileflow:adr:view
@@ -19,6 +33,14 @@ Displays complete ADR information and offers **context-aware actions** based on
 
 ---
 
+## STEP 0: Gather Context
+
+```bash
+node .agileflow/scripts/obtain-context.js adr:view
+```
+
+---
+
 <!-- COMPACT_SUMMARY_START -->
 ## Compact Summary
 

package/src/core/commands/adr.md

@@ -1,13 +1,13 @@
 ---
 description: Create an Architecture Decision Record
-argument-hint: NUMBER=<4-digit> TITLE=<text> CONTEXT=<text> DECISION=<text> CONSEQUENCES=<text> [LINKS=<text>]
+argument-hint: NUMBER=<number> TITLE=<text> CONTEXT=<text> DECISION=<text> CONSEQUENCES=<text> [LINKS=<text>]
 compact_context:
   priority: medium
   preserve_rules:
     - "NUMBER is REQUIRED - must be 4-digit sequentially (0001, 0002, etc.)"
     - "TITLE, CONTEXT, DECISION, CONSEQUENCES all REQUIRED"
     - "Create ADR file in docs/03-decisions/adr-<NUMBER>-<slug>.md"
-    - "Always show preview FIRST, wait for YES/NO confirmation BEFORE writing"
+    - "{{RULES:file_preview}}"
     - "Document BOTH positive and negative consequences"
     - "Keep ADRs concise: 1-2 pages max"
     - "Link related ADRs and stories in Related section"

package/src/core/commands/agent.md

@@ -1,6 +1,6 @@
 ---
 description: Onboard a new agent with profile and contract
-argument-hint: AGENT_ID=<id> ROLE=<role> [TOOLS=<list>] [SCOPE=<dirs>]
+argument-hint: AGENT_ID=<id> ROLE=<text> [TOOLS=<list>] [SCOPE=<list>]
 compact_context:
   priority: high
   preserve_rules:
@@ -225,6 +225,16 @@ Options:
 [AskUserQuestion: "How to proceed?"]
 ```
 
+---
+
+## Related Commands
+
+- `/agileflow:configure` - Manage AgileFlow features and hooks
+- `/agileflow:story` - Create user stories for agents
+- `/agileflow:status` - Update story status and progress
+- `/agileflow:babysit` - Interactive mentor workflow
+- `/agileflow:help` - Display AgileFlow overview
+
 ### Roster File Created
 
 ```

package/src/core/commands/assign.md

@@ -6,12 +6,11 @@ compact_context:
   preserve_rules:
     - "ACTIVE COMMAND: /agileflow:assign - Story assigner and owner changer"
     - "MUST update story frontmatter (owner, status, updated timestamp)"
-    - "MUST update docs/09-agents/status.json using jq or Edit tool"
-    - "MUST validate JSON after modification"
-    - "MUST append assign event to docs/09-agents/bus/log.jsonl"
-    - "MUST use AskUserQuestion for user confirmation (YES/NO format)"
-    - "MUST show diff preview before confirming (diff-first pattern)"
-    - "Status values: ready|in-progress|blocked|in-review|done"
+    - "{{RULES:json_operations}}"
+    - "{{RULES:bus_messaging}}"
+    - "{{RULES:user_confirmation}}"
+    - "{{RULES:file_preview}}"
+    - "{{RULES:status_updates}}"
   state_fields:
     - story_id
     - current_owner
@@ -357,3 +356,13 @@ Files to update:
    New owner: AG-UI
    Notification sent to both agents
 ```
+
+---
+
+## Related Commands
+
+- `/agileflow:status` - Update story status
+- `/agileflow:handoff` - Document work handoff
+- `/agileflow:sprint` - Sprint planning
+- `/agileflow:board` - Kanban board view
+- `/agileflow:story:view` - View story details