/validate-workflow - Validate Active Workflow

Validate that an active workflow's state is consistent, complete, and ready to continue. Auto-fixes simple issues and optionally verifies against Jira.

Usage

/validate-workflow [workflow-name] [--options]

Arguments:

• workflow-name - Specific workflow to validate (optional, auto-detects if only one active)
• --fix - Automatically apply auto-fixes without prompting
• --jira - Include Jira verification (will ask for confirmation before API calls)
• --quiet - Only show errors and warnings, hide passing checks

Examples

/validate-workflow
/validate-workflow development-EPIC-45
/validate-workflow --fix
/validate-workflow development-EPIC-45 --jira

What It Validates

Structure

• Required files exist (workflow.md, state.json, decisions.md)
• stories/ folder exists (for development workflows)
• state.json is valid JSON

State Consistency

• Current step in state.json matches workflow.md
• Workflow type matches folder naming
• Completed steps count matches checkmarks

Stories (Development Workflows)

• All stories in workflow.md have corresponding files
• Current story has required sections
• No orphaned story files

Sync Status

• Pending sync items not accumulating
• Last synced within reasonable time
• No stale unresolved blockers

Health

• Workflow recently updated (not stale)
• Not stuck on same step too long
• No repeated gate failures

Jira Verification (Optional)

• Story statuses match between local and Jira
• Offers to sync if mismatched

Output Format

Valid Workflow

## Workflow Validation: development-EPIC-45

### Structure
- workflow.md: Valid
- state.json: Valid JSON
- decisions.md: Present
- stories/: 3 files

### State Consistency
- Current Step: 3 (Implementation - TDD Green)
- Agent: Junior Developer
- Status: in_progress
- Completed: 2/9 steps

### Stories
| Story | Status | Sections |
|-------|--------|----------|
| PROJECT-123 | Complete | All present |
| PROJECT-124 | Complete | All present |
| PROJECT-125 | In Progress | Assignment, Tests, Guidance |

### Sync Status
- Pending items: 2 decisions, 0 blockers
- Last synced: 45 minutes ago

### Health
- Last updated: 12 minutes ago
- Current step iterations: 1
- Gate failures: 0

---

**Status: VALID**
Workflow is ready to continue.

With Errors

## Workflow Validation: development-EPIC-45

### Errors (2)

1. **State mismatch**
   - state.json says: Step 4 (Code Review)
   - workflow.md says: Step 3 (Implementation)
   - Manual review required - which is correct?

2. **Missing story file**
   - PROJECT-126 listed in workflow.md but no stories/PROJECT-126.md
   - **Auto-fix available:** Create from template

### Warnings (1)

1. **Stale workflow**
   - Last updated: 3 days ago

---

**Status: INVALID**
Fix 2 errors before continuing workflow.

Would you like to apply auto-fixes? [y/n]

Auto-Fix Capabilities

Issue	Auto-Fix
Missing state.json	Create from template
Missing decisions.md	Create from template
Missing stories/ folder	Create empty folder
Missing story file	Create from template
Stale last_updated	Update timestamp

Will NOT auto-fix:

• State mismatches (requires manual review)
• Delete any files
• Modify Jira

Jira Verification

When --jira is used (or you request it), the command will:

1. Ask for confirmation before making API calls
2. Compare local story statuses with Jira
3. Report any mismatches
4. Offer to sync if out of alignment

Skill Used

skills/workflow/workflow-validation/

Related Commands

• /workflow-status - View workflow progress
• /trace - Full execution trace
• /activity - Agent activity log