agileflow 3.4.2 → 4.0.0-alpha.1

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

@@ -1,59 +0,0 @@
----
-description: List available team templates
-argument-hint: "(no arguments)"
-compact_context:
-  priority: low
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:team:list - List team templates"
-  state_fields: []
----
-
-# /agileflow:team:list
-
-List all available team composition templates.
-
----
-
-## Step 1: Find Templates
-
-Read all `.json` files from the teams directory:
-
-```bash
-node -e "
-const fs = require('fs');
-const path = require('path');
-const teamsDir = path.join(process.cwd(), '.agileflow', 'teams');
-if (!fs.existsSync(teamsDir)) {
-  console.log('No teams directory found. Run: npx agileflow update');
-  process.exit(0);
-}
-const files = fs.readdirSync(teamsDir).filter(f => f.endsWith('.json'));
-for (const file of files) {
-  const template = JSON.parse(fs.readFileSync(path.join(teamsDir, file), 'utf8'));
-  console.log(JSON.stringify({ name: template.name, description: template.description, teammates: template.teammates.length, tags: template.tags }));
-}
-"
-```
-
-## Step 2: Display as Table
-
-Format and display all templates:
-
-| Template | Description | Team Size | Tags |
-|----------|-------------|-----------|------|
-| `fullstack` | Full-stack development team | 3 | development, feature |
-| `code-review` | Code review specialists | 3 | review, quality |
-| `builder-validator` | Paired builder+validator | 4 | validation, high-confidence |
-| `logic-audit` | Multi-perspective logic analysis | 4 | analysis, bugs |
-
-## Step 3: Show Agent Teams Status
-
-Also display:
-- Whether Agent Teams is enabled (native mode vs subagent fallback)
-- How to enable if not enabled
-- Link to `/agileflow:team:start <template>` for starting a team
-
-## Step 4: Show Active Team (if any)
-
-If a team is currently active, show its status at the top:
-- "Active team: fullstack (started 2h ago, 3 teammates)"

package/src/core/commands/team/start.md

@@ -1,130 +0,0 @@
----
-description: Start a team from a template
-argument-hint: "<template-name>"
-compact_context:
-  priority: high
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:team:start - Start a native Agent Teams session"
-    - "Requires CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS env var or metadata flag"
-    - "Falls back to orchestrator subagent when Agent Teams not enabled"
-    - "Templates loaded from .agileflow/teams/ directory"
-  state_fields:
-    - template_name
-    - team_mode
-    - teammates_spawned
----
-
-# /agileflow:team:start
-
-Start a team of specialized agents from a predefined template.
-
----
-
-## Prerequisites
-
-Check if Agent Teams is enabled:
-
-```bash
-node -e "const ff = require('./.agileflow/lib/feature-flags'); console.log(JSON.stringify(ff.getFeatureFlags()))"
-```
-
-If not available, try:
-```bash
-node -e "console.log(JSON.stringify({ agentTeams: !!process.env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS }))"
-```
-
-## Step 1: Detect Mode
-
-1. Check if native Agent Teams is enabled using the feature-flags module
-2. If enabled → proceed with native team creation
-3. If NOT enabled → fall back to orchestrator subagent with warning
-
-## Step 2: Load Template
-
-The argument specifies which team template to use. Available templates are in `.agileflow/teams/`:
-
-| Template | Description | Best For |
-|----------|-------------|----------|
-| `fullstack` | API + UI + Testing specialists | Full-stack feature development |
-| `backend` | API + Database + Security specialists | Backend/API work |
-| `frontend` | UI + Accessibility + Testing specialists | Frontend/component work |
-| `solo` | Mentor + Testing (lightweight) | Solo developers, learning |
-| `qa` | QA Strategy + Testing + Browser QA | Test coverage, regression |
-| `code-review` | Code reviewer + Security + Performance | Pre-PR quality gates |
-| `builder-validator` | Paired builders with validators | High-reliability features |
-| `logic-audit` | Multi-perspective logic analysis | Complex business logic |
-
-If no argument given, use AskUserQuestion to let user choose.
-
-## Step 3: Start Team
-
-### Native Mode (Agent Teams enabled)
-
-When Agent Teams is enabled, use native tools to create and coordinate the team:
-
-1. **Run the team-manager script** to load the template and build the native payload:
-   ```bash
-   node .agileflow/scripts/team-manager.js start <template-name>
-   ```
-   Parse the JSON output. The `native_payload` field contains the team configuration.
-
-2. **Announce the team composition** to the user — list each teammate's name, role, and domain.
-
-3. **Spawn teammates using the Task tool with native parameters**:
-   For each teammate in `native_payload.teammates`:
-   ```
-   Task tool call:
-     subagent_type: <teammate.name>     (e.g. "agileflow-api")
-     description: "<role> - <domain>"
-     prompt: <built from teammate instructions + project context>
-   ```
-   The prompt for each teammate should include:
-   - Their role and domain from the template
-   - The specific task or story they should work on
-   - A pointer to read CLAUDE.md and check `docs/09-agents/status.json` for context
-   - Quality gate requirements from the template
-
-4. **If native tools fail** (e.g., TeamCreate not available, tool not found errors):
-   - Log a warning: "Native Agent Teams tools not available. Falling back to subagent mode."
-   - Proceed with the **Fallback Mode** instructions below instead
-   - Update `session-state.json` to reflect `mode: "subagent"`
-
-5. **Create shared tasks** using TaskCreate for the work to be done:
-   - One task per teammate with clear acceptance criteria
-   - Set up dependencies (e.g., UI tasks blocked by API tasks)
-
-6. **Report** which mode was actually used (native vs fallback) and the spawned teammates.
-
-> **Tip**: For teams with 3+ teammates, consider using tmux sessions (`/agileflow:session:spawn`) to run teammates in parallel windows for better visibility.
-
-### Fallback Mode (Agent Teams disabled)
-
-When Agent Teams is NOT enabled:
-
-1. Show warning: "Agent Teams is not enabled. Using orchestrator subagent mode."
-2. Show how to enable: "Set CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1 to use native teams"
-3. Use the `Task` tool with `subagent_type` matching each teammate's agent name
-4. Coordinate results manually
-
-## Step 4: Report
-
-Show team status:
-- Which teammates were spawned
-- What tasks were assigned
-- Current quality gate configuration
-
----
-
-## Examples
-
-```
-/agileflow:team:start fullstack
-/agileflow:team:start code-review
-/agileflow:team:start builder-validator
-```
-
-## Quality Gates
-
-Teams respect quality gates from the template's `quality_gates` configuration:
-- **teammate_idle**: Gates checked before a teammate goes idle (tests, lint, types)
-- **task_completed**: Gates checked when a task is marked done (validator approval)

