QUAD Slash Commands

Custom Commands for QUAD Methodology

Overview

Command Categories

Story Commands

Overview

What Are QUAD Commands?

QUAD provides custom slash commands that users can invoke from:

• Chat (Claude, Copilot, ChatGPT)

• IDE (VS Code, Cursor)

• CLI (Terminal)

• Jira/Confluence (via plugins)

┌──────────────────────────────────────────────────────────────────────┐
│                    QUAD COMMAND ARCHITECTURE                         │
├──────────────────────────────────────────────────────────────────────┤
│                                                                      │
│  USER TYPES:        WHERE IT'S PARSED:      WHAT EXECUTES:           │
│                                                                      │
│  /expand-story      Chat Interface          QAR invokes              │
│  PROJ-123          (Claude, Copilot)        story-agent              │
│       │                   │                      │                   │
│       │                   ▼                      ▼                   │
│       │            ┌─────────────┐        ┌─────────────┐            │
│       └───────────▶│ QUAD        │───────▶│ Story       │            │
│                    │ Command     │        │ Agent       │            │
│                    │ Router      │        │             │            │
│                    └─────────────┘        └─────────────┘            │
│                                                                      │
│  Command Format:                                                     │
│  ┌─────────────────────────────────────────────────────────────────┐│
│  │  /command-name [target] [--options]                              ││
│  │                                                                   ││
│  │  Examples:                                                        ││
│  │  /expand-story PROJ-123                                          ││
│  │  /estimate PROJ-123 --detailed                                   ││
│  │  /pipeline estimation --story=PROJ-123                           ││
│  │  /label add PROJ-123 priority/P0 type/SECURITY                   ││
│  └─────────────────────────────────────────────────────────────────┘│
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

Command Prefix

All QUAD commands start with / followed by the command name:

Prefix StyleExampleUse Case /command/expand-storyStandard QUAD command /quad command/quad expand-storyExplicit namespace (if conflicts) quad commandquad expand-storyCLI style (no slash in terminal)

Command Categories

┌──────────────────────────────────────────────────────────────────────┐
│                    QUAD COMMAND CATEGORIES                           │
├──────────────────────────────────────────────────────────────────────┤
│                                                                      │
│  ┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐      │
│  │  STORY          │  │  ESTIMATION     │  │  PIPELINE       │      │
│  │  Commands       │  │  Commands       │  │  Commands       │      │
│  ├─────────────────┤  ├─────────────────┤  ├─────────────────┤      │
│  │ /expand-story   │  │ /estimate       │  │ /pipeline       │      │
│  │ /split-story    │  │ /complexity     │  │ /run            │      │
│  │ /merge-stories  │  │ /effort         │  │ /status         │      │
│  │ /refine-story   │  │                 │  │ /cancel         │      │
│  └─────────────────┘  └─────────────────┘  └─────────────────┘      │
│                                                                      │
│  ┌─────────────────┐  ┌─────────────────┐  ┌─────────────────┐      │
│  │  AGENT          │  │  LABEL          │  │  SPRINT         │      │
│  │  Commands       │  │  Commands       │  │  Commands       │      │
│  ├─────────────────┤  ├─────────────────┤  ├─────────────────┤      │
│  │ /agent          │  │ /label          │  │ /sprint         │      │
│  │ /invoke         │  │ /filter         │  │ /plan           │      │
│  │ /agents         │  │ /bulk-label     │  │ /velocity       │      │
│  └─────────────────┘  └─────────────────┘  └─────────────────┘      │
│                                                                      │
│  ┌─────────────────┐  ┌─────────────────┐                           │
│  │  CONTEXT        │  │  CONFIG         │                           │
│  │  Commands       │  │  Commands       │                           │
│  ├─────────────────┤  ├─────────────────┤                           │
│  │ /context        │  │ /config         │                           │
│  │ /project        │  │ /setup          │                           │
│  │ /history        │  │ /audit          │                           │
│  └─────────────────┘  └─────────────────┘                           │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

Story Commands

/expand-story

Purpose: Expand a brief requirement into full user stories with acceptance criteria.

<h1 class="text-3xl font-bold text-white mb-8">Basic usage</h1>
/expand-story PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">With options</h1>
/expand-story PROJ-123 --detailed --include-tests
/expand-story PROJ-123 --format=gherkin
/expand-story "As a user, I want to login" --project=PROJ

What happens:

Story Agent reads the original requirement

Uses AI (Gemini/Claude) to expand

Generates:

