critical-thinker

Pressure-test architectural and product decisions before they become load-bearing.

Updated Apr 24, 2026

Search Tags:#documentation #decision analysis #critical thinking #design review #subagent #architecture review

Ready to run

npx skills add https://github.com/brianonieal/Syntaris --skill critical-thinker-brianonieal

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: critical-thinker
Source: https://github.com/brianonieal/Syntaris/tree/main/.claude/skills/critical-thinker
Command: npx skills add https://github.com/brianonieal/Syntaris --skill critical-thinker-brianonieal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you catch risky architectural and product decisions before they become expensive to change. It slows down high-impact choices just enough to expose hidden complexity, missing evidence, and simpler alternatives.

Core Features & Use Cases

Decision Pressure-Testing: Challenges major choices like stack selection, agent architecture, database design, and API direction.
Structured Critique Workflow: Uses a subagent to read project context, compare alternatives, and surface the strongest objections.
Decision Logging: Records the final outcome and rationale so the reasoning survives context resets and future gates.
Use Case: Before committing to a LangGraph-based orchestration layer for a new app, use this Skill to evaluate whether a simpler single-agent approach would reduce risk.

Quick Start

Use the critical-thinker skill to pressure-test my proposed architecture before I lock it in.

Frequently Asked Questions about critical-thinker

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

FAQPage Schema

How do I pressure-test an architecture design before committing to it?▼

Pressure-testing architecture design challenges high-impact choices by comparing alternatives and surfacing objections. It uses a subagent to read project memory, evaluate options, and log the final rationale to DECISIONS.md.

What is the best way to evaluate database schema and API design decisions?▼

Evaluating database schema and API design decisions requires a subagent-driven critique that reads project memory files, compares alternatives, and surfaces the strongest objections before logging the outcome to DECISIONS.md.

When do I need a structured critique workflow for decision analysis?▼

You need a structured critique workflow for decision analysis when a choice affects three or more future gates, such as project starts, agent architecture, stack selection, or database schema design.

Can I compare a single-agent approach against complex orchestration before locking in my stack?▼

Yes, a subagent-driven critique process compares a single-agent approach against complex orchestration by reading project context, evaluating alternatives, and exposing whether a simpler design reduces risk before the decision becomes load-bearing.

Does decision logging help preserve architecture review rationale across context resets?▼

Decision logging preserves architecture review rationale across context resets by recording the final outcome and reasoning in DECISIONS.md, ensuring the critique process survives future gates and project memory resets.

Why should I slow down major product decisions before they become load-bearing?▼

Slowing down major product decisions prevents expensive changes by exposing hidden complexity, missing evidence, and simpler alternatives. The critique workflow ensures choices are fully evaluated before they affect multiple future gates.