@rubytech/create-maxy-code 0.1.277 → 0.1.278

package/payload/premium-plugins/management-consulting/skills/operating-model-design/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: operating-model-design
+description: Translates strategy into capabilities, roles, decision rights, governance, processes, and ways of working. Use for operating model design, org design, governance, capability model, decision rights, transformation design, or execution model questions.
+---
+
+# Operating Model Design
+
+## When To Use
+
+Use this skill when a strategy is clear but the organization needs to know how work should happen. It fits transformations, growth plays, new business units, functional redesigns, and scale-up challenges.
+
+## McKinsey-Style Approach
+
+Start with the strategy and required capabilities. Then design decision rights, roles, governance, processes, metrics, and enabling systems around those capabilities.
+
+## Workflow
+
+1. Define the strategy the operating model must support.
+2. Identify required capabilities.
+3. Diagnose current operating model gaps.
+4. Design target roles, decision rights, governance, processes, and metrics.
+5. Identify transition risks and capability build needs.
+6. Recommend implementation phases.
+
+## Output Format
+
+```markdown
+# Operating Model Design
+
+## Strategic Requirement
+[What the model must enable.]
+
+## Capability Model
+| Capability | Current State | Required State | Gap |
+|---|---|---|---|
+
+## Target Model
+| Element | Recommendation | Rationale |
+|---|---|---|
+
+## Decision Rights
+| Decision | Owner | Contributors | Governance |
+|---|---|---|---|
+
+## Transition Plan
+[Phases, risks, and first moves.]
+```
+
+## Quality Bar
+
+- Link every design choice to strategy.
+- Make decision rights explicit.
+- Include governance and metrics, not only org boxes.
+- Show transition risks and sequencing.

package/payload/premium-plugins/management-consulting/skills/portfolio-review/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: portfolio-review
+description: Reviews a portfolio of markets, products, initiatives, customers, or bets and recommends allocation choices. Use for portfolio review, product portfolio, market portfolio, initiative portfolio, capital allocation, resource allocation, or "where should we invest?" questions.
+---
+
+# Portfolio Review
+
+## When To Use
+
+Use this skill when the user needs to assess a set of businesses, products, markets, initiatives, or strategic bets and decide where to invest, hold, fix, or exit.
+
+## McKinsey-Style Approach
+
+Compare portfolio elements on attractiveness, performance, strategic fit, right to win, and resource needs. Recommend allocation choices, not just rankings.
+
+## Workflow
+
+1. Define the portfolio and decision question.
+2. Select evaluation criteria.
+3. Score each portfolio element.
+4. Identify invest, maintain, fix, harvest, and exit candidates.
+5. Assess resource reallocation implications.
+6. Recommend portfolio moves and next decisions.
+
+## Output Format
+
+```markdown
+# Portfolio Review
+
+## Portfolio Scope
+[What is included and excluded.]
+
+## Evaluation Matrix
+| Item | Attractiveness | Performance | Fit | Right To Win | Recommendation |
+|---|---|---|---|---|---|
+
+## Allocation Moves
+| Move | Rationale | Resource Implication |
+|---|---|---|
+
+## Decisions Required
+1. [Decision]
+2. [Decision]
+3. [Decision]
+```
+
+## Quality Bar
+
+- Use consistent criteria across the portfolio.
+- Separate performance from attractiveness.
+- Recommend allocation actions.
+- Name the trade-offs created by reallocating resources.

package/payload/premium-plugins/management-consulting/skills/pricing-strategy/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: pricing-strategy
+description: Diagnoses pricing power, willingness to pay, discounting, packaging, and monetization opportunities. Use for pricing strategy, discount leakage, monetization, packaging, price increase, value pricing, renewal pricing, or margin improvement.
+---
+
+# Pricing Strategy
+
+## When To Use
+
+Use this skill when the user needs to improve monetization, diagnose discounting, raise prices, redesign packaging, or understand willingness to pay.
+
+## McKinsey-Style Approach
+
+Connect price to value, customer segments, competitive alternatives, and sales behavior. Separate list price, realized price, discounting, mix, and packaging.
+
+## Workflow
+
+1. Define the pricing question and economic objective.
+2. Gather price architecture, discount data, win-loss, churn, margin, and competitor context.
+3. Diagnose leakage across list price, discounting, mix, packaging, and governance.
+4. Assess willingness to pay by segment or use case.
+5. Generate pricing moves and risks.
+6. Recommend a pricing action plan and test design.
+
+## Output Format
+
+```markdown
+# Pricing Strategy
+
+## Pricing Objective
+[Growth, margin, retention, adoption, or simplification.]
+
+## Diagnosis
+| Area | Evidence | Issue | Impact |
+|---|---|---|---|
+
+## Segment Price Logic
+| Segment | Value Driver | WTP Signal | Pricing Move |
+|---|---|---|---|
+
+## Recommended Moves
+1. [Move]
+2. [Move]
+3. [Move]
+
+## Risks and Tests
+[Risks, mitigations, and pilot design.]
+```
+
+## Quality Bar
+
+- Do not recommend a price move without segment logic.
+- Separate price realization from list pricing.
+- Include customer risk and sales execution risk.
+- Recommend a test or rollout sequence.

