skeptic-engineer

Identify and critique flaws in proposed plans and architectures before execution.

4|Updated Feb 19, 2026

Search Tags:#planning #quality-assurance #risk-management #architecture-review #design-review #skepticism

Ready to run

npx skills add https://github.com/oxhagolli/clawdskillz --skill skeptic-engineer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skeptic-engineer
Source: https://github.com/oxhagolli/clawdskillz/tree/main/skills/skeptic-engineer
Command: npx skills add https://github.com/oxhagolli/clawdskillz --skill skeptic-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams anticipate and address flaws in plans, architectures, or proposals by injecting skepticism and structured questioning before execution.

Core Features & Use Cases

Systematic questioning of scope, complexity, dependencies, failure strategies, and maintainability.
Architecture and plan reviews to surface risks and guardrails.
Guided response format for communicating concerns and escalation paths.

Quick Start

Initiate a skeptical review of the current feature proposal to surface hidden risks and decision points.

Frequently Asked Questions about skeptic-engineer

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

FAQPage Schema

What is an architecture review and how does it identify design flaws before execution?▼

An architecture review systematically questions scope, complexity, and dependencies to identify design flaws before execution. It surfaces hidden risks and establishes guardrails to ensure proposed systems remain maintainable.

How do I conduct a skeptical plan review to evaluate risk and maintainability?▼

Conduct a skeptical plan review by applying structured questioning to evaluate risk and maintainability. This process surfaces failure strategies and rollback considerations, exposing decision points before execution begins.

Can I use structured skepticism for software design reviews and proposal evaluations?▼

Yes, you can use structured skepticism for software design reviews and proposal evaluations. It systematically critiques potential flaws across systems and processes, focusing on dependencies and clear escalation paths.

What is the best way to catch hidden risks and dependency flaws in a feature proposal?▼

The best way to catch hidden risks and dependency flaws in a feature proposal is through rigorous review protocols. Explicit risk questions and rollback considerations surface decision points and prevent execution failures.

When do I need a formal risk management review for my system architecture?▼

You need a formal risk management review when proposed architectures face high complexity or unclear dependencies. It injects structured questioning to address failure strategies and maintainability before execution.

What are the limitations of using manual questioning for quality assurance in planning?▼

Manual questioning for quality assurance in planning lacks structured escalation paths if not rigorously guided. Without explicit risk questions and rollback considerations, critical failure strategies and dependencies may be missed.