moai-workflow-thinking
Uses an MCP-based workflow to decompose complex coding tasks into a structured, analysis-first problem-solving process.
Install
mkdir -p .claude/skills/moai-workflow-thinking && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/8681" && unzip -o skill.zip -d .claude/skills/moai-workflow-thinking && rm skill.zipInstalls to .claude/skills/moai-workflow-thinking
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Sequential Thinking MCP for structured step-by-step analysis via --deepthink flag. Separate from UltraThink which is Claude's native extended reasoning mode. Use for multi-step analysis or architecture decisions.Key capabilities
- →Decomposes complex problems into sequential steps
- →Manages architectural decision-making workflows
- →Supports revision of reasoning steps
- →Enables branching for alternative solutions
How it works
It uses an MCP-based tool to force a methodical, step-by-step reasoning process that must be recorded and reviewed.
Inputs & outputs
When to use moai-workflow-thinking
- →Decompose complex architectural designs
- →Troubleshoot multi-layered system bugs
- →Plan large-scale refactoring efforts
- →Reason through complex logic problems
About this skill
Sequential Thinking MCP (--deepthink)
Structured step-by-step reasoning via mcp__sequential-thinking__sequentialthinking MCP tool.
CRITICAL: Three Distinct Reasoning Modes
MoAI has THREE independent deep analysis modes. They are NOT the same thing:
| Mode | Trigger | Mechanism | MCP Tool? | GLM Compatible? | Model |
|---|---|---|---|---|---|
--deepthink | Explicit --deepthink flag | Sequential Thinking MCP tool | YES — mcp__sequential-thinking__sequentialthinking | NO — generates server_tool_use content type | Any |
ultrathink | Keyword or auto-detection | Claude native extended reasoning (high effort) | NO — native to Claude | YES — no special content type | Any |
| Adaptive Thinking | Automatic on Opus 4.7 | Opus 4.7's only supported thinking mode | NO — built-in | YES | Opus 4.7 only |
Rules:
--deepthink→ ALWAYS invoke Sequential Thinking MCP. NEVER use for native reasoning.ultrathink→ ALWAYS use Claude's native extended reasoning. NEVER invoke Sequential Thinking MCP.- They can coexist:
ultrathink --deepthinkactivates BOTH modes independently. - Adaptive Thinking → Opus 4.7's built-in reasoning. Let the model adapt depth automatically based on task complexity.
- On Opus 4.7: do not hardcode a fixed reasoning budget. Adaptive Thinking overrides fixed-budget instructions.
Activation Triggers (--deepthink only)
Use Sequential Thinking MCP when --deepthink flag is explicitly present:
- Breaking down complex problems into steps
- Planning and design with room for revision
- Architecture decisions affect 3+ files
- Technology selection between multiple options
- Performance vs maintainability trade-offs
- Breaking changes under consideration
- Multiple approaches exist to solve the same problem
- Repetitive errors occur
Tool Parameters
Required Parameters:
thought(string): Current thinking step contentnextThoughtNeeded(boolean): Whether another step is neededthoughtNumber(integer): Current thought number (starts from 1)totalThoughts(integer): Estimated total thoughts needed
Optional Parameters:
isRevision(boolean): Whether this revises previous thinkingrevisesThought(integer): Which thought is being reconsideredbranchFromThought(integer): Branching point for alternativesbranchId(string): Branch identifierneedsMoreThoughts(boolean): If more thoughts needed beyond estimate
Usage Pattern
Step 1 - Initial Analysis:
thought: "Analyzing the problem: [describe problem]"
nextThoughtNeeded: true
thoughtNumber: 1
totalThoughts: 5
Step 2 - Decomposition:
thought: "Breaking down: [sub-problems]"
nextThoughtNeeded: true
thoughtNumber: 2
totalThoughts: 5
Step 3 - Revision (if needed):
thought: "Revising thought 2: [correction]"
isRevision: true
revisesThought: 2
thoughtNumber: 3
totalThoughts: 5
nextThoughtNeeded: true
Final Step - Conclusion:
thought: "Conclusion: [final answer]"
thoughtNumber: 5
totalThoughts: 5
nextThoughtNeeded: false
Guidelines
- Start with reasonable totalThoughts estimate
- Use isRevision when correcting previous thoughts
- Maintain thoughtNumber sequence
- Set nextThoughtNeeded to false only when complete
- Use branching for exploring alternatives
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "I can think through this without sequential thinking, it is simple" | Simple problems often hide second-order effects. Structured thinking forces you to enumerate them. |
| "The thinking steps are just internal, I do not need to record them" | Unrecorded reasoning cannot be reviewed. The chain of thoughts is evidence for the conclusion. |
| "I already know the answer, the thinking framework is overhead" | Confirmation bias skips disconfirming evidence. The framework forces you to consider alternatives. |
| "Branching is overkill for this decision" | Decisions with more than one viable path benefit from explicit branch comparison, even briefly. |
| "I will use UltraThink instead, it is the same thing" | UltraThink is native extended reasoning. Sequential Thinking is MCP-based structured analysis. They serve different purposes and have different API compatibility. |
Red Flags
- Architecture decision made without documented reasoning chain
- Sequential thinking session ended with nextThoughtNeeded still true
- Thought chain has no revision steps despite encountering contradictions
- Branching not used when two or more viable alternatives were identified
- --deepthink flag confused with UltraThink (wrong tool for the job)
Verification
- Thinking chain has a clear totalThoughts estimate that was met or revised
- Final thought sets nextThoughtNeeded to false with a conclusion
- At least one revision step exists if contradictions were encountered
- Branching used when multiple alternatives were identified (show branch IDs)
- Conclusion references specific thought numbers as supporting evidence
When not to use it
- →When the task is simple and lacks second-order effects
- →When native reasoning modes are sufficient
Limitations
- →Requires explicit --deepthink flag for activation
- →Must not be confused with native extended reasoning modes
How it compares
It forces explicit documentation of the reasoning chain, preventing confirmation bias by requiring revision and branching.
Compared to similar skills
moai-workflow-thinking side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| moai-workflow-thinking (this skill) | 2 | 3mo | No flags | Intermediate |
| chief-architect | 6 | 7mo | No flags | Advanced |
| ralplan | 1 | 2mo | Review | Intermediate |
| agent-migration-plan | 1 | 6mo | No flags | Advanced |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by modu-ai
View all by modu-ai →You might also like
chief-architect
ananddtyagi
PERSONAL APP ARCHITECT - Strategic development orchestrator for personal productivity applications. Analyzes project context, makes architectural decisions for single-developer projects, delegates to specialized skills, and ensures alignment between user experience goals and technical implementation. Optimized for personal apps targeting 10-100 users.
ralplan
Yeachan-Heo
Iterative planning with Planner, Architect, and Critic until consensus
agent-migration-plan
ruvnet
Agent skill for migration-plan - invoke with $agent-migration-plan
granola-reference-architecture
jeremylongshore
Enterprise meeting workflow architecture with Granola. Use when designing enterprise deployments, planning integrations, or architecting meeting management systems. Trigger with phrases like "granola architecture", "granola enterprise", "granola system design", "meeting system", "granola infrastructure".
phased-migration-plan
kaladron
Author or update a phased plan-*.md document for a multi-step migration or refactor. Use when a change is too large for a single commit, when coordinating database/architecture migrations across many call sites, or when the user asks for a "plan" before implementation. Covers the standard plan struc
oh-my-ccg-plan
1molchuan
RPI 计划阶段 — 约束集转化为零决策可执行计划