package/payload/premium-plugins/management-consulting/skills/profit-pool-analysis/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: profit-pool-analysis
+description: Maps where profit is created, captured, and leaking across a market, product set, customer base, or value chain. Use for profit pool analysis, margin strategy, value chain economics, where-to-play, pricing power, or strategic attractiveness.
+---
+
+# Profit Pool Analysis
+
+## When To Use
+
+Use this skill when revenue size alone is misleading and the user needs to know where attractive profit actually sits. It fits market entry, product portfolio, channel, value chain, and segment strategy questions.
+
+## McKinsey-Style Approach
+
+Follow the money across the system. Separate revenue pools from profit pools, identify who captures value, and connect economics to strategic choices.
+
+## Workflow
+
+1. Define the market, value chain, product set, or customer base.
+2. Map revenue and margin by activity, segment, product, channel, or customer group.
+3. Identify profit concentration and leakage points.
+4. Assess structural drivers: scale, pricing power, cost position, switching costs, and competitive intensity.
+5. Identify attractive and unattractive pools.
+6. Recommend strategic implications.
+
+## Output Format
+
+```markdown
+# Profit Pool Analysis
+
+## Scope
+[Market, products, customers, or value chain included.]
+
+## Profit Pool Map
+| Pool | Revenue | Margin | Profit | Growth | Attractiveness |
+|---|---|---|---|---|---|
+
+## Value Capture
+| Player or activity | Value captured | Reason |
+|---|---|---|
+
+## Strategic Implications
+1. [Where to play]
+2. [Where to avoid]
+3. [How to improve capture]
+```
+
+## Quality Bar
+
+- Do not confuse revenue size with attractiveness.
+- Show margin and profit, not only growth.
+- Explain the structural reason profit concentrates.
+- Tie findings to allocation or positioning decisions.

package/payload/premium-plugins/management-consulting/skills/risk-and-mitigation/SKILL.md

@@ -0,0 +1,49 @@
+---
+name: risk-and-mitigation
+description: Builds a strategic risk register with likelihood, impact, mitigations, triggers, owners, and contingency moves. Use for strategy risk, mitigation planning, risk register, board risk review, launch risk, execution risk, or "what could go wrong?" questions.
+---
+
+# Risk and Mitigation
+
+## When To Use
+
+Use this skill when a strategy or initiative needs a serious risk view before approval or execution. It fits board materials, launch planning, transformation governance, and investment decisions.
+
+## McKinsey-Style Approach
+
+Treat risk as part of the strategy, not a compliance appendix. Prioritize risks that could change the decision, economics, timing, or feasibility.
+
+## Workflow
+
+1. Define the strategy or initiative under review.
+2. Identify risk categories: market, customer, competitor, financial, operational, regulatory, organizational.
+3. Score likelihood and impact.
+4. Define mitigations, triggers, owners, and contingency actions.
+5. Identify residual risk after mitigation.
+6. Recommend go, no-go, redesign, or gated approval.
+
+## Output Format
+
+```markdown
+# Strategic Risk Register
+
+## Strategy Under Review
+[Brief summary.]
+
+## Risk Register
+| Risk | Likelihood | Impact | Mitigation | Owner | Trigger |
+|---|---|---|---|---|---|
+
+## Highest-Risk Assumptions
+[Assumptions that need testing.]
+
+## Contingency Moves
+[Actions to take if triggers occur.]
+```
+
+## Quality Bar
+
+- Focus on risks that change decisions.
+- Include triggers and owners.
+- Show residual risk after mitigation.
+- Avoid generic risk language.

