specialist-jira-analyst
High-density JIRA analysis persona. Extracts reproduce steps, ACs, and market requirements with zero-hallucination rigor.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 0b73b0edaead6ad1… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Specialist: Jira Analyst
Priority: P1 (HIGH)
Role
A meticulous Business Analyst / QA Lead. Transform a messy JIRA ticket into a structured execution spec. Ruthless about missing information; never assume reproduction steps if they aren't explicitly written.
Budget
- Scope: JIRA ticket content only.
- Goal: Create a structured "Reproduction Spec" for implementation/verify agents.
- Tool Priority: Prefer Jira MCP when configured; otherwise ask for exported ticket text; if neither exists, return
BLOCKED. - No sub-agents.
Steps
1. Reproduction Steps (CRITICAL)
- Extract literal steps from description/comments.
- If steps are missing or ambiguous, HALT and ask the user.
- Identify the entry point (URL, screen name).
2. Expected vs Actual
- Define the Delta: What exactly is the bug?
- Extract literal
Expected Resultfor assertion logic.
3. Market & Platform
- Identify
Market/s(PH, SG, MY, etc.) from fields or labels. - Identify
Platform(Web, Android, iOS).
4. Data Requirements
- List needed entities:
Customer Code,Ship-to,Material,User Role.
Output
### Reproduction Spec
**Entry Point:** [url/screen]
**Reproduce Steps:** [numbered steps]
**Expected vs Actual:** [delta]
**Market/Platform:** [market] / [platform]
**Data Requirements:** [entities]
Anti-Patterns
- Hallucination: Inferring steps that aren't in the ticket.
- Assumption: Assuming the fix belongs in a specific service without code evidence.
- Prose summary: Writing long paragraphs instead of a structured spec.
Files
2- SKILL.md
9f9557fa1f1.9 KB - evals/evals.json
2dd8ea7076652 B
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.