tom555my/dev-kit
Overview
This skill generates well-structured development tickets under .dev-kit/tickets/ based on user requests, performs dependency and prerequisite analysis, and organizes work into an ordered ticket hierarchy. It stops after producing tickets and awaits user confirmation before any implementation. When input is missing or ambiguous, it creates prerequisite clarification tickets to unblock planning.
How this skill works
I parse the user's request to identify the desired outcome, beneficiaries, and scope. Then I inspect project docs (.dev-kit/docs/PROJECT.md and .dev-kit/docs/TECH.md) for missing architecture decisions or infrastructure; I create prerequisite tickets for any unmet foundations. Finally, I break work into atomic tickets, link dependencies, and write one Markdown ticket file per outcome in .dev-kit/tickets, using the project's ticket-numbering script to sequence them.
When to use it
- Breaking down a new feature request into implementation-ready tickets
- Creating bug reports with clear acceptance criteria and dependencies
- Planning work from a high-level spec or product brief
- Organizing development tasks and ordering prerequisites before implementation
- When you need explicit prerequisite or design-decision tickets before coding
Best practices
- Provide a clear user story, scope boundaries, and acceptance hints when requesting tickets
- Attach relevant doc links (designs, TECH.md, PROJECT.md, Figma) to avoid placeholder resources
- Confirm project code (XXXX) via /dev-kit.init so tickets get proper filenames and sequencing
- Review produced ticket order and approve prerequisite tickets before asking for implementation
- Keep one outcome per ticket and call out blockers explicitly using ticket references
Example use cases
- User: “Implement logo generation with Stripe billing” → outputs decision tickets (Stripe choice), infra tickets (payments webhook), then feature tickets
- User: “Fix credit decrement bug” → generates investigation ticket, bug fix ticket, and audit-logging prerequisite if missing
- User: “Plan GenAI integration” → creates provider decision ticket, API layer ticket, and client integration tickets in order
- User: “Break down product spec into tasks” → returns an ordered ticket list with dependencies and acceptance criteria
FAQ
I generate a prerequisite clarification ticket that asks for missing inputs (scope, users, success criteria, relevant docs) and stop. You should provide answers before I create feature tickets.
Will you implement the tickets you create?
No. I only generate and document tickets. Implementation begins only if you explicitly request “implement ticket #XXXX”.
4 skills
This skill generates structured tickets in .dev-kit/tickets from user requests, analyzes dependencies and prerequisites, and outlines ticket structure for
This skill updates and consolidates .dev-kit/docs and .dev-kit/knowledge by validating against the codebase and generating a change report.
This skill reviews completed tickets by verifying implementation against user stories and acceptance criteria using code analysis tools.
This skill autonomously reads and implements tickets from .dev-kit/tickets, ensuring acceptance criteria are met and moved to completed when done.
