thinking-critically
Deep engineering analysis before implementation (Phase 2 of 9-Phase Feature Cycle). Challenges assumptions, identifies unknowns, and prevents architectural mistakes. Use when planning complex features, writing PRDs, designing systems, or before any significant code changes.
npx skills add majiayu000/claude-skill-registry --skill thinking-critically --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Thinking Critically Rigorous pre-implementation analysis that simulates a paranoid staff engineer review. This skill prevents costly architectural mistakes by forcing systematic examination of assumptions, trade-offs, and failure modes **before** writing code. **Phase 2 of the 9-Phase Feature Development Cycle:** ``` Interview -> THINK CRITICALLY -> Plan -> Branch -> Implement -> Verify -> PR -> Merge -> Wrap-Up ^ YOU ARE HERE ``` ## Philosophy ``` "The best time to find a design flaw is before you write the code." "Every assumption you don't question is a bug waiting to happen." ``` ## When to Use - Planning a new feature or system (Phase 2 of Feature Cycle) - Writing or reviewing a PRD - Making architectural decisions - Before implementing anything complex - When something "feels off" but you can't articulate why - After getting initial requirements, before diving into code ## Prerequisites - Feature spec completed (Phase 1: Interview complete) - `docs/features/FEAT-XXX/spec.md` exists with decisions - `docs/project.md` exists (for project context) - `docs/architecture/_index.md` exists (for technical constraints) ## Process ### 0. Read Context First ```bash # Read feature spec
- Philosophy
- When to Use
- Prerequisites
- Process
- 0. Read Context First
- 0.1 Determine Analysis Depth
- The 11-Step Critical Analysis Protocol
- Step 1: Problem Clarification & Constraints
- Step 2: Implicit Assumptions Identification (CRITICAL)
- Step 3: Design Space Exploration
- Step 4: Trade-off Analysis
- Step 5: Failure-First Analysis
- Step 6: Boundaries & Invariants
- Step 7: Observability & Control
Read feature spec (REQUIRED - output of Interview phase) cat docs/features/FEAT-XXX/spec.md Read project context cat docs/project.md 2>/dev/null Read architecture constraints cat docs/architecture/_index.md 2>/dev/null Check current status cat docs/features/FEAT-XXX/status.md
What does the thinking-critically skill do?
Deep engineering analysis before implementation (Phase 2 of 9-Phase Feature Cycle). Challenges assumptions, identifies unknowns, and prevents architectural mistakes. Use when planning complex features, writing PRDs, designing systems, or before any significant code changes.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill thinking-critically --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.