design-jira-state-analyzer
Designs and implements state transition analysis systems for tracking time spent in different states. Use when analyzing workflows with state changes (Jira, GitHub PRs, deployments, support tickets, etc.). Covers state machine fundamentals, temporal calculations, bottleneck detection, and business metrics. Trigger keywords: "state analysis", "duration tracking", "workflow metrics", "bottleneck", "cycle time", "state transitions", "time in status", "how long", "state duration", "workflow performance", "state machine", "changelog analysis", "SLA tracking", "process metrics".
npx skills add majiayu000/claude-skill-registry --skill design-jira-state-analyzer --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Design Jira State Analyzer ## When to Use This Skill **Explicit Triggers:** - "Analyze state transitions in Jira" - "Calculate time spent in each status" - "Find workflow bottlenecks" - "Track cycle time for tickets" - "Measure how long tickets stay in review" - "Analyze workflow performance" - "Design a state analyzer" - "Calculate business hours in status" **Implicit Triggers:** - Questions about "how long does it take" for workflow stages - Requests for SLA tracking or compliance analysis - Need to optimize process flow or reduce delays - Questions about which states slow down delivery - Requests to measure team velocity or throughput - Need to analyze deployment pipeline duration **Use This Skill When:** - Building systems to track state changes over time - Analyzing workflows with discrete states (Jira, GitHub PRs, deployments, support tickets) - Calculating temporal metrics (cycle time, lead time, flow efficiency) - Detecting bottlenecks in multi-stage processes - Implementing SLA monitoring and compliance tracking - Extracting insights from audit logs or changelogs **Do NOT Use This Skill When:** - You need real-time event processing (use stream processing instead) - Data
- When to Use This Skill
- What This Skill Does
- Quick Start
- Instructions
- Step 1: Understand State Machines and Transitions
- Step 2: Extract State Transitions from Audit Logs
- Step 3: Calculate Duration Between Transitions
- Step 4: Detect Bottlenecks
- Step 5: Analyze Patterns and Metrics
- Step 6: Export and Communicate Results
- Step 7: Extend for Your Use Case
- Examples
- Example 1: Analyze Single Jira Issue
- Example 2: Find Bottlenecks Across Project
Export issues with changelog uv run jira-tool search "project = PROJ" --expand changelog --format json -o issues.json Analyze state durations uv run jira-tool analyze state-durations issues.json -o durations.csv --business-hours Get issue with changelog uv run jira-tool get PROJ-123 Or analyze via CLI (shorter version) uv run jira-tool search "key = PROJ-123" --expand changelog --format json -o issue.json uv run jira-tool analyze state-durations issue.json -o durations.csv Export all issues from last sprint with changelog
What does the design-jira-state-analyzer skill do?
Designs and implements state transition analysis systems for tracking time spent in different states. Use when analyzing workflows with state changes (Jira, GitHub PRs, deployments, support tickets, etc.). Covers state machine fundamentals, temporal calculations, bottleneck detection, and business metrics. Trigger keywords: "state analysis", "duration tracking", "workflow metrics", "bottleneck", "cycle time", "state transitions", "time in status", "how long", "state duration", "workflow performance", "state machine", "changelog analysis", "SLA tracking", "process metrics".
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill design-jira-state-analyzer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.