← ClaudeAtlas

thinking_oslisted

Cognitive operating system for structured problem solving. Use when designing features, planning projects, debugging issues, implementing solutions, analyzing requirements, writing specs, breaking down tasks, investigating bugs, architecting systems, reviewing designs, or thinking through any non-trivial problem. Supersedes genius-thinking.
kouroshez/coding-os · ★ 6 · AI & Automation · score 77
Install: claude install-skill kouroshez/coding-os
# Thinking OS — Full Methodology ## Purpose Complement the always-active Kernel rule (`thinking_os.md`, in your adapter's rules dir) with the complete Zoom cycle, Process Manager, and 10 Thinking Tools. Load this skill when the Complexity Gate returns COMPLICATED or COMPLEX. Source of truth: consumer projects read `docs/workflow/thinking_os-final-edition.md` (copied by `cos init`); the meta-repo canonical lives at `src/core/docs/thinking_os-final-edition.md`. > Naming note: the skill slug `thinking_os` intentionally keeps the underscore to mirror the `thinking_os` Python subsystem it fronts (other skills use kebab-case). A deliberate, documented exception to the kebab-case convention — not an oversight. --- ## Kernel Decisions (Detailed) ### Complexity Gate (Depth Routing) Gate classification (Q1 + Q2) is handled by the always-active rule. Use this matrix to determine **depth of analysis**: ``` │ 1 dim │ 2-4 dim │ 5+ dim ────────────────┼───────────────┼─────────────────┼───────────────── CLEAR │ Just do it │ Quick checklist │ Rare — batch it COMPLICATED │ Single Zoom In│ Light Zoom cycle │ Full Zoom cycle COMPLEX │ Probe + test │ Zoom + test/dim │ Full Zoom + prototype CHAOTIC │ Act now │ Act now, Zoom │ Act now, Zoom later CONFUSION │ Break it down │ Break it down │ Separate problems ``` For COMPLEX problems, activate **Experiment Protocol** before full Zoom In: 1. HYPOTHESIS: "I