- Detailed user stories - Acceptance criteria (Given/When/Then) - Technical specifications - Test scenarios - Edge cases

Writes output to Confluence/Jira

Options: OptionDescriptionDefault --detailedInclude technical specsfalse --include-testsGenerate test scenariosfalse --formatOutput format: standard, gherkin, yamlstandard --projectProject key if not in story IDauto-detect --outputWhere to write: jira, confluence, stdoutjira Example Output:

✓ Story PROJ-123 expanded successfully Generated: • 4 user stories (PROJ-124, PROJ-125, PROJ-126, PROJ-127) • 12 acceptance criteria • 8 test scenarios • Technical spec linked in Confluence

Complexity estimate: OCTAHEDRON (8 points)

/split-story

Purpose: Split a large story (ICOSAHEDRON) into smaller stories.

<h1 class="text-3xl font-bold text-white mb-8">Basic usage</h1>
/split-story PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Split into specific number</h1>
/split-story PROJ-123 --into=3
<h1 class="text-3xl font-bold text-white mb-8">Split by platform</h1>
/split-story PROJ-123 --by=platform

Options: OptionDescriptionDefault --intoTarget number of storiesauto (by complexity) --bySplit strategy: platform, layer, featureauto --preserve-parentKeep original as epictrue Example:

/split-story PROJ-123 --by=platform
✓ Story PROJ-123 split into 4 stories:
  PROJ-124: [API] User authentication endpoint
            Complexity: CUBE (6 pts)
  PROJ-125: [WEB] Login page UI
            Complexity: CUBE (6 pts)
  PROJ-126: [IOS] Native login screen
            Complexity: TETRAHEDRON (4 pts)
  PROJ-127: [ANDROID] Native login screen
            Complexity: TETRAHEDRON (4 pts)
Original PROJ-123 converted to Epic (parent of above)

/refine-story

Purpose: Improve an existing story based on feedback or questions.

<h1 class="text-3xl font-bold text-white mb-8">Refine with specific feedback</h1>
/refine-story PROJ-123 --feedback="Need to handle SSO case"
<h1 class="text-3xl font-bold text-white mb-8">Refine based on BA answers</h1>
/refine-story PROJ-123 --answers-from=CONF-456
<h1 class="text-3xl font-bold text-white mb-8">Interactive refinement</h1>
/refine-story PROJ-123 --interactive

/merge-stories

Purpose: Combine related stories that should be one.

/merge-stories PROJ-123 PROJ-124 PROJ-125 --into=PROJ-123

Estimation Commands

/estimate

Purpose: Estimate complexity using Platonic Solid scale.

<h1 class="text-3xl font-bold text-white mb-8">Basic estimation</h1>
/estimate PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Detailed breakdown</h1>
/estimate PROJ-123 --detailed
<h1 class="text-3xl font-bold text-white mb-8">Estimate multiple</h1>
/estimate PROJ-123 PROJ-124 PROJ-125
<h1 class="text-3xl font-bold text-white mb-8">Re-estimate with new info</h1>
/estimate PROJ-123 --reason="API complexity higher than expected"

What happens:

Runs Estimation Pipeline (SEQUENTIAL):

- Code Agent: Analyzes code complexity - DB Agent: Analyzes database impact - Flow Agent: Analyzes integration complexity - Estimation Agent: Produces final estimate

Returns Platonic Solid complexity

Example Output:

/estimate PROJ-123 --detailed

┌─────────────────────────────────────────────────────────────────┐ │ ESTIMATION: PROJ-123 - User Authentication │ ├─────────────────────────────────────────────────────────────────┤ │ │ │ Final Estimate: OCTAHEDRON (8 points) │ │ │ │ Breakdown: │ │ ┌──────────────┬────────┬─────────────────────────────────┐ │ │ │ Dimension │ Score │ Notes │ │ │ ├──────────────┼────────┼─────────────────────────────────┤ │ │ │ Code │ 7/10 │ Multi-layer: API, Service, DTO │ │ │ │ Database │ 5/10 │ 3 tables, simple schema │ │ │ │ Integration │ 8/10 │ Redis, Email service, JWT │ │ │ │ Testing │ 6/10 │ Security tests required │ │ │ └──────────────┴────────┴─────────────────────────────────┘ │ │ │ │ Risk Factors: │ │ ⚠ Security-sensitive (auth bypass risk) │ │ ⚠ External dependency (email service) │ │ │ │ Suggested Team: backend-dev + security-reviewer │ │ Suggested Sprint Duration: 3-4 days │ │ │ └─────────────────────────────────────────────────────────────────┘

