thinking

Decompose large engineering problems into granular, solvable units.

Updated May 12, 2026
One-click install
npx skills add https://github.com/FL03/claude-shepherd --skill thinking-fl03
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thinking
Source: https://github.com/FL03/claude-shepherd/tree/main/skills/thinking
Command: npx skills add https://github.com/FL03/claude-shepherd --skill thinking-fl03

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the paralysis caused by large, ambiguous, or overwhelming engineering tasks by forcing a structured decomposition of the problem space.

Core Features & Use Cases

  • Problem Decomposition: Breaks down massive, mountain-sized tasks into manageable, actionable pebbles.
  • Assumption Mapping: Explicitly surfaces hidden assumptions to prevent logic drift during execution.
  • Use Case: Use this before starting a multi-hour sprint or a complex refactor to ensure the problem is clearly defined and the execution path is logically sound.

Quick Start

Invoke the thinking skill to decompose the current project requirements into a series of small, actionable tasks.

Frequently Asked Questions about thinking

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

FAQPage Schema
How do I decompose complex engineering problems into actionable tasks?

To decompose complex engineering problems, you must break large, ambiguous requirements into granular, solvable units. This structured decomposition forces explicit assumption mapping to prevent logic drift during execution phases.

What is assumption mapping in software problem-solving?

Assumption mapping in problem-solving explicitly surfaces hidden assumptions to prevent logic drift. It ensures logical consistency across execution phases by requiring clear problem definition before task delegation.

When do I need to use problem decomposition for sprint planning?

You need problem decomposition for sprint planning when facing multi-hour tasks or complex refactors. It addresses paralysis caused by overwhelming engineering tasks by transforming mountain-sized requirements into manageable pebbles.

Can I use this approach for architectural design and task delegation?

Yes, you can use this problem decomposition approach for architectural design and task delegation scenarios. It applies structured decomposition to ensure the execution path is logically sound across complex engineering projects.

What are the limitations of problem decomposition for ambiguous tasks?

A key limitation of problem decomposition for ambiguous tasks is the strict requirement for clear problem definition and explicit assumption mapping. Without these inputs, achieving logical consistency across execution phases is not possible.