ticket-planning
Drafts, classifies, and optionally creates tickets from an initiative plan. Use when the user provides a plan and wants ticket drafts, wants help shaping a plan into tickets, wants sprint-placement guidance, or wants tickets created in an issue tracker after the plan is approved.
85
81%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description that clearly articulates specific capabilities (drafting, classifying, creating tickets), uses natural trigger terms users would employ, and explicitly states both what the skill does and when to use it. The description is concise yet comprehensive, covering the full workflow from plan intake through ticket creation in an issue tracker.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Drafts, classifies, and optionally creates tickets from an initiative plan.' Also mentions sprint-placement guidance and shaping plans into tickets, which are distinct concrete capabilities. | 3 / 3 |
Completeness | Clearly answers both what ('Drafts, classifies, and optionally creates tickets from an initiative plan') and when ('Use when the user provides a plan and wants ticket drafts, wants help shaping a plan into tickets, wants sprint-placement guidance, or wants tickets created in an issue tracker after the plan is approved'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'plan', 'ticket drafts', 'tickets', 'sprint-placement', 'issue tracker', 'approved'. These cover common variations of how users would describe this workflow. | 3 / 3 |
Distinctiveness Conflict Risk | The combination of initiative plans, ticket drafting/classification, sprint placement, and issue tracker creation carves out a clear niche. Unlikely to conflict with generic project management or coding skills due to the specific workflow described. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
62%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured planning skill with a clear 6-step workflow and good decision logic for sprint placement and ticket creation. Its main weakness is the lack of concrete examples — a sample ticket draft or a before/after transformation would significantly improve actionability. The content is mostly concise but has some redundancy between the introduction and the 'Use This Skill When' section.
Suggestions
Add a concrete example showing a mini plan being transformed into 1-2 sample ticket drafts using the standard structure (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes)
Remove or consolidate the 'Use This Skill When' section since it largely duplicates the bullet list at the top of the file
Add a brief example of the creation output format (e.g., a sample table of created issue keys, status, sprint) to make the output pattern concrete rather than descriptive
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some redundancy — the 'Use This Skill When' section repeats the trigger conditions already stated at the top, and the 'Reduce redundancy' section (Step 5) is somewhat ironic given it could be folded into Step 4's drafting instructions. The classification table and workflow steps are well-structured but could be tighter. | 2 / 3 |
Actionability | Provides a clear structured workflow with specific attributes, title conventions, and section ordering, but lacks concrete examples — no sample ticket draft, no example API call for issue creation, no before/after showing how a plan becomes tickets. The guidance is specific but not executable/copy-paste ready. | 2 / 3 |
Workflow Clarity | The 6-step workflow is clearly sequenced with logical progression from normalization through classification, drafting, redundancy reduction, and conditional creation. Includes validation checkpoints (verify project/board details, validate one issue first if uncertain, create only after approval), and the sprint placement heuristics provide clear decision logic. | 3 / 3 |
Progressive Disclosure | Content is reasonably well-organized with clear sections and an integration table pointing to related skills, but the skill is somewhat long and monolithic. The classification table, sprint heuristics, and creation guidance could potentially be split into referenced files. However, the inline content is all relevant and not excessively deep. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- igmarin/rails-agent-skills
- Commit
ae8ea63
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.