/complexity

Purpose: Quick complexity check without full pipeline.

<h1 class="text-3xl font-bold text-white mb-8">Quick check</h1>
/complexity PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Output:</h1>
<h1 class="text-3xl font-bold text-white mb-8">PROJ-123: CUBE (6 points) - Standard feature, 2-3 days</h1>

Pipeline Commands

/pipeline

Purpose: Run or manage agent pipelines.

<h1 class="text-3xl font-bold text-white mb-8">Run estimation pipeline</h1>
/pipeline estimation --story=PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Run development pipeline</h1>
/pipeline development --story=PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Run custom pipeline</h1>
/pipeline code-review --pr=456
<h1 class="text-3xl font-bold text-white mb-8">List available pipelines</h1>
/pipeline list
<h1 class="text-3xl font-bold text-white mb-8">Check pipeline status</h1>
/pipeline status --id=pipeline-abc123

Available Pipelines: PipelineModeAgents estimationSEQUENTIALcode → db → flow → estimation developmentHYBRID[dev-ui, dev-api] → [test-ui, test-api] → review code-reviewSEQUENTIALsecurity-scanner → code-review → a11y-scanner deploymentSEQUENTIALtest → build → deploy-dev → deploy-qa Example:

/pipeline estimation --story=PROJ-123
✓ Pipeline 'estimation' started
  Pipeline ID: est-20250101-abc123
  Mode: SEQUENTIAL
  Progress:
  [████████░░░░░░░░░░░░] 40%
  Steps:
  ✓ code-agent     (2.3s)  code_complexity: 7
  ✓ db-agent       (1.1s)  db_impact: 5
  ○ flow-agent     (running...)
  ○ estimation-agent
  ETA: ~15 seconds

/run

Purpose: Shorthand for running pipelines or agents.

<h1 class="text-3xl font-bold text-white mb-8">Run pipeline</h1>
/run estimation PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Run single agent</h1>
/run story-agent PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Run with verbose output</h1>
/run estimation PROJ-123 --verbose

Agent Commands

/agent

Purpose: Invoke or manage individual agents.

<h1 class="text-3xl font-bold text-white mb-8">Invoke specific agent</h1>
/agent invoke story-agent --story-id=PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Check agent status</h1>
/agent status story-agent
<h1 class="text-3xl font-bold text-white mb-8">List all agents</h1>
/agent list
<h1 class="text-3xl font-bold text-white mb-8">Get agent info</h1>
/agent info dev-agent-ui

Example:

/agent list

┌──────────────────────────────────────────────────────────────────────┐ │ AVAILABLE AGENTS │ ├──────────────────────────────────────────────────────────────────────┤ │ │ │ Circle 1: MANAGEMENT │ │ ├── story-agent Expands requirements into stories │ │ ├── estimation-agent Calculates complexity estimates │ │ └── pm-agent Project management assistance │ │ │ │ Circle 2: DEVELOPMENT │ │ ├── dev-agent-ui Frontend development (React, iOS, Android) │ │ ├── dev-agent-api Backend development (API, Services) │ │ ├── code-agent Code analysis and metrics │ │ └── review-agent Code review and suggestions │ │ │ │ Circle 3: QA │ │ ├── test-agent Test generation and execution │ │ ├── security-agent Security scanning and analysis │ │ └── perf-agent Performance testing │ │ │ │ Circle 4: INFRASTRUCTURE │ │ ├── deploy-agent-dev Deploy to development environment │ │ ├── deploy-agent-qa Deploy to QA environment │ │ ├── db-agent Database analysis and migrations │ │ └── infra-agent Infrastructure provisioning │ │ │ └──────────────────────────────────────────────────────────────────────┘

/invoke

Purpose: Shorthand for agent invocation.

<h1 class="text-3xl font-bold text-white mb-8">Equivalent to /agent invoke</h1>
/invoke story-agent PROJ-123
/invoke dev-agent-ui --story=PROJ-123 --branch=feature/auth

Label Commands

/label

Purpose: Manage story labels.

<h1 class="text-3xl font-bold text-white mb-8">Add labels</h1>
/label add PROJ-123 priority/P0 type/SECURITY
<h1 class="text-3xl font-bold text-white mb-8">Remove label</h1>
/label remove PROJ-123 priority/P2
<h1 class="text-3xl font-bold text-white mb-8">Replace label (within category)</h1>
/label replace PROJ-123 status/IN_PROGRESS
<h1 class="text-3xl font-bold text-white mb-8">View labels</h1>
/label show PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Suggest labels (AI analyzes story and suggests)</h1>
/label suggest PROJ-123

