From jira-orchestrator
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 claudepluginhub markus41/claude --plugin jira-orchestratorThis skill uses the workspace's default tool permissions.
Structured reasoning frameworks with mandatory documentation lookup for systematic problem solving.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
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).