<objective>

Display the complete DOG command and skill reference.

Output ONLY the reference content below. Do NOT add:

• Project-specific analysis
• Git status or file context
• Next-step suggestions
• Any commentary beyond the reference

</objective> <reference>

DOG Command Reference

DOG (Delegated Orchestration for Git-based projects) enables hierarchical project planning with multi-agent task execution.

Quick Start

1. /dog:new-project - Initialize project with PROJECT.md and ROADMAP.md
2. /dog:add-major-version - Create first major version structure
3. /dog:add-task 1.0 - Add tasks to minor version 1.0
4. /dog:execute-task - Execute the next available task

Hierarchy Structure

MAJOR -> MINOR -> TASK

.claude/dog/
├── PROJECT.md                    # Project overview
├── ROADMAP.md                    # Version summaries
├── dog-config.json               # Configuration
└── major/{n}/
    ├── STATE.md                  # Major version state
    ├── PLAN.md                   # Business-level plan
    ├── CHANGELOG.md              # Major changelog
    └── minor/{m}/
        ├── STATE.md              # Minor version state
        ├── PLAN.md               # Feature-level plan
        ├── CHANGELOG.md          # Minor changelog
        └── task/{name}/
            ├── STATE.md          # Task state
            ├── PLAN.md           # Technical-level plan
            └── CHANGELOG.md      # Task changelog

Core Commands

Project Initialization

/dog:new-project Initialize a new DOG project.

• Creates PROJECT.md, ROADMAP.md, dog-config.json
• Asks for workflow mode (Interactive/YOLO)
• Deep questioning to gather project context

/dog:existing-project Add DOG structure to an existing codebase.

• Detects existing code patterns
• Infers current state as validated requirements
• Creates planning structure reflecting existing work

Task Execution

/dog:execute-task [major.minor/task-name] Execute the next available task.

• Creates worktree and task branch
• Spawns subagent for execution
• Monitors token usage
• Runs approval gate (interactive mode)
• Squashes commits by type
• Merges to main
• Cleans up worktrees

Status

/dog:status Show complete hierarchy status.

• Visual tree of all versions and tasks
• Progress bar and percentages
• Current position highlighted
• Blocked tasks explained
• Next action suggested

Adding Structure

/dog:add-task [major.minor] Add a task to a minor version.

• Discussion workflow generates PLAN.md
• Validates task name (lowercase, hyphens, max 50 chars)
• Checks uniqueness within minor version

/dog:add-minor-version [major] Add a minor version to a major.

• Creates directory structure
• Updates ROADMAP.md

/dog:add-major-version Add a new major version.

• Deep questioning for vision and scope
• Creates major with initial minor (X.0)
• Updates ROADMAP.md

Removing Structure

/dog:remove-task [major.minor/task-name] Remove a task.

• Validates no work in progress
• Checks for dependent tasks
• Confirms with user

/dog:remove-minor-version [major.minor] Remove a minor version.

• Validates no incomplete tasks
• Warns about implicit dependencies
• Confirms with user

/dog:remove-major-version [major] Remove an entire major version.

• Validates no incomplete work
• Extra confirmation required
• Provides git recovery instructions

DOG-Specific Skills

Skill	Description
/dog:spawn-subagent	Launch subagent with task context and token tracking
/dog:monitor-subagents	Check status of running subagents
/dog:collect-results	Gather results from completed subagents
/dog:merge-subagent	Merge subagent branch into task branch
/dog:token-report	Generate token usage report
/dog:decompose-task	Split oversized task into smaller tasks
/dog:learn-from-mistakes	Analyze mistakes with conversation length as factor
/dog:parallel-execute	Orchestrate multiple subagents concurrently

Workflow Modes

Set during /dog:new-project in dog-config.json:

Interactive Mode (default)

• Approval gates at task completion
• User confirms before merge to main
• Pauses for review opportunities

YOLO Mode

• Skips approval gates
• Auto-merges on task completion
• Continuous execution

Change anytime by editing .claude/dog/dog-config.json

Task Naming Rules

• Lowercase letters and hyphens only
• Maximum 50 characters
• Must be unique within minor version

Valid: parse-tokens, fix-memory-leak, add-user-auth Invalid: Parse_Tokens, fix memory leak, add-very-long-task-name-that-exceeds-limit

Branch Naming

Type	Pattern	Example
Task	{major}.{minor}-{task-name}	1.0-parse-tokens
Subagent	{major}.{minor}-{task-name}-sub-{uuid}	1.0-parse-tokens-sub-a1b2c3

Common Workflows

Starting a new project:

/dog:new-project
/dog:add-major-version
/dog:add-task 1.0
/dog:execute-task

Checking progress:

/dog:status

Adding more work:

/dog:add-task 1.0          # Add to existing minor
/dog:add-minor-version 1   # Add new minor to major
/dog:add-major-version     # Add new major version

Removing planned work:

/dog:remove-task 1.0/task-name
/dog:remove-minor-version 1.0
/dog:remove-major-version 1

Configuration Options

dog-config.json:

{
  "yoloMode": false,           // Skip approval gates
  "contextLimit": 200000,      // Total context window
  "targetContextUsage": 0.4,   // Soft limit (40%)
  "autoCleanupWorktrees": true // Clean after merge
}

Getting Help

• Read .claude/dog/PROJECT.md for project vision
• Check .claude/dog/ROADMAP.md for version overview
• Use /dog:status to see current state
• Review individual STATE.md files for detailed progress

</reference>