rigorous-reasoning
Table of Contents
- Overview
- Priority Signals
- Red Flag Self-Monitoring
- Analysis Workflows
- Required TodoWrite Items
- Integration with Other Skills
- Exit Criteria
Rigorous Reasoning
Overview
Rigorous reasoning prioritizes validity and accuracy over conversational politeness. Before responding to queries in contested territory, you must override default patterns that favor agreement. Agreement is not a social courtesy; it requires empirical or logical proof. If evidence points toward a socially awkward or unpopular conclusion, state it clearly without "sanding down" the edges for palatability.
Priority Signals
These principles override default conversational tendencies:
More from athola/claude-night-market
project-planning
Turn a specification into a phased implementation plan with dependency ordering.
126code-quality-principles
KISS, YAGNI, and SOLID code quality principles for clean code, reducing complexity and preventing over-engineering.
94project-brainstorming
Guide project ideation via Socratic questioning to generate project briefs.
92doc-generator
Generate or remediate documentation with human-quality writing and style.
81project-specification
Transform project briefs into testable specifications with user stories, acceptance criteria, and measurable outcomes.
78bloat-detector
Detect codebase bloat via progressive analysis: dead code, duplication, complexity, and doc bloat.
71