package/src/core/commands/team/status.md

@@ -1,66 +0,0 @@
----
-description: Show team member statuses and tasks
-argument-hint: "(no arguments)"
-compact_context:
-  priority: medium
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:team:status - Display team status"
-    - "Shows per-teammate progress, task assignments, and quality gate results"
-  state_fields:
-    - team_active
-    - teammate_statuses
----
-
-# /agileflow:team:status
-
-Display the current status of an active team session.
-
----
-
-## Step 1: Check for Active Team
-
-```bash
-node -e "
-const fs = require('fs');
-const p = require('./.agileflow/lib/paths');
-const state = JSON.parse(fs.readFileSync(p.getSessionStatePath(), 'utf8'));
-console.log(JSON.stringify(state.active_team || null, null, 2));
-"
-```
-
-If no active team, inform user: "No active team session. Use `/agileflow:team:start <template>` to create one."
-
-## Step 2: Display Team Info
-
-Show a formatted table with:
-
-| Field | Source |
-|-------|--------|
-| Team Template | session-state.json `active_team.template` |
-| Mode | native / subagent |
-| Lead | Team lead agent name |
-| Started | Timestamp |
-
-## Step 3: Show Teammate Statuses
-
-For each teammate, display:
-- Agent name and role (builder/validator/reviewer/analyzer)
-- Current status (working/idle/blocked)
-- Current task (if any)
-- Quality gate results (pass/fail per gate)
-
-### Native Mode
-
-Read from native task list and teammate status.
-
-### Subagent Mode
-
-Read from `docs/09-agents/bus/log.jsonl` for latest messages from each agent.
-
-## Step 4: Show Metrics (if available)
-
-If `session-state.json` has `team_metrics`:
-- Total elapsed time
-- Tasks completed per teammate
-- Quality gate pass rate
-- Messages exchanged

package/src/core/commands/team/stop.md

@@ -1,78 +0,0 @@
----
-description: Gracefully shut down a team
-argument-hint: "(no arguments)"
-compact_context:
-  priority: high
-  preserve_rules:
-    - "ACTIVE COMMAND: /agileflow:team:stop - Gracefully shut down team session"
-    - "Must sync final states to status.json before cleanup"
-    - "AskUserQuestion for confirmation before stopping"
-  state_fields:
-    - team_active
-    - final_task_states
----
-
-# /agileflow:team:stop
-
-Gracefully shut down an active team session.
-
----
-
-## Step 1: Check for Active Team
-
-Verify there is an active team session in `session-state.json`.
-
-If no active team, inform user: "No active team session to stop."
-
-## Step 2: Confirm with User
-
-Use AskUserQuestion:
-- "Stop the active team? This will end all teammate sessions."
-- Options: "Yes, stop team" / "No, keep running"
-
-## Step 3: Sync Final States
-
-Before stopping:
-
-1. **Collect final task states** from all teammates
-2. **Write results to status.json** — sync any completed stories, task progress
-3. **Save team metrics** to session-state.json for observability
-4. **Log coordination summary** to bus/log.jsonl
-
-## Step 4: Stop Teammates
-
-### Native Mode
-
-When `active_team.mode === "native"` in session-state.json:
-
-1. **Stop running teammate tasks**: Use `TaskStop` for any background teammate tasks still running
-2. **Attempt TeamDelete**: If the `TeamDelete` tool is available in your tool list, call it with the team name from `active_team.native_payload.name` to clean up the native team session
-3. **If TeamDelete is not available**: This is fine — teammate sessions will end naturally when their tasks complete. Log: "TeamDelete not available, teammates will complete naturally."
-
-### Subagent Mode
-
-No explicit cleanup needed — subagents end when their Task completes.
-
-## Step 5: Clear Team State
-
-Remove `active_team` from session-state.json:
-
-```bash
-node -e "
-const fs = require('fs');
-const p = require('./.agileflow/lib/paths');
-const statePath = p.getSessionStatePath();
-const state = JSON.parse(fs.readFileSync(statePath, 'utf8'));
-delete state.active_team;
-fs.writeFileSync(statePath, JSON.stringify(state, null, 2) + '\n');
-console.log('Team session ended.');
-"
-```
-
-## Step 6: Report
-
-Show summary:
-- Duration of team session
-- Tasks completed
-- Quality gate results
-- Stories updated