| name | issue-create |
| description | Quickly create a single issue from conversation context. Use when you want to create a bead, file an issue, track this as a bead, make a ticket for something, or capture a work item. Lightweight alternative to issue-plan for one piece of work without full planning. |
Quick Bead Creation
Create a single issue from the current conversation context. This is a lightweight alternative to issue-plan for when you need to quickly capture one piece of work.
The skill uses a two-phase approach: ideation happens on the main thread (extracting requirements, clarifying with the user), then a subagent handles the mechanical creation work (codebase exploration, formatting, br commands). This keeps the main conversation focused on what matters.
Context Sources
This command receives context from two sources:
- Conversation history - All messages above inform requirements, decisions, and scope
- Arguments - Additional instructions passed when invoking the command (see $ARGUMENTS at end)
Phase 1: Ideation (Main Thread)
Step 1: Extract from Conversation
Review the conversation history above to identify:
- What: The specific task or bug to address
- Why: The motivation or problem being solved
- Scope: What's included and excluded
- Acceptance criteria: How to know when it's done
- Known files: Any files already discussed or identified in conversation
If the user provided additional instructions below, incorporate those as well.
Step 2: Clarify Ambiguities
Before handing off to the subagent, use AskUserQuestion to clarify anything uncertain. Infer as much as possible from conversation context, but ask about:
Always infer from context, only ask if unclear: