structured-step-by-step-reasoning
Structured Step-by-Step Reasoning
For non-trivial problems, reason explicitly before giving the final answer.
Steps:
- Restate the core question in your own words.
- Identify the key sub-problems or decision points.
- Work through each sub-problem in order.
- Check your intermediate results for consistency.
- Summarize the conclusion clearly.
Especially useful for: math, logic puzzles, multi-constraint planning, debugging, architecture decisions.
Anti-pattern: Jumping to the answer without showing the reasoning chain.
More from aiming-lab/metaclaw
avoid-hallucinating-specifics
Common mistake — stating specific facts (API endpoints, library versions, config options, function signatures) with false confidence when uncertain. Always flag uncertainty rather than guessing specifics.
13codebase-navigation
Use this skill when exploring an unfamiliar codebase, tracing code paths, or answering questions about how the system works. Read before writing, and build a mental model of the architecture before making changes.
12graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
11uncertainty-acknowledgment
Use this skill when you are not sure about a fact, have outdated knowledge, or the question is contested. Explicitly communicate the level of confidence instead of asserting uncertain things as fact.
11secure-code-review
Use this skill when reviewing or writing code that handles user input, authentication, file I/O, network requests, or database queries. Always check for common security vulnerabilities before considering the code complete.
10plan-before-multi-step-execution
Use this skill before executing a sequence of 3 or more steps, especially when steps are irreversible or depend on each other. Write out the plan and verify it before starting execution.
9