igmarin/ticket-planning
skills/planning/ticket-planning/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add igmarin/rails-agent-skills ticket-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 7, 2026, 3:01 AM142.1s4 files scanned
SKILL.md
- name:
- ticket-planning
- license:
- MIT
- description:
- >
- version:
- 1.0.0
- user-invocable:
- true
Ticket Planning
Normalize inputs, classify each work item, apply title conventions, draft tickets in a standard structure, then either return markdown drafts or create issues in the issue tracker after explicit approval.
See EXAMPLES.md for a complete plan → ticket draft example.
Workflow
1. Normalize the initiative
Extract planning inputs:
- initiative/theme
- project/board
- whether the request is draft-only or create-in-tracker
- default sprint or backlog bucket
- constraints on issue types, prefixes, epic, labels, components, status, or sprint
If the user already has a plan, do not re-plan unless there is a material gap.
2. Classify each ticket before drafting it
Assign these core planning attributes to each ticket:
| Attribute | Values |
|-----------|--------|
| type | Story | Task |
| area | backend | web | mobile | cross-platform | external |
| execution_order | foundation | api | client | follow-up |
| dependency_level | unblocked | blocked |
| target_bucket | ready-to-refine | next-dev-sprint | later |
Additional attributes to apply when relevant: coordination_need (single-team | multi-team), external_dependency (yes | no), urgency (normal | priority).
Backend/API enablers generally come before dependent web/mobile tickets.
3. Apply title conventions
Use these prefixes:
BE |for backendFE |for web / frontendMobile |for mobile
When writing the ticket title, leave a space after the |.
Do not add those prefixes to tickets that are not owned by those areas unless the user explicitly wants that.
4. Draft tickets in the standard structure
Use this section order:
| Section | Job | |---------|-----| | Summary | State the outcome | | Background | Explain why | | Acceptance Criteria | List observable criteria | | Dependencies | Note blockers | | Technical Notes | Implementation details that affect sequencing or scoping only |
Keep the main sections business-facing.
5. Output: drafts or create in the issue tracker
Draft-only:
- Return markdown tickets following the five-section structure (Summary, Background, Acceptance Criteria, Dependencies, Technical Notes) with the appropriate area prefix in the title.
- Keep titles, issue types, and dependencies explicit.
- Include brief sequencing notes when helpful.
- See EXAMPLES.md for a full plan → ticket draft with classification applied.
Create in issue tracker:
- Verify the target project/board details first.
- Confirm required fields: project, issue type, sprint, status behavior, epic, labels, components.
- Create issues only after the plan is considered approved enough.
- Use whatever integration the user has (API, MCP, UI); do not assume credentials in the repo.
- Validate one issue before bulk-creating if the sprint field or workflow behavior is uncertain.
- After creation, report: created issue keys, confirmed status, confirmed sprint/bucket, and any assumptions used.
Example field shape for MCP/API creation:
{
"project": "<project-key>",
"issuetype": "Story",
"summary": "BE | Enable payment webhook processing",
"description": "<full ticket body>",
"labels": ["payments", "backend"],
"components": ["payments-service"],
"sprint": { "id": "<sprint-id>" },
"epic": "<epic-key>"
}
Omit fields the project does not require. Confirm actual field names from the tracker's create-metadata endpoint before issuing the call. Do not set status on create — use the project's default initial status.
Sprint Placement Heuristics
Defaults unless the user overrides:
foundationandapitickets → placed before all dependentclientticketsclienttickets → blocked until the API surface they depend on is stableexternalconfirmation tickets → excluded from active build sprintsfollow-uptickets →ready-to-refineorlateruntil their enabling work is complete- Named future sprints (e.g. Ready to Refine) → treat as a planning bucket, not an execution commitment
Integration
| Skill | When to chain | |-------|----------------| | generate-tasks | After tasks exist or in parallel — same initiative can feed ticket breakdown | | create-prd | When tickets should align with PRD scope and acceptance themes |
Assets
- assets/ticket-samples/sample_issue.md
Related Skills
igmarin/rails-agent-skills
development
VerifiedTrustedCommunity
Entry point for Rails development workflows covering TDD, RSpec, Service Objects, DDD, GraphQL, Engines, and Code Quality. Use when the user asks about Ruby on Rails development patterns, needs RSpec test suites generated, wants service objects scaffolded, is setting up GraphQL schemas, performing Rails code review, refactoring .rb files, working with domain-driven design, implementing background jobs, conducting Rails security checks, or building Rails engines. Generates RSpec tests, structures service objects, enforces TDD workflows, configures GraphQL schemas, and coordinates domain-driven design patterns. Trigger keywords: Rails, RSpec, TDD, Rails testing, Rails refactor, Rails API, Rails code review, domain driven design, service objects, GraphQL, Rails engine, Ruby, .rb, background jobs, Rails migrations, Rails security check.
21SKILL.mdUpdated May 18, 2026
igmarin/release-engine
development
VerifiedTrustedCommunity
Use when shipping a Rails engine gem — FIRST run full test suite (`bundle exec rspec`) and fix ALL failures, verify gemspec metadata and dependencies match tested Rails/Ruby versions, dry-run: `gem build *.gemspec && gem push --dry-run *.gem` and verify contents, generate CHANGELOG.md organized by category (added/changed/deprecated/removed/fixed), produce step-by-step upgrade notes with before/after code, set semantic version in `lib/[engine_name]/version.rb`, document deprecations with migration paths, load release assets conditionally and state which one informed the output. Trigger words: version bump, changelog, deprecation, gemspec, upgrade, release, publish gem, ship gem.
21SKILL.mdUpdated May 9, 2026
igmarin/tdd
development
VerifiedTrustedCommunity
Orchestrates the full Rails TDD cycle with hard gates: test MUST exist, be run, and FAIL for the correct reason (e.g. undefined method, not syntax error) before any implementation code — propose minimal implementation and wait for user approval → verify test PASSES → run full suite with rubocop, brakeman, rspec all green → produce YARD documentation and self-reviewed PR; phases context/test design→implementation→iterate→finish. Use when practicing test-driven development, red-green-refactor, TDD workflow, writing tests before code, adding tests first, or building a Rails feature where specs must gate implementation.
19SKILL.mdUpdated Jun 5, 2026
igmarin/setup
development
VerifiedTrustedCommunity
Complete Rails project setup loop with hard gates: verify Ruby version matches .ruby-version, Bundler installed, database connection successful, all env vars loaded, and ALL external CI actions pinned to immutable commit SHAs (never mutable tags like @v4) → configure CI/CD pipeline with linting, testing, and security scanning → validate end-to-end with bundle install, db:create, db:migrate, rspec, and write SETUP_CHECKLIST.md; phases context/onboarding→CI/CD configuration→environment validation. Use when starting a new Rails project, running `rails new`, configuring a Gemfile or .ruby-version, setting up a development environment, or wiring up CI/CD for a Ruby on Rails app. Trigger: setup project, new Rails app, configure CI/CD, dev environment setup, rails new, Gemfile setup, .ruby-version, Ruby on Rails project bootstrap.
19SKILL.mdUpdated Jun 5, 2026