stick-the-landing
Close an mightymodels sprint: gate the push on task_ready, push, open the PR with a checked body, have gitty-up watch CI, and route each failing check as a recorded C task (mechanical fixes to an engineer residual, then architect once; non-obvious causes to whats-broken), treating CI as the hard gate at every new HEAD. On green, ask through AskUserQuestion whether to review now (review-circus) or hand off (baton-pass). Not for Jira sprint operations, not the review itself (review-circus), and not for mid-sprint work (agents-assemble owns the loop).
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__task_ready
- mcp__plugin_mightymodels_mighty-mcp__task_start
- mcp__plugin_mightymodels_mighty-mcp__task_verify
- mcp__plugin_mightymodels_mighty-mcp__task_mark
- mcp__plugin_mightymodels_mighty-mcp__task_show
Files
Every link opens the file at its source, pinned to the revision this page describes.