Example:

/label suggest PROJ-123
Analyzing story PROJ-123: "Implement user authentication with OAuth2"
Suggested labels:
  ✓ priority/P1      (security-related, high business value)
  ✓ type/FEATURE     (new functionality)
  ✓ circle/2-DEV     (development work)
  ✓ platform/API     (backend endpoint)
  ✓ platform/WEB     (frontend integration)
  ✓ complexity/OCTAHEDRON (8 pts - OAuth integration complexity)
Apply these labels? [Y/n]

/filter

Purpose: Filter and list stories by labels.

<h1 class="text-3xl font-bold text-white mb-8">Find all P0 bugs</h1>
/filter priority/P0 type/BUG
<h1 class="text-3xl font-bold text-white mb-8">Find blocked items for iOS</h1>
/filter status/BLOCKED platform/IOS
<h1 class="text-3xl font-bold text-white mb-8">Complex filter</h1>
/filter "priority/P0 OR priority/P1" status/IN_PROGRESS circle/2-DEV
<h1 class="text-3xl font-bold text-white mb-8">Output as list</h1>
/filter status/QA_READY --format=list

/bulk-label

Purpose: Apply labels to multiple stories.

<h1 class="text-3xl font-bold text-white mb-8">Add sprint label to all ready stories</h1>
/bulk-label --filter="status/READY" --add="sprint/SPRINT-04"
<h1 class="text-3xl font-bold text-white mb-8">Move all security to P0</h1>
/bulk-label --filter="type/SECURITY" --replace="priority/P0"

Sprint Commands

/sprint

Purpose: Sprint management.

<h1 class="text-3xl font-bold text-white mb-8">Create new sprint</h1>
/sprint create SPRINT-04 --start="2025-01-15" --end="2025-01-28"
<h1 class="text-3xl font-bold text-white mb-8">View sprint</h1>
/sprint view SPRINT-04
<h1 class="text-3xl font-bold text-white mb-8">Add stories to sprint</h1>
/sprint add SPRINT-04 PROJ-123 PROJ-124 PROJ-125
<h1 class="text-3xl font-bold text-white mb-8">Sprint report</h1>
/sprint report SPRINT-04
<h1 class="text-3xl font-bold text-white mb-8">Sprint velocity</h1>
/sprint velocity SPRINT-04

Example:

/sprint view SPRINT-04

┌──────────────────────────────────────────────────────────────────────┐ │ SPRINT-04: Jan 15 - Jan 28, 2025 │ ├──────────────────────────────────────────────────────────────────────┤ │ │ │ Capacity: 120 points Committed: 98 points Done: 42 points │ │ │ │ Progress: [████████████░░░░░░░░░░░░░░░░░░] 43% │ │ │ │ Status Breakdown: │ │ ┌────────────────┬─────────┬────────┐ │ │ │ Status │ Count │ Points │ │ │ ├────────────────┼─────────┼────────┤ │ │ │ DONE │ 7 │ 42 │ │ │ │ IN_PROGRESS │ 5 │ 34 │ │ │ │ BLOCKED │ 2 │ 12 │ ⚠ Needs attention │ │ │ READY │ 2 │ 10 │ │ │ └────────────────┴─────────┴────────┘ │ │ │ │ Blockers: │ │ • PROJ-156: Waiting for API from vendor │ │ • PROJ-162: Security review pending │ │ │ └──────────────────────────────────────────────────────────────────────┘

/plan

Purpose: Sprint planning assistance.

<h1 class="text-3xl font-bold text-white mb-8">AI-assisted sprint planning</h1>
/plan SPRINT-05 --capacity=120
<h1 class="text-3xl font-bold text-white mb-8">Plan from backlog</h1>
/plan SPRINT-05 --from-backlog --priority=P0,P1

/velocity

Purpose: Team velocity metrics.

<h1 class="text-3xl font-bold text-white mb-8">Last 5 sprints velocity</h1>
/velocity --sprints=5
<h1 class="text-3xl font-bold text-white mb-8">By team</h1>
/velocity --team=dev-ui
<h1 class="text-3xl font-bold text-white mb-8">Trend analysis</h1>
/velocity --trend

Context Commands

/context

Purpose: Manage project context for agents.

