relay-cc 2.0.0

package/commands/relay/map-codebase.md

@@ -0,0 +1,71 @@
+---
+name: relay:map-codebase
+description: Analyze codebase with parallel mapper agents to produce .relay/codebase/ documents
+argument-hint: "[optional: specific area to map, e.g., 'api' or 'auth']"
+allowed-tools:
+  - Read
+  - Bash
+  - Glob
+  - Grep
+  - Write
+  - Task
+---
+
+<objective>
+Analyze existing codebase using parallel relay-codebase-mapper agents to produce structured codebase documents.
+
+Each mapper agent explores a focus area and **writes documents directly** to `.relay/codebase/`. The orchestrator only receives confirmations, keeping context usage minimal.
+
+Output: .relay/codebase/ folder with 7 structured documents about the codebase state.
+</objective>
+
+<execution_context>
+@~/.claude/relay/workflows/map-codebase.md
+</execution_context>
+
+<context>
+Focus area: $ARGUMENTS (optional - if provided, tells agents to focus on specific subsystem)
+
+**Load project state if exists:**
+Check for .relay/STATE.md - loads context if project already initialized
+
+**This command can run:**
+- Before /relay:new-project (brownfield codebases) - creates codebase map first
+- After /relay:new-project (greenfield codebases) - updates codebase map as code evolves
+- Anytime to refresh codebase understanding
+</context>
+
+<when_to_use>
+**Use map-codebase for:**
+- Brownfield projects before initialization (understand existing code first)
+- Refreshing codebase map after significant changes
+- Onboarding to an unfamiliar codebase
+- Before major refactoring (understand current state)
+- When STATE.md references outdated codebase info
+
+**Skip map-codebase for:**
+- Greenfield projects with no code yet (nothing to map)
+- Trivial codebases (<5 files)
+</when_to_use>
+
+<process>
+1. Check if .relay/codebase/ already exists (offer to refresh or skip)
+2. Create .relay/codebase/ directory structure
+3. Spawn 4 parallel relay-codebase-mapper agents:
+   - Agent 1: tech focus → writes STACK.md, INTEGRATIONS.md
+   - Agent 2: arch focus → writes ARCHITECTURE.md, STRUCTURE.md
+   - Agent 3: quality focus → writes CONVENTIONS.md, TESTING.md
+   - Agent 4: concerns focus → writes CONCERNS.md
+4. Wait for agents to complete, collect confirmations (NOT document contents)
+5. Verify all 7 documents exist with line counts
+6. Commit codebase map
+7. Offer next steps (typically: /relay:new-project or /relay:plan-phase)
+</process>
+
+<success_criteria>
+- [ ] .relay/codebase/ directory created
+- [ ] All 7 codebase documents written by mapper agents
+- [ ] Documents follow template structure
+- [ ] Parallel agents completed without errors
+- [ ] User knows next steps
+</success_criteria>

package/commands/relay/pause-work.md