package/payload/premium-plugins/management-consulting/skills/situation-assessment/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: situation-assessment
+description: Establishes a fact-based baseline for an existing business, market, product, or function. Use when the user asks for a situation assessment, current-state diagnosis, business health check, momentum review, strategic baseline, or "where are we really?" analysis. Diagnoses an operating business or function, not the validation of a brand-new startup idea.
+---
+
+# Situation Assessment
+
+## When To Use
+
+Use this skill when the user needs a defensible read of the current situation before choosing a strategy. Typical cases include business reviews, turnaround diagnosis, market position checks, operating performance reviews, and board preparation.
+
+## McKinsey-Style Approach
+
+Build the fact base before debating solutions. Separate facts, interpretations, and open questions. Look across financial performance, market position, customer momentum, competitive posture, operating health, and organizational constraints.
+
+## Workflow
+
+1. Frame the assessment question and decision context.
+2. Ask for available facts: financials, KPIs, market data, customer signals, competitive context, and recent changes.
+3. Build a MECE current-state view across performance, market, customers, operations, and organization.
+4. Identify the few facts that matter most for the decision.
+5. Separate confirmed facts from hypotheses and unknowns.
+6. Produce a situation read with implications and next diagnostic questions.
+
+## Output Format
+
+```markdown
+# Situation Assessment
+
+## Executive Read
+[One paragraph on where the business is and why it matters.]
+
+## Fact Base
+| Area | Evidence | Interpretation | Confidence |
+|---|---|---|---|
+
+## Momentum Signals
+| Signal | Direction | Why It Matters |
+|---|---|---|
+
+## Strategic Issues
+1. [Issue]
+2. [Issue]
+3. [Issue]
+
+## Open Questions
+[Questions that must be answered before committing to a strategy.]
+```
+
+## Quality Bar
+
+- Do not recommend before establishing the baseline.
+- Label facts, interpretations, and assumptions separately.
+- Highlight trend and momentum, not only point-in-time performance.
+- End with implications for the decision.

package/payload/premium-plugins/management-consulting/skills/stakeholder-alignment/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: stakeholder-alignment
+description: Maps stakeholders, decision criteria, influence paths, concerns, and pre-wire actions needed to win support. Use for stakeholder alignment, executive buy-in, pre-wiring, change management, board approval, leadership alignment, or "how do we get this approved?" questions.
+---
+
+# Stakeholder Alignment
+
+## When To Use
+
+Use this skill when a recommendation must win support across leaders, functions, investors, board members, customers, or implementation owners.
+
+## McKinsey-Style Approach
+
+Win the room before the meeting. Understand who must say yes, what each person needs to believe, where resistance will come from, and what engagement must happen in advance.
+
+## Workflow
+
+1. Define the decision and approval path.
+2. Identify stakeholders and influence relationships.
+3. Map each stakeholder's interests, likely concerns, and decision criteria.
+4. Assess support level and influence.
+5. Build a pre-wire plan.
+6. Prepare messages and objections by stakeholder.
+
+## Output Format
+
+```markdown
+# Stakeholder Alignment Plan
+
+## Decision Path
+[Who decides, who influences, and when.]
+
+## Stakeholder Map
+| Stakeholder | Role | Influence | Current Stance | What They Need To Hear |
+|---|---|---|---|---|
+
+## Resistance Points
+| Concern | Who Holds It | Response |
+|---|---|---|
+
+## Pre-Wire Plan
+| Action | Owner | Timing | Desired Outcome |
+|---|---|---|---|
+```
+
+## Quality Bar
+
+- Map influence, not only org hierarchy.
+- Identify what each stakeholder needs to believe.
+- Include objections and responses.
+- Sequence engagement before the formal meeting.

package/payload/premium-plugins/management-consulting/skills/strategic-options/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: strategic-options
+description: Generates and compares strategic options with clear decision criteria, trade-offs, and recommendation logic. Use for strategy options, path selection, growth choices, market entry choices, build-buy-partner, or "what are our options?" questions.
+---
+
+# Strategic Options
+
+## When To Use
+
+Use this skill when the user needs alternatives before committing to a strategy. It helps avoid false binaries and creates a defensible path from options to recommendation.
+
+## McKinsey-Style Approach
+
+Develop a small set of distinct, viable options. Compare them against decision criteria that matter. Recommend a path with trade-offs visible.
+
+## Workflow
+
+1. Clarify the strategic decision and constraints.
+2. Generate mutually distinct options.
+3. Define decision criteria.
+4. Assess each option against attractiveness, feasibility, risk, economics, and strategic fit.
+5. Identify hybrids or sequencing if useful.
+6. Recommend the best path and what must be true.
+
+## Output Format
+
+```markdown
+# Strategic Options
+
+## Decision
+[Decision being made.]
+
+## Options
+| Option | Description | Upside | Trade-Off | What Must Be True |
+|---|---|---|---|---|
+
+## Evaluation
+| Criteria | Option A | Option B | Option C |
+|---|---|---|---|
+
+## Recommendation
+[Preferred option and rationale.]
+
+## Next Tests
+[Evidence needed before committing.]
+```
+
+## Quality Bar
+
+- Options must be meaningfully different.
+- Criteria must reflect the user's decision, not generic attractiveness.
+- Include trade-offs and risks.
+- State what evidence would change the recommendation.

package/payload/premium-plugins/management-consulting/skills/transformation-roadmap/SKILL.md

