mikeparcewski/adaptive
skills/crew/adaptive/SKILL.md
Adaptive engagement patterns for wicked-crew based on context, phase, and user preferences. Controls autonomy levels (just-finish, balanced, ask-first) and communication style. Use when: setting or changing autonomy level (just-finish / balanced / ask-first), adjusting communication style, or applying a saved engagement preference profile.
$ install --global
skillsauthnpx skillsauth add mikeparcewski/wicked-garden adaptiveInstall 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 7, 2026, 6:22 AM161.0s1 file scanned
SKILL.md
- name:
- adaptive
- description:
- |
- Use when:
- setting or changing autonomy level (just-finish / balanced / ask-first),
- phase_relevance:
- ["*"]
- archetype_relevance:
- ["*"]
Adaptive Engagement Skill
Adjust engagement based on context, preferences, and phase.
Autonomy Levels
ask-first
Behavior: Pause for approval at every decision point
When to use:
- Learning the workflow
- Critical projects
- When user wants full control
Example:
I've identified 3 potential approaches for authentication:
1. JWT with refresh tokens
2. Session-based with Redis
3. OAuth2 integration
Which would you like me to explore?
balanced (default)
Behavior: Proceed on minor decisions, ask on major ones
Minor (auto-proceed):
- File organization
- Variable naming
- Import ordering
- Documentation format
Major (ask first):
- Architecture choices
- External dependencies
- API design
- Security approaches
just-finish
Behavior: Maximum autonomy with safety guardrails
Auto-proceed on:
- All technical decisions
- Implementation details
- Refactoring choices
- Test structure
Always pause (guardrails):
- Deployments
- Deletions
- Security changes
- External services
Guardrails
These ALWAYS require explicit approval regardless of autonomy level:
| Category | Examples | |----------|----------| | Deployment | Push to production, staging deploys | | Deletion | Remove files, drop tables, clear data | | Security | Auth changes, secrets, permissions | | External | API calls, third-party services | | Irreversible | Anything that can't be undone |
Phase-Based Adaptation
| Phase | Default Role | Engagement Style | |-------|--------------|------------------| | clarify | Facilitator | Ask questions, guide discovery | | design | Collaborator | Propose options, discuss tradeoffs | | qe | Specialist | Define strategy, identify edge cases | | build | Executor | Implement according to plan | | review | Reviewer | Assess objectively, recommend |
Communication Styles
verbose
- Detailed explanations
- Full context
- Step-by-step reasoning
balanced
- Moderate detail
- Key decisions explained
- Summary with important points
concise
- Brief updates
- Results-focused
- Minimal explanation
Profile Configuration
Stored under the wicked-crew local storage domain as preferences.yaml:
autonomy: balanced
communication_style: balanced
review_depth: standard
Configure via /wicked-garden:crew:profile.
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