Loading...
Loading...
Found 126 Skills
This skill should be used when the user provides a strategy, plan, or decision document and wants to surface hidden assumptions and blind spots using the Known/Unknown 4-quadrant framework. Trigger on "known unknown", "4분면 분석", "blind spots", "뭘 놓치고 있지", "뭘 모르는지 모르겠어", "전략 점검", "전략 분석", "assumption check", "가정 점검", "quadrant analysis", "what am I missing". Strategy-level blind spot analysis with hypothesis-driven questioning. For requirement clarification use vague; for content-vs-form reframing use metamedium.
Trigger: Invoke when you have proposed a solution, hypothesis, or judgment that needs to be verified through practice, iterated via trial and error, or used to upgrade cognition through review. Common signals include experiment, prototype, validate, iterate, feedback loop. Trigger when an idea, hypothesis, or plan must be tested in practice and improved through iteration. Use this skill to move from action to understanding and back to action in a spiral learning loop.
Emergency Triage and Symptom Screening Assistant. This skill is triggered when users describe physical discomfort, pain, sudden symptoms, or ask urgent/semi-urgent health-related questions such as "Where do I hurt?", "I feel unwell", "Which department should I register for?", "Do I need to go to the hospital?", or "Help me judge". It also applies to scenarios where users conduct preliminary symptom screening for family or friends. Core capabilities: Quickly narrow down the range of possible causes through hypothesis-elimination interactive consultation, provide a ranking of possible causes, suggestions for registration departments, and examination items to be done after arriving at the hospital. Help users prepare information before seeing a doctor and reduce communication costs in the hospital.
Property-based testing with Hypothesis for discovering edge cases automatically. Use when testing invariants, finding boundary conditions, implementing stateful testing, or validating data transformations.
Document debugging sessions with hypothesis tracking and knowledge base
Select the right Proof of Life (PoL) probe based on hypothesis, risk, and resources. Use this to match the validation method to the real learning goal, not tooling comfort.
Execute complete FPF cycle from hypothesis generation to decision
Day 2 end capstone move of a Foundation Sprint. Compresses the sprint's full strategic frame into a single canonical sentence (the Founding Hypothesis) plus an assumption scorecard, why-we-believe, what-could-prove-us-wrong, and recommended next validation step. Use after Magic Lenses is signed. Strict canonical template; paraphrase is not accepted in v0.1.0. The Founding Hypothesis is the spine artifact the sprint exists to produce.
Deep Research Skill - Multi-source investigation across X (Twitter), the Web, and academic papers using team agents. Utilize this skill when users request deep research, comprehensive investigation, multi-perspective analysis, or hypothesis development on any topic. It is triggered by phrases such as "deep research", "investigate thoroughly", "research across sources", "ディープリサーチ", or requests for fact-based analysis with original hypotheses. It conducts a 6-phase research process: needs analysis, X preliminary research, parallel web deep-dive (3 agents), information integration, hypothesis construction, and final report delivery.
Probability, distributions, hypothesis testing, and statistical inference. Use for A/B testing, experimental design, or statistical validation.
Design a rigorous A/B test or experiment when the user asks to create an experiment, design an A/B test, or validate a hypothesis
Search the FPF knowledge base and display hypothesis details with assurance information