relay-cc 2.0.0

package/commands/relay/settings.md

@@ -0,0 +1,165 @@
+---
+name: relay:settings
+description: Configure Relay workflow toggles and model profile
+allowed-tools:
+  - Read
+  - Write
+  - AskUserQuestion
+---
+
+<objective>
+Allow users to toggle workflow agents on/off and select model profile via interactive settings.
+
+Updates `.relay/config.json` with workflow preferences and model profile selection.
+</objective>
+
+<process>
+
+## 1. Ensure config exists
+
+```bash
+ls .relay/config.json 2>/dev/null
+```
+
+If `.relay/config.json` missing, create it with defaults:
+```bash
+mkdir -p .relay
+```
+```json
+{
+  "model_profile": "balanced",
+  "workflow": {
+    "research": true,
+    "plan_check": true,
+    "verifier": true
+  }
+}
+```
+Write this to `.relay/config.json`, then continue.
+
+## 2. Read Current Config
+
+```bash
+cat .relay/config.json
+```
+
+Parse current values (default to `true` if not present):
+- `workflow.research` — spawn researcher during plan-phase
+- `workflow.plan_check` — spawn plan checker during plan-phase
+- `workflow.verifier` — spawn verifier during execute-phase
+- `model_profile` — which model each agent uses (default: `balanced`)
+- `git.branching_strategy` — branching approach (default: `"none"`)
+- `integration.type` — connected ticket system (jira, github, azure_devops, or null)
+- `integration.project_key` — project identifier for ticket system
+
+## 3. Present Settings
+
+Use AskUserQuestion with current values shown:
+
+```
+AskUserQuestion([
+  {
+    question: "Which model profile for agents?",
+    header: "Model",
+    multiSelect: false,
+    options: [
+      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
+      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for execution/verification" },
+      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" }
+    ]
+  },
+  {
+    question: "Spawn Plan Researcher? (researches domain before planning)",
+    header: "Research",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Research phase goals before planning" },
+      { label: "No", description: "Skip research, plan directly" }
+    ]
+  },
+  {
+    question: "Spawn Plan Checker? (verifies plans before execution)",
+    header: "Plan Check",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify plans meet phase goals" },
+      { label: "No", description: "Skip plan verification" }
+    ]
+  },
+  {
+    question: "Spawn Execution Verifier? (verifies phase completion)",
+    header: "Verifier",
+    multiSelect: false,
+    options: [
+      { label: "Yes", description: "Verify must-haves after execution" },
+      { label: "No", description: "Skip post-execution verification" }
+    ]
+  },
+  {
+    question: "Git branching strategy?",
+    header: "Branching",
+    multiSelect: false,
+    options: [
+      { label: "None (Recommended)", description: "Commit directly to current branch" },
+      { label: "Per Phase", description: "Create branch for each phase (relay/phase-{N}-{name})" },
+      { label: "Per Ticket", description: "Create branch for each ticket ({ticket_id}/{slug})" }
+    ]
+  }
+])
+```
+
+**Pre-select based on current config values.**
+
+## 4. Update Config
+
+Merge new settings into existing config.json:
+
+```json
+{
+  ...existing_config,
+  "model_profile": "quality" | "balanced" | "budget",
+  "workflow": {
+    "research": true/false,
+    "plan_check": true/false,
+    "verifier": true/false
+  },
+  "git": {
+    "branching_strategy": "none" | "phase" | "ticket"
+  }
+}
+```
+
+Write updated config to `.relay/config.json`.
+
+## 5. Confirm Changes
+
+Display:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► SETTINGS UPDATED
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Setting              | Value |
+|----------------------|-------|
+| Model Profile        | {quality/balanced/budget} |
+| Plan Researcher      | {On/Off} |
+| Plan Checker         | {On/Off} |
+| Execution Verifier   | {On/Off} |
+| Git Branching        | {None/Per Phase/Per Ticket} |
+
+These settings apply to future `/relay:work` runs.
+
+Quick commands:
+- /relay:set-profile <profile> — switch model profile
+- /relay:setup — reconfigure integration
+```
+
+</process>
+
+<success_criteria>
+- [ ] Current config read
+- [ ] User presented with 5 settings (profile + 3 workflow toggles + git branching)
+- [ ] Config updated with model_profile, workflow, and git sections
+- [ ] Changes confirmed to user
+</success_criteria>

package/commands/relay/setup.md

@@ -0,0 +1,247 @@
+---
+name: relay:setup
+description: Configure Relay for your project — detect integrations, map codebase, initialize .relay/
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - Task
+  - AskUserQuestion
+---
+
+<objective>
+Initialize Relay for the current project. Detects available MCP integrations (Jira, GitHub Issues, Azure DevOps), configures the project, maps the codebase, and creates `.relay/` directory structure.
+
+This replaces the old `/relay:new-project` command with a ticket-driven setup flow.
+</objective>
+
+<process>
+
+## 1. Check Existing Setup
+
+```bash
+test -f .relay/config.json && echo "exists" || echo "missing"
+```
+
+**If `.relay/config.json` exists:**
+
+Read current config and offer options:
+
+```
+AskUserQuestion(
+  header: "Setup",
+  question: "Relay is already configured for this project. What would you like to do?",
+  options: [
+    { label: "Reconfigure", description: "Update integration settings and refresh config" },
+    { label: "Cancel", description: "Keep current configuration" }
+  ]
+)
+```
+
+If "Cancel", STOP.
+
+## 2. Detect Available MCP Integrations
+
+Probe for available MCP tools by checking what's available:
+
+```bash
+# Check for Jira MCP tools
+echo "Checking integrations..."
+```
+
+Check for these MCP tool patterns (use tool availability, not execution):
+- `mcp__jira__*` → Jira integration available
+- `mcp__github__*` → GitHub Issues integration available
+- `mcp__azure_devops__*` → Azure DevOps integration available
+
+Report what was detected.
+
+## 3. Configure Integration
+
+Based on detected MCP tools, ask user to confirm:
+
+```
+AskUserQuestion(
+  header: "Integration",
+  question: "Which ticket system should Relay connect to?",
+  options: [
+    { label: "Jira", description: "Connect via Jira MCP server" },
+    { label: "GitHub Issues", description: "Connect via GitHub MCP server" },
+    { label: "Azure DevOps", description: "Connect via Azure DevOps MCP server" },
+    { label: "None", description: "Use Relay without external ticket system" }
+  ]
+)
+```
+
+If an integration is selected, ask for the project key:
+
+```
+AskUserQuestion(
+  header: "Project",
+  question: "What is your project key? (e.g., PROJ for Jira, owner/repo for GitHub)",
+  options: [
+    { label: "Enter key", description: "Provide your project identifier" }
+  ]
+)
+```
+
+## 4. Detect Existing Code
+
+Check if this is a brownfield project:
+
+```bash
+# Count source files (exclude node_modules, .git, etc.)
+find . -type f \( -name "*.js" -o -name "*.ts" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.java" -o -name "*.rb" -o -name "*.php" -o -name "*.cs" -o -name "*.swift" -o -name "*.kt" \) ! -path "*/node_modules/*" ! -path "*/.git/*" ! -path "*/vendor/*" ! -path "*/dist/*" ! -path "*/build/*" 2>/dev/null | wc -l
+```
+
+If source files > 0, offer codebase mapping:
+
+```
+AskUserQuestion(
+  header: "Codebase",
+  question: "Existing code detected. Map the codebase for better analysis?",
+  options: [
+    { label: "Yes (Recommended)", description: "Run parallel codebase mappers to understand the project" },
+    { label: "Skip", description: "Set up without codebase mapping" }
+  ]
+)
+```
+
+## 5. Create `.relay/` Structure
+
+```bash
+mkdir -p .relay/tickets
+mkdir -p .relay/codebase
+mkdir -p .relay/debug
+mkdir -p .relay/quick
+mkdir -p .relay/todos/pending
+```
+
+## 6. Write Config
+
+Write `.relay/config.json` with detected settings:
+
+```json
+{
+  "mode": "interactive",
+  "depth": "standard",
+  "integration": {
+    "type": "{jira|github|azure_devops|null}",
+    "project_key": "{project_key|null}",
+    "mcp_server": "{mcp_server_name|null}"
+  },
+  "workflow": {
+    "research": true,
+    "plan_check": true,
+    "verifier": true
+  },
+  "planning": {
+    "commit_docs": true,
+    "search_gitignored": false
+  },
+  "parallelization": {
+    "enabled": true,
+    "plan_level": true,
+    "task_level": false,
+    "skip_checkpoints": true,
+    "max_concurrent_agents": 3,
+    "min_plans_for_parallel": 2
+  },
+  "gates": {
+    "confirm_analysis": true,
+    "confirm_plan": true,
+    "confirm_execution": true,
+    "confirm_sync": true,
+    "issues_review": true
+  },
+  "git": {
+    "ticket_branch_template": "{ticket_id}/{slug}"
+  },
+  "safety": {
+    "always_confirm_destructive": true,
+    "always_confirm_external_services": true
+  }
+}
+```
+
+## 7. Write STATE.md
+
+Write `.relay/STATE.md` from template:
+
+```markdown
+# Relay State
+
+## Active Ticket
+
+**Ticket:** None
+**Branch:** —
+**Stage:** —
+**Started:** —
+
+## Recent Tickets
+
+| Ticket | Title | Status | Branch | Completed |
+|--------|-------|--------|--------|-----------|
+
+## Velocity Metrics
+
+**Completed:** 0 tickets
+**Average duration:** —
+**Recent trend:** —
+
+## Session Continuity
+
+Last session: {current date}
+Stopped at: Initial setup
+Resume file: None
+
+## Pending Todos
+
+None yet.
+
+## Blockers/Concerns
+
+None yet.
+```
+
+## 8. Run Codebase Mapping (if selected)
+
+If user opted for codebase mapping:
+
+```
+SlashCommand("relay:map-codebase")
+```
+
+## 9. Display Completion
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► SETUP COMPLETE
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| Setting            | Value                          |
+|--------------------|--------------------------------|
+| Integration        | {type or "None"}               |
+| Project Key        | {key or "—"}                   |
+| Codebase Mapped    | {Yes/No}                       |
+
+## Next Steps
+
+- `/relay:tickets` — browse available tickets
+- `/relay:work <ticket-id>` — start working on a ticket
+- `/relay:settings` — adjust workflow settings
+```
+
+</process>
+
+<success_criteria>
+- [ ] MCP integrations detected
+- [ ] Integration type and project key configured
+- [ ] `.relay/` directory structure created
+- [ ] `config.json` written with integration settings
+- [ ] `STATE.md` initialized
+- [ ] Codebase mapping offered for brownfield projects
+- [ ] User knows next steps (`/relay:tickets` or `/relay:work`)
+</success_criteria>

package/commands/relay/status.md

@@ -0,0 +1,131 @@
+---
+name: relay:status
+description: Show current Relay status — active ticket, recent work, and next actions
+allowed-tools:
+  - Read
+  - Bash
+  - Grep
+  - Glob
+  - SlashCommand
+---
+
+<objective>
+Show the current state of Relay for this project: active ticket progress, recent tickets, and routing to the next action.
+
+Provides situational awareness before continuing work.
+</objective>
+
+<process>
+
+<step name="verify">
+**Verify Relay structure exists:**
+
+```bash
+test -d .relay && echo "exists" || echo "missing"
+```
+
+If no `.relay/` directory:
+
+```
+No Relay setup found.
+
+Run /relay:setup to initialize Relay for this project.
+```
+
+STOP.
+
+If missing STATE.md: suggest `/relay:setup`.
+</step>
+
+<step name="load">
+**Load project context:**
+
+- Read `.relay/STATE.md` for current state
+- Read `.relay/config.json` for settings
+</step>
+
+<step name="active_ticket">
+**Check active ticket:**
+
+From STATE.md, extract:
+- Active ticket ID and title
+- Current stage (FETCHING, ANALYZING, PLANNING, EXECUTING, VERIFYING, SYNCING)
+- Branch name
+- When started
+
+If active ticket exists, read its artifacts:
+```bash
+ls .relay/tickets/${TICKET_ID}/ 2>/dev/null
+```
+</step>
+
+<step name="recent">
+**Gather recent work:**
+
+- Read recent tickets table from STATE.md
+- Count pending todos: `ls .relay/todos/pending/*.md 2>/dev/null | wc -l`
+- Check for active debug sessions: `ls .relay/debug/*.md 2>/dev/null | grep -v resolved | wc -l`
+</step>
+
+<step name="report">
+**Present status report:**
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► STATUS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+## Active Ticket
+
+{TICKET_ID}: {title}
+Stage: {ANALYZING | PLANNING | EXECUTING | VERIFYING}
+Branch: {branch_name}
+Started: {date}
+
+## Recent Tickets
+
+| Ticket | Title | Status | Completed |
+|--------|-------|--------|-----------|
+| {id} | {title} | {done/verified} | {date} |
+
+## Velocity
+
+Completed: {N} tickets
+Average: {duration}
+
+## Pending Todos
+
+{count} pending — /relay:check-todos to review
+
+## Active Debug Sessions
+
+{count} active — /relay:debug to continue
+(Only show this section if count > 0)
+```
+</step>
+
+<step name="route">
+**Route to next action:**
+
+| State | Suggestion |
+|-------|-----------|
+| Active ticket in progress | `/relay:work {ID}` to resume |
+| No active ticket | `/relay:tickets` to browse, `/relay:work <id>` to start |
+| Paused ticket (.continue-here exists) | `/relay:resume-work` to continue |
+
+```
+## Next Steps
+
+{context-appropriate suggestion}
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Current state loaded from STATE.md
+- [ ] Active ticket shown with stage
+- [ ] Recent tickets displayed
+- [ ] Smart routing to next action
+- [ ] User knows what to do next
+</success_criteria>

package/commands/relay/tickets.md

@@ -0,0 +1,106 @@
+---
+name: relay:tickets
+description: Browse and select tickets from your connected ticket system
+allowed-tools:
+  - Read
+  - Bash
+  - Grep
+  - AskUserQuestion
+  - mcp__jira__search
+  - mcp__jira__get_issue
+  - mcp__github__search_issues
+  - mcp__github__get_issue
+  - mcp__azure_devops__get_work_items
+---
+
+<objective>
+Fetch and display tickets from the configured external ticket system (Jira, GitHub Issues, or Azure DevOps) via MCP tools.
+
+Presents a formatted table of available tickets and suggests `/relay:work <id>` to start working.
+</objective>
+
+<context>
+@.relay/config.json
+@.relay/STATE.md
+</context>
+
+<process>
+
+## 1. Read Configuration
+
+```bash
+cat .relay/config.json 2>/dev/null || echo "missing"
+```
+
+If config missing:
+```
+No Relay configuration found. Run `/relay:setup` first.
+```
+STOP.
+
+Extract integration settings:
+- `integration.type` — jira, github, azure_devops, or null
+- `integration.project_key` — project identifier
+- `integration.mcp_server` — MCP server name
+
+If `integration.type` is null:
+```
+No ticket system configured. Run `/relay:setup` to connect one,
+or use `/relay:work` directly with a ticket description.
+```
+STOP.
+
+## 2. Fetch Tickets
+
+Based on integration type, fetch open tickets:
+
+**Jira:**
+Use `mcp__jira__search` with JQL:
+```
+project = {project_key} AND status NOT IN (Done, Closed) ORDER BY priority DESC, updated DESC
+```
+
+**GitHub Issues:**
+Use `mcp__github__search_issues` with:
+```
+repo:{project_key} state:open sort:updated-desc
+```
+
+**Azure DevOps:**
+Use `mcp__azure_devops__get_work_items` with query for open items in the project.
+
+## 3. Display Tickets
+
+Format as a table:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► TICKETS
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+| ID | Title | Type | Priority | Assignee |
+|----|-------|------|----------|----------|
+| {id} | {title} | {type} | {priority} | {assignee} |
+...
+
+Showing {N} open tickets from {project_key}
+```
+
+## 4. Suggest Next Action
+
+```
+## Next Steps
+
+`/relay:work <ticket-id>` — start working on a ticket
+
+Example: `/relay:work PROJ-123`
+```
+
+</process>
+
+<success_criteria>
+- [ ] Config read and integration type detected
+- [ ] Tickets fetched from external system via MCP
+- [ ] Formatted table displayed
+- [ ] User directed to `/relay:work <id>`
+</success_criteria>