philosopher

Applies expansive cross-domain reasoning to reframe design problems before solving them.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill philosopher-rakedzior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: philosopher
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/philosopher
Command: npx skills add https://github.com/rakedzior/rootine --skill philosopher-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Design work often rushes from a shallow problem statement straight to solutions, baking in unexamined assumptions and missing the real problem. This Skill provides a structured cognitive mode that forces deeper problem exploration before any solutioning begins. ## Core Features & Use Cases - Three-Phase Reasoning Protocol: Moves through problem immersion, associative expansion, and synthesis in strict order, blocking premature solution generation. - Cross-Skill Integration: Works alongside every Intent design skill (strategize, investigate, blueprint, journey, organize, articulate, evaluate, fortify, include, specify, measure) to reframe briefs, question structural assumptions, and stress-test specs. - Intensity Levels and Check-ins: Supports low, medium, and high exploration depth with structured check-ins every few exchanges, plus clean exit sequences that translate insights back into the active design skill. - Use Case: A designer stuck on a user flow that feels logical but lifeless invokes philosopher mode; the Skill questions inherited interaction patterns, pulls analogies from library wayfinding and physical spaces, then hands reframed mental models back to the journey skill. ## Quick Start Ask the assistant to enter philosopher mode and sit with your design problem before proposing any solutions.

Frequently Asked Questions about philosopher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I brainstorm a design problem without jumping to solutions?

Invoke philosopher mode by saying "sit with this", "brainstorm", or "I'm stuck". The Skill enforces problem immersion first, then cross-domain associative expansion, and only enters synthesis when you explicitly ask for it.

What is expansive mode in a design workflow?

Expansive mode is a cognitive reasoning protocol that widens associative thinking, suppresses premature idea dismissal, and surfaces cross-domain connections. It changes how reasoning happens, not the tone or persona of the output.

Can philosopher mode work with other design skills?

Yes, it is designed as a cross-cutting mode for the Intent skill system. It pairs with strategize, investigate, blueprint, journey, organize, articulate, evaluate, fortify, include, specify, and measure, translating insights back into each skill's language on exit.

How do I control the depth of a brainstorming session?

Specify an intensity level: low for a quick reframe, medium for the full protocol, or high for maximum associative width. Check-in frequency adjusts accordingly, from every 2 exchanges at low intensity to every 4-5 at high.

When should I not use expansive exploration mode?

Avoid it when you need a concrete deliverable, decision, or recommendation immediately. The protocol blocks solution space until you choose to synthesize, so it slows down tasks that require fast, direct answers.