Loading...
Loading...
Found 165 Skills
Use when evaluating ideas in voting phase. Be aggressive - score misaligned or poor ideas low enough to veto, score weak proposals below approval, score strong aligned ideas high. First check directive, then vote.
Pre-sprint diagnostic that determines whether a team should run a Foundation Sprint now, postpone it, or do prerequisite work first. Produces a Go / Conditional Go / Wait verdict with diagnosis, recommended preconditions, attendee list, and pre-sprint activities. Use when a team is considering starting a Foundation Sprint and wants a fast yes/no diagnosis before committing two days of facilitated work.
Day 3 (Wednesday) move of a Design Sprint that runs the art museum layout, heat map, speed critique, straw poll, Decider supervote, rumble-vs-all-in-one decision, and the storyboard that drives Thursday's prototype build. The most decision-heavy day of the sprint. Use Wednesday morning and afternoon after Tuesday's sketches are collected and attribution-stripped. Produces the canonical 5-15 step storyboard that becomes the build spec.
Apply first-principles thinking to break down complex problems into fundamental truths and rebuild solutions from the ground up. Use when solving strategic decisions, breaking through blockers, or challenging assumptions. Triggers on first principles, Elon Musk methodology, fundamental truths, strip assumptions, physics of the problem, rebuild from scratch.
Apply George Mack's High Agency approach to founder and leadership execution. Use when facing ambiguity, blockers, stalled execution, "impossible" constraints, cross-functional deadlock, or high-uncertainty decisions that require ownership and rapid action.
Structured disagreement protocols to strengthen proposals through systematic challenge and alternative generation.
Analyze complex systems through stocks, flows, and feedback loops to find high-leverage interventions. For organizational, environmental, social, and technical systems exhibiting circular causality. NOT for linear problems or simple cause-effect chains.
Produces structured judgment briefs for contested situations — news events, decisions, conflicts, strategy questions. Surfaces hidden bets, real disagreements, unspeakable truths, and who concretely pays. Use when the user wants sharper thinking about something messy, not a summary.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.
Use when a user asks for CEO review, founder-mode review, think bigger, strategy review, rethink this plan, is this ambitious enough, or critique of an existing product, strategy, roadmap, or implementation plan.
Technical Research Expert Skill, providing systematic technical research methodologies, document specifications, and best practices. Trigger this skill when you need to conduct technology selection, architecture research, framework comparison, or implementation scheme research.
Know the boundaries of your expertise and operate within them. Use when evaluating opportunities, making decisions outside your domain, or assessing when to defer to experts.