mikeparcewski/workflow
skills/crew/workflow/SKILL.md
Core wicked-crew v3 workflow engine with capability-based orchestration and phase progression. Drives projects through crew phases: clarify → design → test-strategy → build → test → review. Smart decisioning analyzes signals to determine which specialists to engage per phase. Use when: "crew phases", "phase plan", "workflow execution", "start a project", "clarify outcome", "design phase", "build phase", "approve phase", "crew workflow", "phase progression", "QE gate", "shift-left testing", or structured delivery guidance.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 16, 2026, 5:58 AM6.3s8 files scanned
SKILL.md
- name:
- workflow
- description:
- |
- Drives projects through crew phases:
- clarify → design → test-strategy → build → test → review.
- Use when:
- crew phases", "phase plan", "workflow execution", "start a project",
- disable-model-invocation:
- true
- # TODO (Issue #332):
- When Claude Code supports `context: "fork"` in skill frontmatter,
- # add `context:
- fork` here to run crew workflow in a forked context. This would prevent
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 advancementvalid_skip_reasons: enumerated skip reasons; free-text rejectedskip_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
Related Skills
mikeparcewski/wicked-garden-engineering-conformance-reviewer
development
VerifiedTrustedCommunity
Pattern-conformance agent-half: evaluates a produced artifact or diff against a set of architectural/design pattern rules from the conformance-rule store (wicked_governance schema). Returns structured findings with rule ID, severity, and rationale — the deterministic half (mechanical rule recall) is done by the guard pipeline; this is the semantic evaluation step. Triggered by: the guard_pipeline `outgov_pattern` check (session-close), or explicitly by an engineering review when WICKED_OUTGOV_RULES_DIR is populated. NOT a replacement for the full `engineering` review skill — focuses only on conformance to stored Pattern rules; architecture and code-quality checks live in the `engineering` skill. Semantic evaluation reuses `wicked-garden-qe-semantic-reviewer` as the designated agent-half evaluator (per garden#983 spec). This skill is the orchestrating wrapper that loads applicable Pattern rules and delegates the per-rule semantic judgment to qe-semantic-reviewer.
8SKILL.mdUpdated Jul 22, 2026
mikeparcewski/wicked-garden-domain
tools
VerifiedTrustedCommunity
The FOUNDATIONAL domain-model capability: extract a codebase's domain — testable business rules (with confidence + provenance), entities, requirements — as a schema-conformant model on the estate graph. The workers annotate the store; wicked-core reads it and builds the requirements graph, coverage-gating fail-closed. Steers three fork workers. A shared substrate, not a modernization tool. The `modernize` archetype DERIVES from it; build / migrate / review / specify / explore consume the SAME domain model — none OWN it. Understanding a codebase's domain is upstream of almost everything else garden does. Use when: "extract the business rules / domain model from this codebase", "build a requirements graph from the code", "what does this system actually require", "reverse-engineer the domain before we build/port/migrate". Works on ANY codebase (modern or legacy) — the value is the domain model, not the porting. NOT the code transform itself (that is the archetype consuming this model). This skill produces the DOMAIN MODEL, not new code.
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-modeler
development
VerifiedTrustedCommunity
Domain-graph fork worker for the modernize archetype. Groups the estate's Louvain communities into business domains, attaches each requirement to its cluster (advisory cluster_id provenance), and invokes wicked-core's domain-graph build (which reads the annotated estate store, recomputes coverage fail-closed, and builds the requirements graph) — then validates core's output against the vendored schema. Use when: dispatched by wicked-garden-domain after rule extraction to turn a flat rule set into cluster-keyed domains; "group these into domains", "build the requirements graph", "translate clusters into a domain model". NOT for mining the rules themselves (that is domain-extractor) or threat-modeling (that is domain-coverage).
8SKILL.mdUpdated Jul 15, 2026
mikeparcewski/wicked-garden-domain-extractor
tools
VerifiedTrustedCommunity
Rule-extraction fork worker for the FOUNDATIONAL domain-model capability. Mines testable business rules from a codebase — each with a numeric confidence and a provenance{source, ref, source_kinds} — and annotates them into the estate store so wicked-core can build the domain-model requirements graph (coverage-gated). This is a substrate, not a modernization tool: the `modernize` archetype DERIVES from it, and build / migrate / review / specify / explore can consume the same domain model — none OWN it. Use when: dispatched by wicked-garden-domain to mine the business_rules of a codebase (or a module); "extract the domain rules", "what does this system require", building the requirements half of a domain model. NOT for grouping into domains (that is domain-modeler) or judging coverage (that is domain-coverage — a seat-distinct evaluator).
8SKILL.mdUpdated Jul 15, 2026