Agent skill
self-critique
Analyze your own previous response with rigorous self-critique
Install this agent skill to your Project
npx add-skill https://github.com/scizorman/dotfiles/tree/main/modules/home/coding-agent/config/skills/self-critique
SKILL.md
Critical Thinking
You are now operating in a "Critical Thinking Mode". Your primary function is to act as skeptical, detail-oriented, and ruthlessly honest analyst. Your objective is NOT to defend or justify your previous response, but to actively identify its potential weaknesses, hidden assumptions, and overlooked risks.
Analyze your OWN immediately preceding response in this conversation based on the following comprehensive framework. Structure your output using these exact headings. Number items within each section starting from 1.
1. Core Thesis & Confidence Score (Initial)
-
- Core Thesis: In a single, concise sentence, what was the central solution or argument I proposed in my previous answer?
-
- Initial Confidence: On a scale of 1-10, how confident was I in that proposal at the moment of generation?
2. Foundational Analysis: Assumptions & Context
-
- High-Impact Assumptions: What are the top 3 most critical assumptions I made that, if proven wrong, would completely invalidate my proposed solution? Focus on technical, environmental, and resource-based assumptions.
-
- Contextual Integrity: Did I fully respect all constraints and requirements mentioned earlier in this conversation? Point out any potential contradictions or forgotten details.
3. Logical Integrity Analysis
-
- Premise Identification: What were the fundamental premises or starting points of my argument? (e.g., "The user needs a scalable solution," "Redis is the best tool for rate limiting.")
-
- Chain of Inference: Is there a clear, step-by-step logical chain connecting the identified premises to the final conclusion? Point out any significant logical leaps, gaps, or steps where the conclusion does not necessarily follow from the evidence provided.
-
- Potential Fallacies: Does my reasoning contain any common logical fallacies (e.g., asserting a false dichotomy, making a hasty generalization, appealing to a questionable authority)?
4. AI-Specific Pitfall Analysis
Evaluate my previous response against these common failure modes for AI agents. Provide a "Pass" or "Fail" for each, with a brief justification for any "Fail".
-
- Problem Evasion: (Pass/Fail) Did I solve the user's stated problem but avoid the actual, underlying difficult problem?
-
- "Happy Path" Bias: (Pass/Fail) Did I neglect to address error handling, edge cases, or potential failure scenarios?
-
- Over-Engineering: (Pass/Fail) Did I propose a solution that is unnecessarily complex?
-
- Factual Accuracy & Hallucination: (Pass/Fail) Are all technical details verifiably correct?
5. Risk & Mitigation Analysis
-
- Overlooked Risks: What are the top 3 practical risks or negative consequences of implementing my suggestion?
-
- Alternative Scenarios: What is a fundamentally different approach that I failed to consider?
6. Synthesis & Revised Recommendation
-
- Summary of Flaws: In bullet points, summarize the most critical weaknesses discovered.
-
- Revised Confidence Score: Given this analysis, re-evaluate the confidence in my original proposal on a 1-10 scale.
-
- Actionable Next Step: What is the single most important action the user should take before acting on my original advice?
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
project-plan-creator
Creates project management plans in Markdown. Use when creating project plans, defining how to manage scope/schedule/risk/communication, or detailing project execution strategy. Primarily for internal projects that build systems, processes, or organizational capabilities.
github-project-operator
Manages GitHub Projects v2 write operations using gh CLI. Use when adding issues or PRs to a project, creating tasks (issues) in a project, updating field values (Status, Priority, Size, Sprint, etc.), creating draft issues, creating fields, or archiving items. Also use at the start of a session when selecting a project to work with.
github-issue-creator
Create GitHub issues with gh CLI, including standard issues and sub-issues linked to a parent issue. Use when creating a new issue, breaking down a larger issue into child issues, or establishing a parent-child relationship between issues. Detect repository issue templates, apply title and body conventions, and create the issue with gh CLI.
github-issue-pr-commenter
Post structured comments to GitHub Issues and Pull Requests with gh CLI. Use when reporting completed work, sharing progress, summarizing investigation results, recording design decisions, proposing implementation plans, asking for feedback, or adding supplementary context to a pull request conversation. Do not use for inline pull request review comments on specific files or lines.
github-pr-creator
Submit changes as a GitHub Pull Request with gh CLI. Covers the full workflow: issue confirmation, branch naming, ghq-based git worktree creation or reuse, commit and push, PR template detection, and PR creation with gh pr create. Use when creating a pull request, opening a PR, starting work on an issue, or cutting a working branch.
project-charter-creator
Use this skill whenever the user wants to create, draft, or improve a Project Charter. Triggers include: any mention of 'project charter', 'charter', 'プロジェクト憲章', 'プロジェクトチャーター', 'プロジェクト企画書', or requests to formally authorize a project, define project scope and objectives, align stakeholders, or establish project governance. Also use when the user says 'プロジェクトの立ち上げ', 'プロジェクトの認可', 'キックオフ文書', or mentions needing to get sponsor approval for a project. This skill covers project charters for any methodology (Waterfall, Agile, Lean Six Sigma) and any domain (IT, construction, marketing, organizational change, product development, etc.). Use this skill even if the user just says 'help me start a project' or 'I need to get alignment on my project'.
Didn't find tool you were looking for?