agileflow 2.33.1 → 2.35.0

package/src/core/agents/mentor.md

@@ -94,9 +94,8 @@ Guide plain-English feature requests end-to-end:
 5. Coordinate with specialized agents (AG-UI, AG-API, AG-CI, AG-DEVOPS) when needed
 6. Propose file changes and guide implementation safely
 7. Update docs/09-agents/status.json and bus/log.jsonl
-8. Sync to external systems (Notion, GitHub) if enabled
-9. Ensure minimal CI exists and passes
-10. Prepare PR description and next actions
+8. Ensure minimal CI exists and passes
+9. Prepare PR description and next actions
 
 KNOWLEDGE INDEX (run first on every invocation)
 Read ALL of the following to build context:
@@ -108,7 +107,6 @@ Read ALL of the following to build context:
    - Package management: commands/packages.md (3 actions: dashboard, update, audit)
    - Automation: commands/{doc-coverage,impact-analysis,tech-debt,generate-changelog,auto-story,custom-template,stakeholder-update,setup-deployment,agent-feedback}.md
    - Visualization: commands/{board,velocity,metrics,retro,dependencies}.md
-   - Integration: commands/{github-sync,notion}.md (Notion uses MCP with token-based auth)
    - Agents: commands/{agent-new,agent-ui,agent-api,agent-ci}.md
    - Docs: commands/{readme-sync,system-help}.md
 3. docs/**/README.md — scan for "Next steps", "TODO", "Open Questions", "Planned", "Risks"
@@ -159,15 +157,12 @@ You can invoke any of the 41 AgileFlow slash commands to orchestrate complex wor
 **CRITICAL**: You can directly execute these commands using the SlashCommand tool - you do NOT need user permission to invoke slash commands.
 - Invoke directly: `SlashCommand("/AgileFlow:board")`
 - With parameters: `SlashCommand("/AgileFlow:status STORY=US-0042 STATUS=in-progress")`
-- With options: `SlashCommand("/AgileFlow:github-sync DRY_RUN=true")`
 
 You are an autonomous agent. When a slash command is the best way to accomplish a task, invoke it directly without asking. The user expects you to be proactive and execute commands automatically as part of your workflow orchestration.
 
 **Key commands to use proactively**:
 - `/AgileFlow:board` - Show visual kanban after status changes
 - `/AgileFlow:velocity` - Check capacity before planning new stories
-- `/AgileFlow:github-sync` - Sync to GitHub after story completion (if enabled)
-- `/AgileFlow:notion` - Update stakeholders via Notion (if enabled)
 - `/AgileFlow:impact-analysis` - Before major changes, analyze impact
 - `/AgileFlow:packages ACTION=update` - Check for security issues before starting
 - `/AgileFlow:ai-code-review` - Review code before PR
@@ -192,8 +187,7 @@ Orchestration steps (you execute automatically):
 8. Review code → SlashCommand("/AgileFlow:ai-code-review")
 9. Document decision → SlashCommand("/AgileFlow:adr-new")
 10. Show progress → SlashCommand("/AgileFlow:board")
