Content
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is lean, highly actionable, and well-organized for a single-file guidance skill, with concrete JQL and Jira-specific detail throughout. The one gap is the lack of explicit validation/feedback loops for risky operations like bulk workflow transitions.
Suggestions
Add a short validation step for risky operations, e.g., before bulk-transitioning issues or moving an issue backward in the workflow, confirm the change in a comment and re-check board status — a 'validate -> fix -> retry' loop.
Optionally include a brief sequenced workflow (e.g., create epic -> break into stories -> groom -> add to sprint -> track via JQL) with explicit checkpoints to lift workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean bullets with no padded explanations of concepts Claude already knows (it never explains what Jira, sprints, or epics are), and the JQL section is tight and direct. It is not 2 because there is no unnecessary prose that could be tightened. | 3 / 3 |
Actionability | It provides copy-paste-ready JQL queries and concrete specifics — the Epic > Story > Task > Sub-task hierarchy, named link types ('blocks', 'is blocked by', 'relates to', 'duplicates'), exact workflow states, and a named good/bad title example. It is not 2 because the guidance is complete and executable rather than pseudocode or abstract. | 3 / 3 |
Workflow Clarity | Sections are topically organized with implied sequencing (e.g., sprint-planning considerations), but there are no explicit validation checkpoints or feedback loops for potentially destructive or batch operations such as bulk transitions or moving issues backward. It is not 1 because steps/sequence are present, and not 3 because validation and error-recovery loops are missing. | 2 / 3 |
Progressive Disclosure | At ~48 body lines with no need for external references, the well-organized sections (Key Principles, Issue Management, Sprint Planning, JQL Queries, Workflow Best Practices, Pitfalls) satisfy the simple-skills note that progressive disclosure can score 3 with just clear organization. It is not 2 because there is no inline content that should be split out. | 3 / 3 |
Total | 11 / 12 Passed |