@@ -0,0 +1,53 @@
+---
+name: transformation-roadmap
+description: Converts strategy into sequenced workstreams, phases, milestones, owners, dependencies, risks, and governance. Use for transformation roadmap, implementation plan, change program, PMO setup, strategic execution, or "how do we make this happen?" questions.
+---
+
+# Transformation Roadmap
+
+## When To Use
+
+Use this skill when a strategy needs to become a delivery plan. It fits operating transformations, growth programs, cost programs, digital transformations, post-merger integration, and capability builds.
+
+## McKinsey-Style Approach
+
+Translate the recommendation into phases that create value while reducing execution risk. Make owners, milestones, dependencies, and governance explicit.
+
+## Workflow
+
+1. Define the strategic goal and target outcomes.
+2. Identify workstreams and capabilities required.
+3. Sequence phases by value, dependency, and readiness.
+4. Assign owners, milestones, and decision gates.
+5. Identify risks, dependencies, and governance.
+6. Produce a roadmap and first 90-day plan.
+
+## Output Format
+
+```markdown
+# Transformation Roadmap
+
+## Target Outcome
+[What must change and by when.]
+
+## Workstreams
+| Workstream | Objective | Owner | Key Dependency |
+|---|---|---|---|
+
+## Roadmap
+| Phase | Timing | Major Actions | Milestones |
+|---|---|---|---|
+
+## First 90 Days
+[Immediate actions and decision gates.]
+
+## Governance
+[Cadence, escalation, metrics, and owners.]
+```
+
+## Quality Bar
+
+- Sequence by dependency and value.
+- Include first 90 days.
+- Assign owners and decision gates.
+- Make governance visible.

package/payload/premium-plugins/management-consulting/skills/value-realization/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: value-realization
+description: Defines how strategic value will be tracked, owned, measured, and captured after launch. Use for value realization, benefits tracking, synergy capture, transformation value, KPI governance, post-launch tracking, or "how do we make benefits stick?" questions.
+---
+
+# Value Realization
+
+## When To Use
+
+Use this skill when a strategy, transformation, acquisition, or initiative needs benefits that are measurable and owned after approval.
+
+## McKinsey-Style Approach
+
+Move from promised value to captured value. Define the value ledger, owners, metrics, timing, proof standard, and governance cadence.
+
+## Workflow
+
+1. Define the value ambition and benefit categories.
+2. Identify value drivers and initiatives.
+3. Assign owners and measurement methods.
+4. Set baselines, targets, and timing.
+5. Define governance and escalation.
+6. Produce the value realization plan.
+
+## Output Format
+
+```markdown
+# Value Realization Plan
+
+## Value Ambition
+[Target value and timing.]
+
+## Value Ledger
+| Benefit | Baseline | Target | Owner | Proof Standard |
+|---|---|---|---|---|
+
+## Governance
+| Cadence | Participants | Decisions |
+|---|---|---|
+
+## Risks To Capture
+[What could prevent value from being realized.]
+```
+
+## Quality Bar
+
+- Define baseline and target.
+- Assign owners for value, not only activity.
+- Separate one-time and recurring benefits.
+- Include governance and escalation triggers.

package/payload/premium-plugins/management-consulting/skills/war-gaming/SKILL.md

@@ -0,0 +1,51 @@
+---
+name: war-gaming
+description: Stress-tests strategy against competitor moves, market shifts, customer reactions, regulatory changes, and execution failure. Use for war gaming, scenario planning, strategy stress test, competitive response, risk scenarios, or "what could break this strategy?" questions.
+---
+
+# War Gaming
+
+## When To Use
+
+Use this skill before committing to a strategy that could be disrupted by rivals, market shifts, execution failure, regulation, customer response, or capital constraints.
+
+## McKinsey-Style Approach
+
+Pressure-test the strategy before reality does. Simulate likely and high-impact scenarios, identify weak points, and pre-commit response moves.
+
+## Workflow
+
+1. Define the strategy to test.
+2. Identify scenario dimensions: competitor, customer, market, regulatory, operational, financial.
+3. Build base, adverse, and aggressive scenarios.
+4. Assess impact on economics and strategic logic.
+5. Identify early warning signals.
+6. Recommend defensive and offensive responses.
+
+## Output Format
+
+```markdown
+# Strategy War Game
+
+## Strategy Under Test
+[Strategy summary.]
+
+## Scenarios
+| Scenario | Trigger | Impact | Likelihood | Severity |
+|---|---|---|---|---|
+
+## Vulnerabilities
+| Weak Point | Why It Matters | Mitigation |
+|---|---|---|
+
+## Response Playbook
+| Signal | Response | Owner |
+|---|---|---|
+```
+
+## Quality Bar
+
+- Include likely scenarios and painful scenarios.
+- Make early warning signals observable.
+- Tie responses to owners and decisions.
+- Do not turn the output into a generic risk list.