skills/product/strategy/SKILL.md
Strategic business analysis for technical investments. Evaluates ROI, value proposition, competitive positioning, and market alignment. Provides decision support with business justification. Use when: building a business case for a technical investment, evaluating ROI or value proposition, or doing competitive positioning analysis.
npx skillsauth add mikeparcewski/wicked-garden wicked-garden-product-strategyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Multi-perspective business analysis to guide technical investment decisions.
/wicked-garden:product:strategy)Best for: Major investments, strategic decisions, go/no-go evaluations
Best for: Budget justification, fast approvals, comparative costs
Best for: Product positioning, feature prioritization, marketing alignment
Questions to Answer:
Output: Impact score (HIGH/MEDIUM/LOW) with justification
Financial Model:
ROI = (Benefits - Costs) / Costs × 100%
Payback Period = Investment / Annual Benefit
Costs Include:
Benefits Include:
Framework: Jobs-to-be-Done
Differentiation:
5 Forces Analysis:
SWOT:
Market Assessment:
| Score | Confidence | Recommendation | |-------|-----------|----------------| | APPROVE | HIGH | Strong business case, proceed | | APPROVE | MEDIUM | Solid case with caveats, proceed with monitoring | | CONDITIONAL | MEDIUM | Viable if conditions met, address concerns first | | REJECT | HIGH | Weak case, recommend alternative | | REJECT | MEDIUM | Insufficient evidence, gather more data |
Store strategic insights:
Skill(skill="wicked-brain:memory", args="store \"ROI analysis: {project}\" --type decision")
Recall past analysis:
Skill(skill="wicked-brain:memory", args="recall \"strategic analysis {domain}\"")
Called during clarify phase for value assessment:
Attach analysis as evidence by appending to the task description:
TaskUpdate(taskId={task_id}, description="{previous}\n\n## Strategy Analysis\n{analysis_summary}")
## Strategic Analysis: {Project}
### Decision: APPROVE | CONDITIONAL | REJECT
**Confidence**: HIGH | MEDIUM | LOW
### Executive Summary
{3-5 sentence business case}
### ROI Analysis
- **Investment**: ${cost}
- **Annual Benefit**: ${benefit}
- **ROI**: {percentage}
- **Payback Period**: {months}
### Value Proposition
{Why this matters to customers/stakeholders}
### Competitive Position
{How this compares to alternatives}
### Risks & Mitigation
| Risk | Impact | Mitigation |
|------|--------|------------|
### Recommendation
{Action items with priorities}
Discover available analytics/market integrations via capability detection. Fall back to qualitative analysis when no data sources available.
development
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.
tools
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.
development
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).
tools
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).