From futureproof-c-suite-brainstorming
Systematically applies the seven SCAMPER innovation prompts (Substitute, Combine, Adapt, Modify, Put to other use, Eliminate, Reverse) to an existing product, service, or process to generate concrete, board-ready innovation ideas. Trigger: when a user describes an existing product, service, or business process and asks for innovation ideas, improvement angles, or structured brainstorming. Also triggers when a user says they need to evolve or reinvent a current business line.
How this skill is triggered — by the user, by Claude, or both
Slash command
/futureproof-c-suite-brainstorming:scamper-innovation-prompterThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
```
FutureProof:connect(skill="scamper-innovation-prompter")
Use the returned context, experiments, instructions, and recent_sessions to personalise this session — particularly any prior SCAMPER analyses, strategic priorities, competitive landscape intelligence, and ICA definitions that should inform ideation filters.
Ask the user:
If FutureProof context contains existing ICA profiles, strategic plans, or prior session findings, surface them for confirmation before proceeding.
Before applying SCAMPER, construct a Current-State Architecture of the subject:
This baseline ensures SCAMPER prompts interrogate the actual structure rather than a surface-level abstraction.
Work through each lens systematically. For every lens, generate 2–4 concrete innovation hypotheses grounded in the baseline from Step 3. Each hypothesis must specify the component(s) it targets and articulate a plausible mechanism of impact.
What components, materials, suppliers, channels, technologies, or people could be replaced with alternatives that improve cost, speed, quality, or ICA experience?
What elements — internal or external — could be merged, bundled, or integrated to create compounding value?
What models, frameworks, or solutions from other industries, geographies, or eras could be borrowed and fitted to this context?
What happens if we dramatically amplify or reduce a specific attribute — scale, frequency, intensity, price, complexity, personalisation?
Could the existing product, service, process, data, or infrastructure serve a different ICA segment, use case, or market entirely?
What could be removed entirely — features, steps, approvals, roles, costs — without degrading (or while actually improving) ICA-perceived value?
What if the sequence, hierarchy, ownership, or direction of flow were inverted?
Apply any user-specific instructions from FutureProof context — such as strategic themes, risk appetite, or prioritised innovation horizons — to weight and filter hypotheses throughout this step.
Produce a structured SCAMPER Innovation Brief containing the following sections:
A single paragraph identifying the 3 highest-potential innovation hypotheses across all seven lenses, with a rationale for why these warrant executive attention first.
A table with the following columns for every hypothesis generated:
| # | SCAMPER Lens | Target Component | Hypothesis | Mechanism of Impact | Estimated Effort (L/M/H) | Estimated Impact (L/M/H) | Strategic Alignment |
|---|
A 2×2 effort-versus-impact plot (described textually or as a structured list) categorising each hypothesis into:
For each of the three highest-priority hypotheses, provide:
A consolidated list of the critical assumptions underlying the top hypotheses, formatted as testable statements suitable for experiment design.
FutureProof:save_experiment(skill="scamper-innovation-prompter", experiment={
hypothesis: "[Top-ranked SCAMPER hypothesis framed as a testable statement]",
variants: ["control: current product/service/process design", "variant: [specific SCAMPER modification described concisely]"],
measurement: "[ICA-facing metric or financial KPI, e.g., conversion rate, NPS delta, unit margin, time-to-value]",
expected_impact: "[Quantified directional estimate, e.g., 10–20% reduction in onboarding time for mid-market ICA segment]"
})
Generate one experiment block for each of the top 3 hypotheses. Where prior experiments from FutureProof context exist, reference their outcomes to refine the new hypotheses.
FutureProof:request_research(skill="scamper-innovation-prompter",
query="[Targeted query informed by the SCAMPER analysis, e.g., 'Emerging subscription-to-outcome business model transitions in enterprise SaaS 2024–2025' or 'Case studies of successful feature elimination driving NPS improvement in B2B services']",
reason="Validate and enrich the top SCAMPER hypotheses with external market evidence, competitive precedent, and ICA behaviour data before executive presentation"
)
Tailor the query to the specific industry, ICA segment, and SCAMPER lenses that surfaced the most promising hypotheses.
FutureProof:save_session(skill="scamper-innovation-prompter", session={
summary: "Applied SCAMPER framework to [subject] targeting [innovation intent] for [ICA segment]",
key_findings: ["[Top hypothesis 1 — lens and one-line description]", "[Top hypothesis 2]", "[Top hypothesis 3]", "[Most significant assumption identified for testing]"],
user_feedback: null
})
npx claudepluginhub peter-swain-inc/futureproof-skillsCreates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.