<h1 class="text-3xl font-bold text-white mb-8">Set project context</h1>
/context set @project_xyz
<h1 class="text-3xl font-bold text-white mb-8">View current context</h1>
/context show
<h1 class="text-3xl font-bold text-white mb-8">Add context file</h1>
/context add ./requirements.md
<h1 class="text-3xl font-bold text-white mb-8">Clear context</h1>
/context clear

Example:

/context show Current Context: @globalretail ─────────────────────────────── Loaded files: • README.md (project overview) • tech_stack.yaml (Java/Oracle/Vertica/React) • architecture.md (system diagrams) • api_standards.md (REST conventions) • domain_glossary.md (business terms)

Active stories in context: 47 Sprint: SPRINT-04

/project

Purpose: Project-level commands.

<h1 class="text-3xl font-bold text-white mb-8">Switch project</h1>
/project switch PROJ
<h1 class="text-3xl font-bold text-white mb-8">Project overview</h1>
/project overview
<h1 class="text-3xl font-bold text-white mb-8">Project health</h1>
/project health

/history

Purpose: View agent invocation history.

<h1 class="text-3xl font-bold text-white mb-8">Recent activity</h1>
/history
<h1 class="text-3xl font-bold text-white mb-8">For specific story</h1>
/history PROJ-123
<h1 class="text-3xl font-bold text-white mb-8">Filter by agent</h1>
/history --agent=story-agent --limit=10

Configuration

Where Commands Are Defined

<h1 class="text-3xl font-bold text-white mb-8">.quad/commands.yaml (in your project)</h1> commands: # Custom command for this project expand-story: alias: [es, expand] # Short forms agent: story-agent defaults: --format: standard --output: jira permissions: circles: [1, 2] # Management, Development

# Override default behavior estimate: pipeline: estimation defaults: --detailed: true # Always show details

Registering Custom Commands

<h1 class="text-3xl font-bold text-white mb-8">Add project-specific command</h1> custom_commands: # Deploy to GlobalRetail staging deploy-staging: description: "Deploy to GlobalRetail staging environment" agent: deploy-agent-staging requires_approval: true allowed_users: [devops-team]

# Run legacy system analysis analyze-cobol: description: "Analyze COBOL batch job" pipeline: cobol-analysis defaults: --include-dependencies: true

Quick Reference Card

┌──────────────────────────────────────────────────────────────────────┐
│                    QUAD COMMANDS QUICK REFERENCE                     │
├──────────────────────────────────────────────────────────────────────┤
│                                                                      │
│  STORY                            ESTIMATION                         │
│  ─────                            ──────────                         │
│  /expand-story PROJ-123           /estimate PROJ-123                 │
│  /split-story PROJ-123            /complexity PROJ-123               │
│  /refine-story PROJ-123                                              │
│  /merge-stories PROJ-1 PROJ-2                                        │
│                                                                      │
│  PIPELINE                         AGENT                              │
│  ────────                         ─────                              │
│  /pipeline estimation --story=X   /agent invoke NAME --args          │
│  /pipeline development --story=X  /agent list                        │
│  /run estimation PROJ-123         /invoke story-agent PROJ-123       │
│                                                                      │
│  LABELS                           SPRINT                             │
│  ──────                           ──────                             │
│  /label add PROJ-123 priority/P0  /sprint create SPRINT-04           │
│  /label suggest PROJ-123          /sprint view SPRINT-04             │
│  /filter status/BLOCKED           /sprint add SPRINT-04 PROJ-123     │
│  /bulk-label --filter=X --add=Y   /velocity --sprints=5              │
│                                                                      │
│  CONTEXT                          CONFIG                             │
│  ───────                          ──────                             │
│  /context set @project_xyz        /config show                       │
│  /context show                    /audit --story=PROJ-123            │
│  /project switch PROJ                                                │
│                                                                      │
└──────────────────────────────────────────────────────────────────────┘

QUAD Slash Commands

Custom Commands for QUAD Methodology

Table of Contents

Overview

What Are QUAD Commands?

Command Prefix

Command Categories

Story Commands

/expand-story

/split-story

/refine-story

/merge-stories

Estimation Commands

/estimate

/complexity

Pipeline Commands

/pipeline

/run

Agent Commands

/agent

/invoke

Label Commands

/label

/filter

/bulk-label

Sprint Commands

/sprint

/plan

/velocity

Context Commands

/context

/project

/history

Configuration

Where Commands Are Defined

Registering Custom Commands

Quick Reference Card