Stub

Create ticket stubs to capture ideas or bugs on the Kanban board.

Overview

Stubs are the initial form of all tickets - just enough information to capture an idea. This skill:

• Creates new stub tickets from descriptions
• Adopts existing Kanban items by creating ticket files for them
• Handles bugs with required structure (steps to reproduce, expected/actual results)
• Assigns sequential ticket IDs
• Updates the Kanban board with wiki-style links

Ticket Types

Stub (Generic)

For ideas that aren't yet classified as features, stories, or bugs. Requires only a title and 1-2 sentence description.

Bug

For defects that need fixing. Must have:

• Steps to reproduce (numbered list)
• Expected result
• Actual result

If any of these are missing, use AskUserQuestion to gather them before creating the ticket.

Workflow

1. Determine Intent

Identify what the user wants:

• Create new stub: User provides a description of an idea
• Create new bug: User describes a defect or problem
• Adopt existing item: User references an item already on the Kanban board

2. Gather Information

For new stubs:

• Extract title and description from user input
• If description is too vague (less than a sentence), ask for clarification

For bugs:

• Extract or ask for: steps to reproduce, expected result, actual result
• All three are required - do not create bug ticket without them

For adopting existing items:

• Read the Kanban board at .agent/project-docs/MIMIR Kanban.md
• Find the matching item in the Ideas column
• Use the item text as the title
• Ask user for description (stubs) or bug details

3. Generate Ticket ID

• Scan .agent/project-docs/Tickets/ for existing ticket files
• Extract IDs matching pattern {PREFIX}-NNN-*
• Use project ticket prefix from CLAUDE.md (default: MIMIR)
• Increment highest found ID by 1 (or start at 001)
• Format: {PREFIX}-{NNN} (e.g., MIMIR-001)

4. Create Ticket File

Generate filename: {ID}-{kebab-case-title}.md

Use appropriate template:

• Generic stub: stub-template.md
• Bug: bug-template.md

Write to .agent/project-docs/Tickets/

5. Update Kanban Board

Read .agent/project-docs/MIMIR Kanban.md

For new items: Add to Ideas column:

- [ ] [[Tickets/{filename}|{Title}]]

For adopted items: Replace the plain text item with the wiki link:

# Before

- [ ] Setup LLM Access system

# After

- [ ] [[Tickets/MIMIR-001-setup-llm-access|Setup LLM Access system]]

Write updated Kanban file.

6. Confirm Creation

Report to user:

• Ticket ID and title
• File path created
• Kanban board updated

Key Rules

• Always ask clarifying questions if information is ambiguous or missing
• Bugs must have steps to reproduce, expected result, and actual result
• Never guess at reproduction steps - ask the user
• Ticket IDs are sequential and never reused
• All new stubs go in the Ideas column
• Use wiki-style links: [[Tickets/filename|Display Title]]

Examples

Creating a stub

User: "stub out an idea for user authentication"

1. Title: "User Authentication"
2. Ask for 1-2 sentence description
3. Generate ID (scan existing, increment)
4. Create MIMIR-001-user-authentication.md using stub template
5. Add to Kanban Ideas column
6. Report completion

Creating a bug

User: "I found a bug where the app crashes on startup"

1. Type: Bug
2. Ask: "What are the steps to reproduce this crash?"
3. Ask: "What did you expect to happen?"
4. Ask: "What actually happened?"
5. Create bug ticket with all required fields
6. Add to Kanban Ideas column

Adopting existing item

User: "create a ticket for 'Setup LLM Access system' on the board"

1. Read Kanban, find "Setup LLM Access system" in Ideas
2. Ask for description
3. Generate ID, create ticket file
4. Replace plain text with wiki link in Kanban
5. Report completion