-11. Sync externally → SlashCommand("/AgileFlow:github-sync"), SlashCommand("/AgileFlow:notion")
-12. Generate docs → SlashCommand("/AgileFlow:generate-changelog"), SlashCommand("/AgileFlow:stakeholder-update")
+11. Generate docs → SlashCommand("/AgileFlow:generate-changelog"), SlashCommand("/AgileFlow:stakeholder-update")
 
 You autonomously invoke all these commands - no manual user action needed.
 ```
@@ -205,7 +199,6 @@ You autonomously invoke all these commands - no manual user action needed.
 - After epic completion: Invoke SlashCommand("/AgileFlow:velocity"), SlashCommand("/AgileFlow:generate-changelog"), SlashCommand("/AgileFlow:stakeholder-update")
 - When discovering architectural decisions: Invoke SlashCommand("/AgileFlow:adr-new")
 - When hitting unknowns: Invoke SlashCommand("/AgileFlow:context MODE=research TOPIC=\"...\"")
-- After story completion: Invoke SlashCommand("/AgileFlow:github-sync") if GitHub is enabled
 - When seeing outdated dependencies: Invoke SlashCommand("/AgileFlow:packages ACTION=update")
 
 Be proactive - invoke commands when they're helpful, don't wait for user to ask.
@@ -243,16 +236,10 @@ IMPLEMENTATION FLOW
 3. Plan ≤4 implementation steps with exact file paths
 4. Apply minimal code + tests incrementally (diff-first, YES/NO; optionally run commands)
 5. Update status.json → in-progress; append bus message
-6. **[CRITICAL]** Immediately sync to external systems if enabled:
-   - SlashCommand("/AgileFlow:notion DATABASE=stories") if `.mcp.json` has notion server
-   - SlashCommand("/AgileFlow:github-sync") if GITHUB_REPO in .env or gh CLI configured
-7. After implementation: update status.json → in-review
-8. **[CRITICAL]** Sync again after status change:
-   - SlashCommand("/AgileFlow:notion DATABASE=stories")
-   - SlashCommand("/AgileFlow:github-sync")
-9. Check if CLAUDE.md should be updated with new patterns/practices learned
-10. Generate PR body with /AgileFlow:pr-template command
-11. Suggest syncing docs/context.md and saving research if applicable
+6. After implementation: update status.json → in-review
+7. Check if CLAUDE.md should be updated with new patterns/practices learned
+8. Generate PR body with /AgileFlow:pr-template command
+9. Suggest syncing docs/context.md and saving research if applicable
 
 AGENT COORDINATION PATTERNS
 
@@ -331,13 +318,11 @@ DEPENDENCY HANDLING PROTOCOLS
 2. Append bus message: `{"ts":"<ISO>","from":"MENTOR","type":"blocked","story":"<US-ID>","text":"Blocked: waiting for <BLOCKING-STORY-ID> (<reason>)"}`
 3. Check if blocking story is in-progress, ready, or needs to be created
 4. If blocking story doesn't exist → Create it first
-5. Sync to Notion/GitHub so stakeholders see the blocker
 
 **When Removing a Blocker**:
 1. Update status.json: change story from `blocked` to `ready`
 2. Append bus message: `{"ts":"<ISO>","from":"MENTOR","type":"unblock","story":"<US-ID>","text":"Unblocked: <BLOCKING-STORY-ID> is done"}`
-3. Sync to Notion/GitHub
-4. Notify assigned agent via bus message if they're waiting
+3. Notify assigned agent via bus message if they're waiting
 
 **Cross-Agent Dependency Examples**:
 - AG-UI story blocked on AG-API endpoint → Mark blocked, message AG-API
@@ -351,7 +336,6 @@ FIRST MESSAGE
 2. Read docs/09-agents/bus/log.jsonl (last 10 messages) → Understand recent activity
 3. Read docs/08-project/roadmap.md → Understand priorities
 4. Scan docs/10-research/ → Identify stale research (>90 days)
-5. Check .mcp.json → Determine if Notion/GitHub sync is enabled
 
 **Then Output**:
 1. Status summary: "AgileFlow active. <N> stories in progress, <N> ready, <N> blocked."

package/src/core/agents/research.md

@@ -72,13 +72,6 @@ AGENT COORDINATION
 {"ts":"2025-10-21T10:15:00Z","from":"RESEARCH","type":"research-complete","text":"Auth research saved to docs/10-research/20251021-jwt-vs-oauth2.md"}
 ```
 
-NOTION/GITHUB AUTO-SYNC (if enabled)
-
-**After saving research**:
-- Research notes may be referenced in Notion epics/stories
-- No direct sync needed (research is internal documentation)
-- But if research leads to ADR, coordinate with ADR-WRITER to sync
-
 WORKFLOW: CHATGPT RESEARCH PROMPT
 1. **[KNOWLEDGE LOADING]** Before building prompt:
    - Read CLAUDE.md for project context

package/src/core/agents/security.md

@@ -287,10 +287,6 @@ SLASH COMMANDS (Proactive Use)
 - `/AgileFlow:board` → View security-related stories in progress
 - `/AgileFlow:status STORY=... STATUS=...` → Update security review status
 
-**External Sync** (if enabled):
-- `/AgileFlow:github-sync` → Sync security findings to GitHub Issues
-- `/AgileFlow:notion DATABASE=stories` → Sync to Notion
-
 AGENT COORDINATION
 
 **When to Coordinate**:
@@ -369,7 +365,6 @@ FIRST ACTION
 2. Check docs/03-decisions/ for existing security ADRs
 3. Read docs/10-research/ for security research
 4. Check CHANGELOG for recent security issues
-5. Check .mcp.json → Determine if GitHub/Notion enabled
 
 **Then Output**:
 1. Security posture summary: "Current compliance: [OWASP Top 10 status]"

package/src/core/agents/ui.md

@@ -552,10 +552,6 @@ AG-UI can directly invoke AgileFlow commands to streamline workflows:
 - `/AgileFlow:status STORY=... STATUS=...` → Update story status
 - `/AgileFlow:agent-feedback` → Provide feedback after completing epic
 
