/blockers - Blocked Task Surface

Surface all blocked tasks across project plans with blocker details and suggested resolutions.

System Prompt

EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. Scan project plans for blocked tasks (⏸️, BLOCKED, waiting)
2. Query context database for blocker records
3. Analyze dependencies and identify unblock paths
4. Present blocked items with resolution suggestions

---

Usage

/blockers [options]

Examples

# Show all blockers
/blockers

# Filter by track
/blockers --track A

# Show with resolution suggestions
/blockers --suggest

# Show blockers from specific plan
/blockers --plan "PILOT-PARALLEL-EXECUTION-PLAN.md"

# Show critical blockers only
/blockers --critical

# Export blockers report
/blockers --export blockers-report.md

What It Does

1. Scan Project Plans - Search for tasks marked blocked/waiting
2. Query Context DB - Find blocker records via /cxq
3. Check Dependencies - Identify what's blocking what
4. Analyze Root Causes - Determine underlying blockers
5. Suggest Resolutions - Provide actionable unblock steps

Blocker Detection Patterns

Pattern	Meaning
⏸️	Paused/blocked emoji
BLOCKED	Explicit blocked status
waiting on	Dependency waiting
depends on	Has upstream dependency
blocked by	Explicit blocker reference
needs	Missing requirement

Output Format

## 🚫 Blocked Tasks (3 found)

### Critical (1)
1. **Track C.2: Deploy to production**
   - Status: ⏸️ BLOCKED
   - Blocker: Waiting on security review (D.1)
   - Duration: 3 days blocked
   - Resolution: Complete security checklist items 4-7

### High Priority (1)
2. **Track A.5: API integration tests**
   - Status: waiting on staging environment
   - Blocker: DevOps Track C.1 not complete
   - Duration: 1 day blocked
   - Resolution: Use mock server for now, revisit after C.1

### Normal (1)
3. **Track F.3: User documentation**
   - Status: needs final UI screenshots
   - Blocker: UI changes still in progress (B.4)
   - Duration: 2 days blocked
   - Resolution: Document current UI, update screenshots later

Options

Option	Description
--track LETTER	Filter by track (A, B, C, etc.)
--critical	Show only critical blockers
--suggest	Include resolution suggestions
--plan FILE	Scan specific plan file
--export FILE	Export report to markdown file
--json	Output as JSON for scripting

Blocker Priority Levels

Level	Criteria
Critical	Blocks multiple tracks or release
High	Blocks key deliverable
Normal	Blocks single task
Low	Nice-to-have dependency

Integration

Works with:

• /work-next - Excludes blocked tasks from recommendations
• /momentum - Shows blockers affecting hot areas
• /handoff - Includes blockers in handoff documentation
• /cxq - Queries blocker context

Related Commands

Command	Relationship
/work-next	Uses blocker info for recommendations
/momentum	Shows blockers in active areas
/handoff	Includes blockers in documentation
/cxq	Query blocker records

Success Output

When blocker analysis completes:

✅ COMMAND COMPLETE: /blockers
Blockers found: N total
Critical: X | High: Y | Normal: Z
Suggestions: M resolution options

Completion Checklist

Before marking complete:

• Plan file scanned
• Blockers identified and categorized
• Suggestions generated (if --suggest)
• Report displayed

Failure Indicators

This command has FAILED if:

• ❌ No project plan found
• ❌ Plan file not readable
• ❌ Invalid track specified
• ❌ Context database unavailable

When NOT to Use

Do NOT use when:

• No active project plan exists
• Looking for general issues (not blockers)
• Need full project status (use /pilot instead)

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Ignore critical blockers	Project stalls	Address critical first
Skip --suggest	Miss solutions	Include resolution options
Don't update plan	Stale blocker data	Update after resolution

Principles

This command embodies:

• #9 Based on Facts - Analyzes actual plan data
• #5 No Assumptions - Reports what's documented
• #6 Clear, Understandable - Categorized by priority

Full Standard: CODITECT-STANDARD-AUTOMATION.md

---

Version: 1.0.0 Created: 2026-01-03 Author: CODITECT Team