@@ -0,0 +1,128 @@
+---
+name: relay:pause-work
+description: Create context handoff when pausing work on a ticket
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+<objective>
+Create `.continue-here.md` handoff file to preserve complete work state across sessions.
+
+Enables seamless resumption in fresh session with full context restoration.
+</objective>
+
+<context>
+@.relay/STATE.md
+</context>
+
+<process>
+
+<step name="detect">
+**Find active ticket from STATE.md.**
+
+Read STATE.md and extract active ticket ID. If no active ticket, report:
+```
+No active ticket found. Nothing to pause.
+```
+STOP.
+</step>
+
+<step name="gather">
+**Collect complete state for handoff:**
+
+1. **Current position**: Which ticket, which stage, which task
+2. **Work completed**: What got done this session
+3. **Work remaining**: What's left in current plan
+4. **Decisions made**: Key decisions and rationale
+5. **Blockers/issues**: Anything stuck
+6. **Mental context**: The approach, next steps
+7. **Files modified**: What's changed but not committed
+
+Ask user for clarifications if needed.
+</step>
+
+<step name="write">
+**Write handoff to `.relay/tickets/${TICKET_ID}/.continue-here.md`:**
+
+```markdown
+---
+ticket: ${TICKET_ID}
+stage: ${CURRENT_STAGE}
+status: paused
+last_updated: [timestamp]
+---
+
+<current_state>
+[Where exactly are we? Immediate context]
+</current_state>
+
+<completed_work>
+- [What was accomplished]
+</completed_work>
+
+<remaining_work>
+- [What's left to do]
+</remaining_work>
+
+<decisions_made>
+- [Key decisions and rationale]
+</decisions_made>
+
+<blockers>
+- [Any blockers or issues]
+</blockers>
+
+<context>
+[Mental state, the plan, approach being taken]
+</context>
+
+<next_action>
+Start with: [specific first action when resuming]
+</next_action>
+```
+
+Be specific enough for a fresh Claude to understand immediately.
+</step>
+
+<step name="commit">
+**Check planning config:**
+
+```bash
+COMMIT_PLANNING_DOCS=$(cat .relay/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
+git check-ignore -q .relay 2>/dev/null && COMMIT_PLANNING_DOCS=false
+```
+
+**If `COMMIT_PLANNING_DOCS=false`:** Skip git operations
+
+**If `COMMIT_PLANNING_DOCS=true` (default):**
+
+```bash
+git add .relay/tickets/${TICKET_ID}/.continue-here.md
+git commit -m "wip(${TICKET_ID}): paused work"
+```
+</step>
+
+<step name="confirm">
+```
+Handoff created: .relay/tickets/${TICKET_ID}/.continue-here.md
+
+Current state:
+- Ticket: ${TICKET_ID}
+- Stage: ${CURRENT_STAGE}
+- Status: paused
+
+To resume: /relay:resume-work
+```
+</step>
+
+</process>
+
+<success_criteria>
+- [ ] Active ticket identified from STATE.md
+- [ ] .continue-here.md created in ticket directory
+- [ ] All sections filled with specific content
+- [ ] Committed as WIP
+- [ ] User knows how to resume
+</success_criteria>

package/commands/relay/pr.md

@@ -0,0 +1,223 @@
+---
+name: relay:pr
+description: Create a pull request from completed ticket work
+argument-hint: [ticket-id]
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+  - Glob
+  - Grep
+  - AskUserQuestion
+  - mcp__jira__add_comment
+  - mcp__github__create_comment
+  - mcp__azure_devops__update_work_item
+---
+
+<objective>
+Create a pull request from completed ticket work with auto-generated title and description based on ticket artifacts (ANALYSIS.md, SUMMARY.md, VERIFICATION.md).
+
+No agents spawned — orchestration only.
+</objective>
+
+<context>
+@.relay/config.json
+@.relay/STATE.md
+Ticket ID: $ARGUMENTS
+</context>
+
+<process>
+
+## 0. Pre-flight
+
+```bash
+test -f .relay/config.json && echo "config exists" || echo "no config"
+command -v gh >/dev/null 2>&1 && echo "gh available" || echo "gh missing"
+gh auth status 2>&1 | head -1
+```
+
+If no config: suggest `/relay:setup` and STOP.
+If `gh` CLI not available or not authenticated: report requirement and STOP.
+
+## 1. Resolve Ticket ID
+
+**If $ARGUMENTS provided:** Use as ticket ID.
+
+**If no arguments:** Try to detect from STATE.md active ticket or current branch:
+
+```bash
+# Try active ticket from STATE.md
+grep -oE 'Active.*: [A-Z]+-[0-9]+' .relay/STATE.md 2>/dev/null | grep -oE '[A-Z]+-[0-9]+' | head -1
+
+# Try current branch name
+git branch --show-current | grep -oE '[A-Z]+-[0-9]+' | head -1
+```
+
+If no ticket ID resolved:
+```
+AskUserQuestion(
+  header: "Ticket",
+  question: "Which ticket's work should this PR cover?",
+  options: [
+    { label: "Enter ID", description: "Type a ticket ID (e.g., PROJ-123)" },
+    { label: "Browse tickets", description: "See tickets with existing work" }
+  ]
+)
+```
+
+## 2. Gather Context
+
+Read ticket artifacts:
+
+```bash
+test -f .relay/tickets/${TICKET_ID}/ANALYSIS.md && echo "analysis exists"
+test -f .relay/tickets/${TICKET_ID}/SUMMARY.md && echo "summary exists"
+test -f .relay/tickets/${TICKET_ID}/VERIFICATION.md && echo "verification exists"
+```
+
+Read available artifacts and extract:
+- **From ANALYSIS.md:** Ticket title, type, acceptance criteria
+- **From SUMMARY.md:** What was implemented, key decisions
+- **From VERIFICATION.md:** Pass/fail status, coverage
+
+Get git context:
+
+```bash
+# Diff stat against main/master
+BASE_BRANCH=$(git remote show origin 2>/dev/null | grep 'HEAD branch' | sed 's/.*: //')
+BASE_BRANCH=${BASE_BRANCH:-main}
+
+git diff ${BASE_BRANCH}...HEAD --stat
+git log ${BASE_BRANCH}...HEAD --oneline
+```
+
+## 3. Generate PR Content
+
+**Title format:** `${TICKET_ID}: ${ticket_title}`
+
+**Body format:**
+
+```markdown
+## Summary
+
+{2-3 bullet points from SUMMARY.md describing what was done}
+
+## Changes
+
+{diff stat summary — files changed, insertions, deletions}
+
+## Verification
+
+{pass/fail status from VERIFICATION.md}
+{list acceptance criteria with check marks}
+
+## Commits
+
+{list of commits from git log}
+
+---
+
+Ticket: ${TICKET_ID}
+Generated by [Relay](https://github.com/ibnyusrat/relay)
+```
+
+## 4. Preview and Confirm
+
+Display the generated PR:
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► PR PREVIEW — ${TICKET_ID}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+Title: ${PR_TITLE}
+
+${PR_BODY}
+```
+
+```
+AskUserQuestion(
+  header: "Create PR",
+  question: "How would you like to proceed?",
+  options: [
+    { label: "Create PR", description: "Push branch and create pull request" },
+    { label: "Edit title", description: "Modify the PR title before creating" },
+    { label: "Edit body", description: "Modify the PR description before creating" },
+    { label: "Cancel", description: "Don't create a PR" }
+  ]
+)
+```
+
+If "Edit title": ask for new title, then re-preview.
+If "Edit body": ask for changes, then re-preview.
+If "Cancel": STOP.
+
+## 5. Push and Create PR
+
+```bash
+# Push branch
+CURRENT_BRANCH=$(git branch --show-current)
+git push -u origin "${CURRENT_BRANCH}"
+
+# Create PR
+gh pr create --title "${PR_TITLE}" --body "${PR_BODY}" --base "${BASE_BRANCH}"
+```
+
+Capture PR URL from output.
+
+## 6. Update State
+
+Update STATE.md with PR link:
+
+```bash
+# Add PR reference to ticket's section in STATE.md
+PR_URL=$(gh pr view --json url --jq '.url')
+```
+
+## 7. Optional: Post PR Link to Ticket System
+
+If integration is configured:
+
+```
+AskUserQuestion(
+  header: "Sync",
+  question: "Post PR link back to ${TICKET_ID}?",
+  options: [
+    { label: "Post link", description: "Add PR URL as comment on the ticket" },
+    { label: "Skip", description: "Don't update the external ticket" }
+  ]
+)
+```
+
+If "Post link": use appropriate MCP tool to add comment with PR URL.
+
+## 8. Completion
+
+```
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+ Relay ► PR CREATED — ${TICKET_ID}
+━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+PR: ${PR_URL}
+Title: ${PR_TITLE}
+Branch: ${CURRENT_BRANCH} → ${BASE_BRANCH}
+
+## Next Steps
+
+- Review the PR at ${PR_URL}
+- `/relay:tickets` — pick another ticket
+- `/relay:work <id>` — start next ticket
+```
+
+</process>
+
+<success_criteria>
+- [ ] Ticket ID resolved (from argument, STATE.md, or branch)
+- [ ] Ticket artifacts read for context
+- [ ] PR title and body generated from artifacts
+- [ ] User previewed and approved content
+- [ ] Branch pushed to remote
+- [ ] PR created via `gh pr create`
+- [ ] STATE.md updated with PR link
+- [ ] Optionally synced PR link to ticket system
+</success_criteria>