issue-tree-generator
SolidGenerate and validate issue trees for structured problem solving with MECE validation
Install
Quality Score: 96/100
Skill Content
Details
- Author
- a5c-ai
- Repository
- a5c-ai/babysitter
- Created
- 4 months ago
- Last Updated
- today
- Language
- JavaScript
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
issue-trees
Decompose a core problem into root causes with an ASCII tree. Outputs a fenced code block using box-drawing characters. Use for root-cause analysis, drilling from a high-level problem down to testable sub-problems, or step 2 of a strategic analysis.
tree-of-thought
Structured ideation and problem-solving using the Tree of Thought (ToT) technique. Use this skill whenever the user wants to brainstorm, ideate, explore solutions to a challenge, solve a complex problem, weigh options, or think through a decision with multiple possible paths. Triggers include phrases like "help me think through", "brainstorm", "explore options", "what are the possible approaches", "ideation session", "problem solve", "tree of thought", "think this through systematically", "explore different angles", "weigh my options", "decision analysis", or any open-ended challenge where multiple solution paths should be explored, evaluated, and refined before arriving at a recommendation. Also use when the user presents a business problem, strategic question, or creative challenge and wants structured exploration rather than a single direct answer.
behavior-trees-skill
Behavior tree design and implementation for robot decision making
creating-issues
Issue creation expertise and convention enforcement. Auto-invokes when creating issues, writing issue descriptions, asking about issue best practices, or needing help with issue titles. Validates naming conventions, suggests labels, and ensures proper metadata.
diagnose
Structured diagnosis of business and strategic problems — builds MECE logic trees, forms testable If/Then/Because hypotheses, scans external factors, and identifies root causes with evidence. Use when a metric is underperforming, something went wrong, or you need to find what's actually causing a problem before acting. Not for code bugs (use clean-code), brainstorming solutions to a known problem (use prioritize), or scoping a new idea (use discover). For market-level trends and competitive context, see research-market.