sequential-thinking

Analyzes complex decisions and produces a structured reasoning tree via dependency mapping and bias review.

1|Updated May 18, 2026
One-click install
npx skills add https://github.com/linenoize/topia --skill sequential-thinking-linenoize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sequential-thinking
Source: https://github.com/linenoize/topia/tree/main/skills/sequential-thinking
Command: npx skills add https://github.com/linenoize/topia --skill sequential-thinking-linenoize

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps reason through complex decisions where multiple variables, constraints, and trade-offs interact, so conclusions are based on ordered logic instead of guesswork.

Core Features & Use Cases

  • Reversibility classification: Distinguishes one-way, two-way, and partially reversible decisions before deep analysis.
  • Dependency mapping: Identifies which variables constrain or influence others so evaluation happens in the correct order.
  • Second-order and bias checks: Reviews downstream effects and common reasoning biases to improve decision quality.
  • Use case: Choose an architecture, debug a multi-cause issue, or compare competing plans when the best choice depends on several interconnected factors.

Quick Start

Use the sequential-thinking skill to analyze the decision by identifying its variables, dependencies, and best recommendation.

Frequently Asked Questions about sequential-thinking

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

FAQPage Schema
How do I break down complex architecture decisions into structured steps?

Architecture decisions are broken down by mapping variable dependencies and classifying reversibility, producing a structured reasoning tree. This approach ensures multi-variable planning constraints are resolved in the correct logical order.

What is the best way to map dependencies when comparing competing software plans?

Dependency mapping identifies which variables constrain or influence others, ensuring evaluation happens in the correct order. This structured reasoning process prevents guesswork when comparing competing plans with interconnected factors.

How do you check for second-order effects and bias in multi-variable planning?

Second-order effects and common reasoning biases are checked by reviewing downstream impacts during decision-making. This structured analysis improves recommendation quality by exposing hidden trade-offs before finalizing architecture choices.

Can I use structured reasoning to debug multi-cause issues instead of guessing?

Structured reasoning debugging applies dependency mapping to multi-cause issues, resolving constraints in ordered logic. By distinguishing reversible and irreversible changes, it produces rigorous recommendations based on analysis instead of guesswork.

When should I classify decision reversibility before deep architecture analysis?

Decision reversibility classification should occur before deep analysis to distinguish one-way, two-way, and partially reversible decisions. This step ensures architecture trade-offs are evaluated with the correct level of caution regarding downstream constraints.