SCAMPER is an acronym for 7 transformation operations:
원문 언어: 영어
메뉴
이 저장소의 skills
SkillsMP는 benjam3n/reasoningtool에서 655개의 skill을 수집했습니다. skill을 열어 소스와 세부 정보를 확인하세요.
benjam3n/reasoningtool수집된 skill 655개 중 40개를 표시합니다.
SCAMPER is an acronym for 7 transformation operations:
원문 언어: 영어
Systematically identify Strengths, Weaknesses, Opportunities, and Threats to inform strategic decisions
원문 언어: 영어
Analyze complex systems using causal loop diagrams, stock and flow models, feedback loop identification, and system archetypes
원문 언어: 영어
Build comprehensive database of advocacy targets with personalized dossiers
원문 언어: 영어
Procedure for designing and implementing effective software testing strategies
원문 언어: 영어
Systematic process for creating, updating, and maintaining taxonomies and classification systems.
원문 언어: 영어
This procedure is the culmination of the no-guessing philosophy.
원문 언어: 영어
Goals often serve multiple intrinsic values that conflict with each other.
원문 언어: 영어
Value elicitation discovers what someone ACTUALLY values - their intrinsic goals.
원문 언어: 영어
Design and optimize viral loops, referral programs, and word-of-mouth triggers to achieve organic growth
원문 언어: 영어
Weekly review procedure to maintain visibility across all active projects, identify stalled work, and ensure continuous progress.
원문 언어: 영어
Take a hidden or implicit assumption and force it to be explicit and true. Trace what world that creates, what depends on it, and how fragile it is.
원문 언어: 영어
Force the assumption that X actually causes Y (not just correlates). Trace the mechanism, test the claim, and identify what must be true for causation to hold.
원문 언어: 영어
Force the assumption that a constraint is real and binding. Trace what it means for your options: what's ruled out, what's left, and is the constraint actually real?
원문 언어: 영어
Force the assumption that the situation is more complex than it appears. What are we missing? What hidden variables, feedback loops, or emergent dynamics are at play?
원문 언어: 영어
Force the assumption that something is absolutely critical — a must-have, non-negotiable, load-bearing element. Trace what that demands and whether it's actually true.
원문 언어: 영어
Force the assumption that the endeavor fails. Trace what happens: what's the damage? What's the recovery? What does failure teach? Pre-mortem thinking.
원문 언어: 영어
Force the assumption that something widely considered important is actually irrelevant. Trace what follows: what simplifies? What were we wasting attention on?
원문 언어: 영어
Force the assumption that something is theoretically possible — no physical, logical, or mathematical barrier prevents it. Trace what engineering, resource, or practical barriers remain.
원문 언어: 영어
Force the assumption that something is already known or settled. Trace what follows: what can we build on? Are we re-investigating the already-answered?
원문 언어: 영어
Force the assumption that a perceived constraint doesn't exist. What would you do with total freedom? What does the unconstrained solution reveal about the constrained one?
원문 언어: 영어
Take whatever the input claims or assumes, and force the exact opposite. Trace what world that implies, what evidence would support it, and what you learn from the inversion.
원문 언어: 영어
Force the assumption that something IS the problem. Trace what follows if this is truly the root cause. What would fixing it look like? What evidence would confirm it?
원문 언어: 영어
Force the assumption that a particular question is THE right question to ask. Trace what follows: does answering it actually help? What questions does it foreclose?
원문 언어: 영어
Force the assumption that two things are related. Trace the implications: what kind of relationship? Causal, correlational, structural, temporal? What follows?
원문 언어: 영어
Force the assumption that a decision or action is fully reversible. Trace what follows: should we just try it? What's the real cost of reversal? Is it actually reversible?
원문 언어: 영어
Force the assumption that a solution is discoverable — not just that it exists, but that we can actually find it with available methods. Trace what search strategy follows.
원문 언어: 영어
Force the assumption that the solution can be derived from first principles — no experiments, no search, just reasoning. What does that require? When is this warranted?
원문 언어: 영어
Force the assumption that no solution exists, then trace what follows. What does that imply about the problem? What should we do instead? What changes if we accept unsolvability?
원문 언어: 영어
Force the assumption that a solution exists for the problem at hand, then trace what follows. What does the solution space look like? What constraints must it satisfy? What have we been missing?
원문 언어: 영어
Force the assumption that the simple explanation is correct. Trace what follows from Occam's razor: what complexity can we eliminate? What if it really is that straightforward?
원문 언어: 영어
Force the assumption that something IS the solution. Trace what follows: does it actually address the problem? What are the costs? What breaks?
원문 언어: 영어
Force the assumption that the endeavor succeeds. Trace forward: what does the world look like after success? What new problems emerge? Is the success state actually desirable?
원문 언어: 영어
Force the assumption that something is theoretically impossible — a fundamental barrier prevents it. Trace what follows: what should we do instead? What's the closest achievable thing?
원문 언어: 영어
Force the assumption that something treated as known is actually unknown or unknowable. Trace what changes when the ground beneath a belief disappears.
원문 언어: 영어
Take any free-text input, classify it, and route to the correct sub-orchestrator. The automatic front door to all 597 skills.
원문 언어: 영어
Manage changes to system requirements, design, or implementation in a controlled way. Assesses impact, evaluates alternatives, and ensures traceability through implementation.
원문 언어: 영어
Systematically analyze competitive landscape using Porter's Five Forces, competitor mapping, and differentiation strategies
원문 언어: 영어
Establish and maintain consistency of system attributes with requirements and design throughout the lifecycle. Produces a CM plan with configuration item identification, baselines, change control procedures, status accounting, and audit planning.
원문 언어: 영어
Develop a structured Concept of Operations (ConOps) document that defines operational scenarios, user interactions, mission context, and operational modes for a system. Bridges the gap between stakeholder needs and system requirements.
원문 언어: 영어