Do Issue

A progressive workflow for implementing issues from the detected git platform (GitHub, GitLab, or Bitbucket), following the attune pattern: analyze → specify → plan → implement → validate → complete

Invoke Skill(sanctum:do-issue), which carries the six-step workflow, the task planning, the parallel execution, the quality gates and the completion steps. The arguments, step-skipping rules and War Room gate below are applied by this command.

When To Use

Use this command when you need to:

• Implementing fixes for one or more issues (GitHub, GitLab, or Bitbucket)
• Progressive issue resolution with validation
• Addressing a particular issue or ticket that is referenced

When NOT To Use

• Simple changes that don't need the full workflow
• Work already completed through another sanctum command

Quick Reference

/do-issue 42                  # Full workflow for issue #42
/do-issue 42 --from plan      # Skip analysis/specify, start at planning
/do-issue 42 --to plan        # Stop after planning (dry run)
/do-issue 42 --scope minor    # Auto-skip steps for minor fixes
/do-issue 42 43 44            # Multiple issues with dependency analysis

Intelligent Step-Skipping

The workflow auto-detects scope and suggests step-skipping:

Minor scope (typo fix, config change):

• Skip: Analyze, Specify, Plan
• Run: Implement → Validate → Complete

Medium scope (single feature, clear requirements):

• Skip: Specify (if criteria clear)
• Run: Analyze → Plan → Implement → Validate → Complete

Major scope (multi-file, complex requirements):

• Run all steps

# Detect scope automatically
/do-issue 42 --scope auto

# Override with explicit scope
/do-issue 42 --scope minor
/do-issue 42 --scope medium
/do-issue 42 --scope major

War Room Checkpoint (Automatic)

Purpose: Assess whether complex multi-issue work warrants expert deliberation.

Auto-triggers when (moderate approach):

• 3+ issues being implemented, OR
• Dependency conflicts detected between issues, OR
• Overlapping file changes identified (same files in multiple issues), OR
• Single issue touches critical modules (auth, database schema, API contracts)

Checkpoint invocation (automatic, no user action needed):

Skill(attune:war-room-checkpoint) with context:
  source_command: "do-issue"
  decision_needed: "Execution strategy for issues #42, #43, #44"
  issues_involved: [42, 43, 44]
  files_affected: [list of overlapping files]
  conflict_description: "Issues #42 and #44 both modify auth middleware"
  profile: [from user settings, default: "default"]

Response handling:

Auto-continue logic:

• If War Room confidence > 0.8: Orders applied automatically
• If confidence <= 0.8: User prompted to confirm approach

Example checkpoint output:

War Room Checkpoint: /do-issue
────────────────────────────────
Decision: Execution strategy for issues #42, #43, #44

Assessment:
  RS: 0.52 (Type 1B - Heavy Door)
  Mode: Lightweight (3 experts)
  Confidence: 0.87

Recommendation:
  1. Implement #42 first (establishes auth base)
  2. Then #43 in parallel (independent parser fix)
  3. Defer #44 to separate PR (scope creep detected)

Rationale: Issues #42 and #44 both touch auth module.
Combining risks merge conflicts and unclear rollback.

[Auto-continuing with War Room orders...]

Skip conditions (checkpoint not invoked):

• Single issue with scope=minor
• --skip-war-room flag (escape hatch)
• All issues are clearly independent (no shared files, no dependency chain)

Step 3 Output: Task breakdown with dependencies (War Room-validated if triggered)

Options Reference

Multiple Issues

When implementing multiple issues:

/do-issue 42 43 44

The workflow:

1. Analyzes all issues in parallel
2. Detects dependencies between issues
3. Plans execution order:

• Independent issues run in parallel
• Dependent issues run sequentially

1. Executes with code review between batches
2. Creates single PR (or multiple if needed)

Execution Mode for Batch Processing

When processing multiple issues, especially with --dangerous flag: