skills.rest
doanchienthangdev
doanchienthangdevCOMMUNITY
Explore all skills by this author →
GitHub

thinking-sequentially

Structure complex reasoning into numbered thoughts with explicit dependencies.

4|1|Updated Dec 30, 2025
Search Tags:#planning#debugging#problem solving#reasoning#thought process
One-click install
npx skills add https://github.com/doanchienthangdev/omgkit --skill thinking-sequentially
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: thinking-sequentially
Source: https://github.com/doanchienthangdev/omgkit/tree/main/plugin/skills/methodology/sequential-thinking
Command: npx skills add https://github.com/doanchienthangdev/omgkit --skill thinking-sequentially

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps users break down complex problems into manageable, traceable steps, ensuring thoroughness and clarity in their thought process.

Core Features & Use Cases

  • Decomposition: Breaks down multi-step problems into numbered thoughts with explicit dependencies.
  • Tracking: Allows for clear tracking of how each insight builds upon previous ones.
  • Revision & Branching: Supports updating thoughts and exploring parallel hypotheses.
  • Use Case: When debugging a complex software issue, use this skill to meticulously log each step of your investigation, noting which tests depend on previous findings, making it easier to pinpoint the root cause.

Quick Start

Use the thinking sequentially skill to break down the problem of planning a new feature into numbered thoughts.

Frequently Asked Questions about thinking-sequentially

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

FAQPage Schema
How do I structure complex reasoning for multi-step debugging?▼

Structure complex reasoning by decomposing multi-step debugging into numbered thoughts with explicit dependencies. This allows you to track how each insight builds on previous findings and pinpoint root causes meticulously.

What is the best way to break down architectural decisions into traceable steps?▼

Breaking down architectural decisions involves creating numbered thought sequences with explicit dependencies. This method supports decomposition, tracking, and branching of insights to ensure thoroughness and clarity.

Can I track parallel hypotheses during root cause analysis?▼

Yes, you can track parallel hypotheses during root cause analysis by using thought branching. This supports exploring and updating parallel investigation paths while maintaining clear dependency tracking.

How do I log a code review thought process with explicit dependencies?▼

Log a code review thought process by structuring insights as numbered thoughts with explicit dependencies. This decomposition allows for clear tracking of how each review finding builds upon previous observations.

When should I use numbered thought sequences for problem solving?▼

Use numbered thought sequences for problem solving when facing multi-step problems requiring decomposition, revision, and branching of insights. It is ideal for complex debugging, architectural decisions, and root cause analysis.

Related Skills

Explore More Software Engineering Skills→
ShavakanShavakan
2

sequential-thinking

Assess problem complexity and generate a documented reasoning trail for MCP applicability decisions.

Community
Basic
markus41markus41
18

complex-reasoning

Apply Chain-of-Thought, Tree-of-Thought, and MECE analysis to complex problems.

Community
Advanced
php-testophp-testo
203

testo-inline-tests

Attach inline test cases to pure functions for deterministic output validation.

Official
Intermediate
ThuHuynh1438ThuHuynh1438

json-canvas

Create and edit valid JSON Canvas files with nodes and edges.

Community
Intermediate