plugins/jira-orchestrator/skills/reasoning/SKILL.md
This skill should be used when the user asks to "reason through", "think step by step", "analyze systematically", "debug with hypotheses", "root cause analysis", "chain of thought", "tree of thought", "documentation lookup", or needs structured reasoning frameworks with mandatory documentation retrieval before analysis.
npx skillsauth add markus41/claude reasoningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Structured reasoning frameworks with mandatory documentation lookup for systematic problem solving.
This skill wraps two complementary capabilities:
Complex Reasoning (complex-reasoning.md) — Multiple reasoning frameworks (Chain-of-Thought, Tree-of-Thought, Hypothesis-Driven Debugging, Root Cause Analysis) that always query documentation before reasoning and store insights in memory.
Documentation Lookup (documentation-lookup.md) — Systematic documentation retrieval using Context7 MCP to ground all decisions in accurate, version-specific library documentation.
| Problem Type | Framework | Agent |
|-------------|-----------|-------|
| Linear, sequential | Chain-of-Thought | hypothesis-debugger |
| Multiple valid approaches | Tree-of-Thought | requirements-analyzer |
| Complex bug, unclear root cause | Hypothesis-Driven Debugging | hypothesis-debugger |
| Incident, systemic issue | Root Cause Analysis | root-cause-analyzer |
| Any technology decision | Documentation Lookup | requirements-analyzer |
MANDATORY before any reasoning about technology:
See complex-reasoning.md for full reasoning framework details.
See documentation-lookup.md for documentation retrieval protocol.
Works with: hypothesis-debugger (debugging workflows), root-cause-analyzer (incident analysis), requirements-analyzer (architecture decisions), task-enricher (technical planning).
development
Enhanced plan-authoring skill with Pre-Writing context gathering, task metadata, non-TDD templates, Red Flags, telemetry, and an automated plan linter. Use when you have a spec or requirements for a multi-step task, before touching code.
tools
Documentation intelligence engine with graph-based API docs, algorithm library, and drift detection
tools
Ultraplan cloud planning — kick off a plan in the cloud from your terminal, review and revise in the browser, then execute remotely or send back to CLI
tools
--- name: mcp description: Configure MCP servers for Claude Code — stdio vs HTTP, authentication, Tools/Resources/Prompts distinction, channels (CI webhook, mobile relay, Discord bridge, fakechat), and cost of always-loaded tools. Use this skill whenever adding an MCP server, debugging connection issues, choosing between MCP Tools vs Prompts vs Resources, installing channel servers, or managing .mcp.json. Triggers on: "MCP server", "mcp config", "add Obsidian MCP", "install context7", "channels"