mikeparcewski/skills/workflow
skills/workflow/SKILL.md
--- name: workflow description: | Reference for how the wicked-crew workflow engine operates — phase catalog, gate enforcement, rigor tiers, and facilitator rubric. Use when understanding or troubleshooting crew phase mechanics (gate config, CONDITIONAL resolution, phase dependencies). NOT for starting a project (use crew:start) or proposing a process plan (use propose-process). context: fork **Plain:** wicked-crew v6 — propose-process rubric picks phases and rigor tier; gates are hard
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden skills/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: May 8, 2026, 5:56 AM194.9s8 files scanned
SKILL.md
- name:
- workflow
- description:
- |
- NOT for starting a project (use crew:
- start) or proposing a process plan (use propose-process).
- context:
- fork
- **Plain:
- ** wicked-crew v6 — propose-process rubric picks phases and rigor tier;
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Workflow Skill (v6)
Facilitator-rubric orchestration with hard quality gates.
Decision Engine — wicked-garden:propose-process
User project description
│
▼
propose-process facilitator
├── Score 9 risk factors (0-3 each)
├── Read agents/**/*.md frontmatter → pick specialists
├── Pick phases from phases.json catalog
├── Set rigor_tier (minimal / standard / full)
└── Emit process-plan.md + full task chain
All phase selection is judgment-driven by the facilitator, not rule-based.
Interaction Modes
| Mode | How | Effect |
|------|-----|--------|
| normal | Default | Each phase gate requires explicit user approval before advancing |
| yolo | /wicked-garden:crew:auto-approve | Auto-advance through gates; gates still run, findings still logged |
Rigor Tiers
| Tier | Complexity | Gates | Reviewers | |------|-----------|-------|-----------| | minimal | 0-2 | Advisory — gate findings logged but do not block | Single reviewer | | standard | 3-5 | Enforced — REJECT blocks advancement | Single reviewer | | full | 6-7 | Enforced — REJECT blocks; multi-reviewer | 2+ reviewers |
Security or compliance signals override to full regardless of complexity.
Phase Plan
clarify → design → [challenge?] → [test-strategy?] → build → test → review
Brackets = optional phases. The facilitator picks which phases apply based on
factor readings. phases.json defines gate config per phase (min_gate_score,
valid_skip_reasons, depends_on).
Phase Summary
| Phase | Goal | Key deliverable | |-------|------|-----------------| | clarify | Define success criteria | Outcome statement + success criteria | | design | Architect solution | Architecture docs + approach | | challenge | Adversarial stress-test | Challenge findings + revised design | | test-strategy | Define test approach pre-build | Test scenarios + risk assessment | | build | Implement | Working implementation | | test | Verify | Test results + convergence evidence | | review | Multi-perspective validation | Review findings + sign-off |
Gate Enforcement (v2.5.0+)
Gates are hard enforcement — not advisory — at standard and full rigor.
| Verdict | Effect |
|---------|--------|
| APPROVE | Phase advances |
| CONDITIONAL | conditions-manifest.json written; verify before next phase |
| REJECT | Blocks advancement; mandatory rework |
CONDITIONAL auto-resolution (AC-4.4): spec gap conditions → fixed inline. Intent-changing conditions → escalate to user or council.
Gate reviewer assignment happens at approve time, not at phase start. Banned
reviewer values: just-finish-auto, fast-pass, auto-approve-*.
Build depends on design (depends_on: ["clarify", "design"]). To migrate
legacy beta.3 projects: the adopt-legacy migration guide was removed in v9 — v6 is the baseline.
Specialist Discovery
Crew discovers specialists by reading agents/**/*.md frontmatter directly at
runtime. No static enhances map. Fallback agents (facilitator, researcher,
implementer, reviewer) handle phases when no specialist matches.
Convergence Tracking (build/test phases)
Artifact states: Designed → Built → Wired → Tested → Integrated → Verified.
The convergence-verify gate flips REJECT → APPROVE only when every tracked
artifact reaches Integrated. Stalls at threshold 3 sessions surface as findings.
Commands Reference
| Command | Purpose |
|---------|---------|
| /wicked-garden:crew:start | Begin project — invokes propose-process |
| /wicked-garden:crew:status | View current phase and engaged specialists |
| /wicked-garden:crew:execute | Run current phase |
| /wicked-garden:crew:approve | Advance phase after gate |
| /wicked-garden:crew:just-finish | Autonomous completion (yolo-equivalent) |
| /wicked-garden:crew:gate | Run a specific quality gate |
| /wicked-garden:crew:evidence | Query evidence for a task |
| /wicked-garden:crew:auto-approve | Switch to auto-advance mode |
Storage
| Store | What |
|-------|------|
| Native tasks | TaskCreate/TaskUpdate with validated metadata (see scripts/_event_schema.py) |
| wicked-brain:memory | Cross-session learning at project completion and gate failures |
| Local JSON | DomainStore fallback; always available |
Refs (load on demand)
- Evidence Tracking — evidence tiers L1-L4, artifact naming
- Integration Details — mem, search, wicked-bus usage
- Scoring Rubric — HISTORICAL v5 only; see propose-process for v6
- Risk Dimension Signals — signal keywords per factor
Related Skills
mikeparcewski/skills/engineering/large-scale-migration
development
VerifiedTrustedCommunity
--- name: large-scale-migration description: How to execute a LARGE MECHANICAL change across any codebase with LEVERAGE instead of an agent-grind or hand-edits — a cross-cutting migration, refactor, rename, dialect/framework/DB port, library adoption, or bulk transform. The map→transform→gate pattern: a deterministic transform driven by a source-of-truth map, proven by a differential-equivalence gate. Use when the work is "migrate all X to Y", "rename Z everywhere", "port to a new DB/dialect/fra
8SKILL.mdUpdated Jun 3, 2026
mikeparcewski/wicked-garden:classify
testing
VerifiedTrustedCommunity
v11 LLM-based work-shape classifier. Replaces the regex archetype detector with the model's own reasoning. Reads the user's prompt, picks the right archetype(s) from the catalog, identifies signals (blast_radius, novelty, reversibility, etc.), and persists to SessionState so subsequent turns steer correctly. Use when: the prompt_submit hook emitted a `<wg classify-due />` directive, OR explicitly invoked at session start, OR when re-classifying after the user changes scope mid-session.
8SKILL.mdUpdated May 26, 2026
mikeparcewski/wicked-garden:archetype
tools
VerifiedTrustedCommunity
v11 work-shape archetype runner. When a prompt has been routed to one of the 9 archetypes (triage, explore, specify, decide, ship, review, incident, build, migrate), this skill is the entry point. It picks the right per-archetype playbook from refs/ and executes the phase shape declared in `.claude-plugin/archetypes.json`. Use when: a `<wg archetype="X">` or `<wg archetypes>` system-reminder tag appears, an explicit "let's run the X archetype" request, or when one of the per-archetype slash commands resolves to this skill.
8SKILL.mdUpdated May 8, 2026
mikeparcewski/intent
development
VerifiedTrustedCommunity
Show or set the session intent variable. Intent gates how loud the framework is — simple-edit (silent), feature/research (synthesis directive), rigor (full crew context). Auto-detected on turn 1; this skill overrides explicitly. Sticky for the session. Use when: "set intent", "intent override", "/wicked-garden:intent", "make the framework quiet", "force rigor", "what's my intent".
8SKILL.mdUpdated May 6, 2026