mikeparcewski/workflow

Workflow Skill (v3)

Capability-based orchestration with smart specialist engagement.

v3 Architecture

User Input → Smart Decisioning → Specialist Discovery → Engagement
                  │                     │
                  ├── Signal Detection  ├── Available specialists
                  ├── Complexity Score  ├── Personas
                  └── Ambiguity Check   └── Fallback agents

Phase Progression

clarify → design → test-strategy → build → test → review

Each phase has: Clear deliverables, specialist engagement based on signals, mandatory quality gate.

Gate Enforcement (v2.5.0+)

Gates are hard enforcement — not advisory. phases.json defines per-phase:

• min_gate_score (0.6-0.8): gates below threshold block advancement
• valid_skip_reasons: enumerated skip reasons; free-text rejected
• skip_complexity_threshold: prevents skipping at high complexity (e.g., test-strategy at >= 3)

Gate verdicts: APPROVE → proceed. CONDITIONAL → conditions-manifest.json written, must verify before next phase. REJECT → blocks advancement, mandatory rework.

CONDITIONAL auto-resolution (AC-4.4): spec gaps fixed inline; intent changes escalate to user/council.

Build depends on design (depends_on: ["clarify", "design"]). Rollback: CREW_GATE_ENFORCEMENT=legacy.

Smart Decisioning

Signal Categories

| Signal | Keywords | Specialists | |--------|----------|-------------| | Security | auth, encrypt, token, jwt | platform, compliance | | Performance | scale, optimize, cache | engineering, qe | | Product | user, feature, story | product | | Compliance | SOC2, HIPAA, audit | platform | | Ambiguity | maybe, should we, options | jam | | Complexity | integration, migrate, refactor | delivery, engineering |

Complexity Scoring (0-7)

• 0-2: Simple → Built-in agents only
• 3-4: Moderate → Core specialists
• 5-7: Complex → All relevant + delivery

Specialist Engagement

Discovery

Crew discovers specialists via specialist.json in each plugin.

Fallback Agents

| Specialist | Fallback | |------------|----------| | jam | facilitator | | qe, product | reviewer | | engineering (arch) | researcher | | engineering, platform | implementer |

Phase Details

Clarify

Goal: Define success criteria Deliverables: Outcome statement, success criteria, scope boundaries Specialists: jam (if ambiguous), product

Design

Goal: Architect the solution Deliverables: Architecture docs, pattern identification, technical approach Specialists: product, engineering

QE (Quality Engineering)

Goal: Define test strategy before building Deliverables: Test scenarios, risk assessment, edge cases Specialists: qe, platform (if security signals)

Build

Goal: Implement the solution Deliverables: Working implementation, progress tracking, tests passing Specialists: engineering, platform (if infra)

Review

Goal: Multi-perspective validation Deliverables: Review findings, recommendations, sign-off Specialists: product, qe, platform (if regulated)

Project Lifecycle

Projects can be archived when complete or paused:

sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/crew/crew.py" archive <name>      # Sets archived=true
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/crew/crew.py" unarchive <name>    # Reactivates
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/crew/crew.py" list                 # Excludes archived by default
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/crew/crew.py" list --include-archived

Phase operations are blocked on archived projects.

Commands Reference

| Command | Purpose | |---------|---------| | /wicked-garden:crew:start | Begin project with smart decisioning | | /wicked-garden:crew:status | View current state and engaged specialists | | /wicked-garden:crew:execute | Run current phase with specialists | | /wicked-garden:crew:approve | Approve and advance phase | | /wicked-garden:crew:just-finish | Autonomous completion | | /wicked-garden:crew:gate | Run QE gate (value/strategy/execution) | | /wicked-garden:crew:evidence | Query evidence for a task |

Event Flow

Project Start

crew:project:started:success
crew:specialist:engaged:success
crew:specialist:unavailable:warning (with fallback)

Phase Transitions

crew:phase:started:success
crew:phase:completed:success
crew:phase:approved:success

Utility Integration

| Plugin | Enhancement | Fallback | |--------|-------------|----------| | wicked-garden:kanban | Persistent task board | TodoWrite | | wicked-garden:mem | Cross-session learning | Project files |

See Integration Details for usage patterns.

Evidence Tracking

Gate decisions and artifacts are tracked as evidence. See Evidence Tracking for:

• Evidence tiers (L1-L4)
• Artifact naming conventions
• Automatic vs manual evidence collection

Configuration

Customize in the wicked-crew local storage domain as config.yaml:

defaults:
  always_engage: [qe]      # Always use QE specialist
  complexity_threshold: 4  # Lower = more specialists