Loading...
Loading...
Found 8 Skills
A deterministic thinking partner that challenges assumptions and applies mental models to sharpen decisions, solve problems, and think more clearly. Use this skill whenever a user says "help me think through X", "challenge my thinking", "what am I missing", "apply mental models to this", "play devil's advocate", "stress test this idea", "poke holes in my plan", "help me decide between X and Y", "what are the second-order effects", "I'm stuck on a decision", names any specific model (SWOT, first principles, inversion, pre-mortem, etc.), or asks for structured reasoning on any ambiguous, high-stakes, or complex problem. Also trigger when the user seems uncertain, is rationalizing, or is asking "am I thinking about this right?" Even casual phrases like "what do you think about..." on non-trivial topics should trigger this skill.
Thinking Partner - Help you sort out the situation from chaos, lock in core problems, break down bottlenecks, co-create solutions, and implement actions
Gather project context before drafting an ADR — business domain, system landscape, existing ADRs, related repos, LikeC4 model. Run BEFORE draft-adr when the architect is new to the system or context is thin. Back-and-forth Q&A with zero hallucination; every fact confirmed by the human before it counts.
Adversarial truth-extraction agent that interrogates the user to get past their own self-deception, evasions, and comfortable cover stories to what is ACTUALLY true. A harder-edged sibling of thinking-partner: instead of gently facilitating, it treats the user as a subject with a story to crack open — using the real elicitation craft of intelligence and police interrogation (rapport, the Scharff method, strategic use of evidence, contradiction-pinning). Use when the user says: 'допроси меня', 'interrogate me', 'колись', 'вытащи из меня правду', 'допрос', 'расколи меня', 'press me', 'grill me', 'проверь меня на прочность', 'я себе вру', 'help me stop bullshitting myself', or wants to stress-test a decision, claim, or plan by being questioned hard. Also trigger when the user is obviously rationalizing, hiding the real reason, or asking to be held to account. NEVER hands over conclusions — it extracts them from the user under questioning. Refuses to coach interrogating anyone but the consenting user.
This skill should be used when the user says "interview me about", "help me clarify", "stress-test my idea", "let's explore this concept", "challenge my assumptions about", "grill me on", "drill into my plan", or needs structured questioning to refine and articulate their thinking.
Brainstorm product ideas, explore problem spaces, and challenge assumptions as a thinking partner. Use when exploring a new opportunity, generating solutions to a product problem, stress-testing an idea, or when a PM needs to think out loud with a sharp sparring partner before converging on a direction.
Thinking partner for trading theses: worldview, evidence, conviction, execution. Use when discussing market views, macro worries, or building a trade idea (e.g. "I think dollar gets debased", "is DeFi undervalued", asset allocation).
Optional Stage 0 of the feature workflow — clarify vague ideas through dialogue until they are ready to enter the design phase. The role of AI is a thinking partner: dig out the real problem the user wants to solve (instead of sticking to the first solution they blurt out), actively evaluate the solution when the user brings it up, and propose better alternatives if necessary. After the discussion, output {slug}-brainstorm.md to document the results. Trigger scenarios: The user says "I have an unclear idea", "Let's brainstorm first", "The feature direction is still undecided", or the user brings a specific solution but wants to hear other ideas first. Skip this stage and proceed directly to design if the idea is already clear and the user does not want to discuss the solution further. This stage also does not handle bugs and refactoring.