open-ticket
Turn an understood problem into a staged unit of work: one AskUserQuestion interview (slug, tracker GitHub / Jira / both / none), then the ticket directory, a Findings rollup from the lets-investigate ledger or what-we-know, the GitHub issue and/or Jira ticket (a draft file when the CLI is absent) with a checked tracker body, the branch, ticket.yml with derived model routing, and a validated ticket row in the state database. Ends by asking whether to plan now (game-plan), go straight to one-shot, or hand off (baton-pass). Not for starting the implementation itself (game-plan or one-shot), and not for handing off an existing ticket (baton-pass).
Pinned to revision 112e73167d38, so it is the text this page describes rather than whatever the author pushed since.
Pre-approved tools experimental
Experimental field. Support varies between clients, so this list is what the author declared, not what your client will enforce.
- AskUserQuestion
- mcp__plugin_mightymodels_mighty-mcp__investigation_knowns
- mcp__plugin_mightymodels_mighty-mcp__investigation_list
- mcp__plugin_mightymodels_mighty-mcp__ticket_write
- mcp__plugin_mightymodels_mighty-mcp__ticket_validate
Files
- skills/open-ticket/SKILL.md
- skills/open-ticket/assets/tracker-body.md
- skills/open-ticket/evals/evals.json
- skills/open-ticket/references/mightymodels-dir.md
- skills/open-ticket/references/ticket-schema.md
- skills/open-ticket/scripts/humanize_tracker_body.py
Every link opens the file at its source, pinned to the revision this page describes.