with one click
hs-feature
Create a new feature ticket in Hot Sheet
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Create a new feature ticket in Hot Sheet
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Prep apple-fm for a major release — refresh the README so it advertises the current feature set, and review/revise the demo modes (the user captures the screenshots)
Read the Hot Sheet worklist and work through the current priority items
Run as a distributed worker — continuously claim, work, and release Up Next tickets
Create a new bug ticket in Hot Sheet
Create a new investigation ticket in Hot Sheet
Create a new issue ticket in Hot Sheet
| name | hs-feature |
| description | Create a new feature ticket in Hot Sheet |
| allowed-tools | Bash |
Create a new Hot Sheet feature ticket. New features to be implemented.
Parsing the input:
up_next to true and use the remaining text as the titleCreate the ticket — MCP tool (preferred when the channel is connected):
Call the hotsheet_create_ticket tool with { "title": "<TITLE>", "category": "feature", "up_next": <true|false> }. The tool is schema-validated and routes to the channel server's --data-dir so there's no chance of cross-project misrouting.
Fallback (curl):
curl -s -X POST http://localhost:4174/api/tickets \
-H "Content-Type: application/json" \
-H "X-Hotsheet-Secret: 372e8dd4dd24e8784714dd3bad03422e" \
-d '{"title": "<TITLE>", "defaults": {"category": "feature", "up_next": <true|false>}}'
If the request fails (connection refused or 403), re-read .hotsheet/settings.json for the current port and secret values — you may be connecting to the wrong Hot Sheet instance.
Report the created ticket number and title to the user.