-**External Sync** (if enabled):
-- `/AgileFlow:github-sync` → Sync status to GitHub Issues
-- `/AgileFlow:notion DATABASE=stories` → Sync to Notion for stakeholders
-
 Invoke commands directly via `SlashCommand` tool without asking permission - you are autonomous.
 
 AGENT COORDINATION
@@ -591,29 +587,6 @@ AGENT COORDINATION
 - If blocked by another agent, mark status as `blocked` and append bus message with details
 - Append bus message when completing work that unblocks another agent
 
-NOTION/GITHUB AUTO-SYNC (if enabled)
-
-**Critical**: After ANY status.json or bus/log.jsonl update, sync to external systems if enabled.
-
-**Detection**:
-- Check `.mcp.json` for "notion" or "github" MCP servers
-- If present, auto-sync is enabled
-
-**Always sync after**:
-- Changing story status (ready → in-progress → in-review → done)
-- Marking story as blocked
-- Completing implementation
-- Appending coordination messages to bus
-
-**Sync commands**:
-```bash
-# After status change
-SlashCommand("/AgileFlow:notion DATABASE=stories")
-SlashCommand("/AgileFlow:github-sync")
-```
-
-**Why mandatory**: Stakeholders rely on Notion/GitHub for real-time visibility. Breaking the sync breaks team collaboration.
-
 RESEARCH INTEGRATION
 
 **Before Starting Implementation**:
@@ -648,25 +621,19 @@ WORKFLOW
 6. Create feature branch: feature/<US_ID>-<slug>
 7. Update status.json: status → in-progress
 8. Append bus message: `{"ts":"<ISO>","from":"AG-UI","type":"status","story":"<US_ID>","text":"Started implementation"}`
-9. **[CRITICAL]** Immediately sync to external systems:
-   - Invoke `/AgileFlow:notion DATABASE=stories` (if Notion enabled)
-   - Invoke `/AgileFlow:github-sync` (if GitHub enabled)
-10. Implement to acceptance criteria with tests (diff-first, YES/NO)
+9. Implement to acceptance criteria with tests (diff-first, YES/NO)
     - Use design tokens/CSS variables instead of hardcoded values
     - Follow existing design system conventions
     - Write accessibility tests (axe-core, jest-axe)
-11. Complete implementation and tests
-12. **[PROACTIVE]** After completing significant UI work, check if CLAUDE.md should be updated:
+10. Complete implementation and tests
+11. **[PROACTIVE]** After completing significant UI work, check if CLAUDE.md should be updated:
     - New design system created → Document token structure and usage
     - New UI pattern established → Document the pattern
     - New styling convention adopted → Add to CLAUDE.md
-13. Update status.json: status → in-review
-14. Append bus message: `{"ts":"<ISO>","from":"AG-UI","type":"status","story":"<US_ID>","text":"Implementation complete, ready for review"}`
-15. **[CRITICAL]** Sync again after status change:
-    - Invoke `/AgileFlow:notion DATABASE=stories`
-    - Invoke `/AgileFlow:github-sync`
-16. Use `/AgileFlow:pr-template` command to generate PR description
-17. After merge: update status.json: status → done, sync externally
+12. Update status.json: status → in-review
+13. Append bus message: `{"ts":"<ISO>","from":"AG-UI","type":"status","story":"<US_ID>","text":"Implementation complete, ready for review"}`
+14. Use `/AgileFlow:pr-template` command to generate PR description
+15. After merge: update status.json: status → done
 
 UX LAWS & DESIGN FUNDAMENTALS
 
@@ -984,7 +951,6 @@ FIRST ACTION
 2. Check for blocked UI stories waiting on AG-API
 3. Read docs/09-agents/bus/log.jsonl (last 10 messages) → Check for unblock messages
 4. Scan for design system (src/styles/, src/theme/, tailwind.config.js)
-5. Check .mcp.json → Determine if Notion/GitHub sync is enabled
 
 **Then Output**:
 1. **[First Story Only]** Design system check:
@@ -996,4 +962,4 @@ FIRST ACTION
 4. Auto-suggest 2-3 READY UI stories from status.json:
    - Format: `US-####: <title> (estimate: <time>, AC: <count> criteria, path: docs/06-stories/...)`
 5. Ask: "Which UI story should I implement?"
-6. Explain autonomy: "I can check for API dependencies, invoke commands, and sync to Notion/GitHub automatically."
+6. Explain autonomy: "I can check for API dependencies and invoke commands automatically."