analyze-ticket
Analyzes ticket technical complexity to guide planning and development effort.
Install
mkdir -p .claude/skills/analyze-ticket && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/16920" && unzip -o skill.zip -d .claude/skills/analyze-ticket && rm skill.zipInstalls to .claude/skills/analyze-ticket
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.
Internal helper called by /resolve. Analyzes ticket complexity (SIMPLE, MEDIUM, COMPLEX) to determine exploration depth and planning approach. Not intended for direct invocation.Key capabilities
- →Extract keywords from ticket content for complexity signals
- →Calculate a base score based on technical complexity and scope indicators
- →Apply label-based overrides to force complexity levels
- →Determine the complexity level (SIMPLE, MEDIUM, COMPLEX)
- →Recommend workflow phases based on complexity level
- →Suggest focus areas and key concerns for ticket resolution
How it works
The skill analyzes ticket content by extracting keywords, calculating a score based on technical and scope factors, and applying label overrides to determine a complexity level. It then recommends workflow phases and actions.
Inputs & outputs
When to use analyze-ticket
- →Assess ticket scope
- →Determine planning requirements
- →Identify need for architecture review
- →Categorize technical debt complexity
About analyze-ticket
Evaluates ticket complexity based on multi-component changes, schema updates, and security implications. Assigns a score to determine the required exploration depth.
Internal helper called by /resolve. Analyzes ticket complexity (SIMPLE, MEDIUM, COMPLEX) to determine exploration depth and planning approach. Not intended for direct invocation.
When not to use it
- →When the skill is not called internally by /resolve
- →When direct invocation by a user is intended
Limitations
- →The skill is intended for internal invocation by /resolve.
- →The skill relies on predefined scoring factors and detection signals.
- →The skill's configuration for labels and thresholds is external.
How it compares
This skill provides a structured, score-based method for analyzing ticket complexity and recommending specific workflow phases, unlike a manual or ad-hoc assessment.
Compared to similar skills
analyze-ticket side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| analyze-ticket (this skill) | 0 | 3mo | No flags | Advanced |
| drift-analysis | 2 | 7mo | No flags | Intermediate |
| planning | 2 | 4mo | No flags | Intermediate |
| gsd-plan-checker | 1 | 6mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
drift-analysis
avifenesh
This skill should be used when the user asks about "plan drift", "reality check", "comparing docs to code", "project state analysis", "roadmap alignment", "implementation gaps", or needs guidance on identifying discrepancies between documented plans and actual implementation state.
planning
citypaul
Planning work in small, known-good increments. Use when starting significant work or breaking down complex tasks.
gsd-plan-checker
toonight
Validates plans before execution to catch issues early
feature-planning
mhattingpete
Break down feature requests into detailed, implementable plans with clear tasks. Use when user requests a new feature, enhancement, or complex change.
linear-ticket
useautumn
Refine rough engineering thoughts into structured Linear tickets with GitHub permalinks
design-to-issues
cloverich
Creates a GitHub epic and child issues from a design document's implementation plan. Use when a design doc has a reviewed plan section ready to be converted into trackable work.