analogical-thinking
No SKILL.md available for this skill.
View on GitHubMore from andurilcode/skills
inversion-premortem
Apply inversion and pre-mortem thinking whenever the user asks to evaluate a plan, strategy, architecture, feature, or decision before execution — or when they want to stress-test something that already exists. Triggers on phrases like "is this a good idea?", "what could go wrong?", "review this plan", "should we do this?", "are we missing anything?", "stress-test this", "what are the risks?", or any request to validate a decision or design. Use this skill proactively — if the user is about to commit to something, this skill should be consulted even if they don't ask for it explicitly.
23scenario-planning
Apply scenario planning whenever the user is making long-term decisions, building roadmaps, evaluating strategies, or operating in an environment with significant uncertainty about how the future will unfold. Triggers on phrases like "what should our roadmap look like?", "how do we plan for the future?", "what if things change?", "we're not sure which direction the market will go", "how do we make this strategy resilient?", "what's our plan B?", "what are the different futures we could face?", or when a plan assumes a single future state. Also trigger when someone is over-committed to one expected outcome and hasn't stress-tested the strategy against alternative futures. Don't plan for one future — plan for multiple.
21second-order-thinking
Apply second-order thinking whenever the user is making a decision, proposing a change, or evaluating an action — especially one that seems obviously good or obviously safe. Triggers on phrases like "let's just do X", "the obvious answer is", "we should change Y", "what happens if we do Z?", "should we implement this?", "will this work?", or any time a user proposes an intervention in a system involving people, incentives, markets, or complex processes. Also trigger when first-order analysis has already been done and the user needs to go deeper. Second-order thinking should be applied before any significant decision is made — don't wait to be asked.
20red-teaming
Apply red teaming whenever the user wants to stress-test a system, plan, architecture, security model, or decision against adversarial conditions — or when they want to find the weakest points before someone else does. Triggers on phrases like "where are the weak points?", "how would someone break this?", "is this secure?", "find the holes in this plan", "play devil's advocate", "what are we not seeing?", "challenge this", "attack this design", "where could this be exploited?", or when the user is about to launch or commit to something significant. Also trigger for any system where trust, security, incentives, or adversarial actors are relevant — don't wait for the user to ask for a red team explicitly.
20decision-synthesis
Apply decision synthesis whenever the user has completed analysis — run multiple frameworks, mapped the problem, identified options — and now needs to actually choose. Triggers on phrases like "so what should we do?", "how do we decide between these?", "we have too many options", "everything seems equally valid", "how do we weigh these trade-offs?", "we can't agree on which direction", "given all this, what's the call?", or when a rich diagnostic phase has produced competing insights without a clear winner. Also trigger when a decision involves multiple stakeholders with different priorities, multiple criteria that pull in different directions, or significant irreversibility. This skill bridges analysis to action — don't leave a decision unmade because the map is rich.
20reasoning-orchestrator
Apply this skill first whenever the user presents a problem, question, or situation that requires structured thinking — before reaching for any specific reasoning framework. Triggers on any substantive request to evaluate, analyze, diagnose, decide, design, improve, understand, or learn from something. This is the entry point for the reasoning skill collection. If you are unsure which reasoning skill to use, always start here.
16