sdk: Command for Claude Code

Create implementation tickets for the Linear project specified in $ARGUMENTS.

Steps

1. Fetch project details using mcp__linear__get_project with the project name from $ARGUMENTS
2. Fetch team info using mcp__linear__list_teams to get the team ID for creating issues
3. Analyze the project description to understand:
   • The overall goal and scope
   • Key implementation areas (database, API, UI, etc.)
   • Dependencies between components
4. Break down into atomic tickets following these principles:
   • Each ticket should be completable by a single agent in isolation
   • Tickets should have clear inputs and outputs
   • Dependencies should be explicit (use Linear's blocking relations)
   • Group by layer: Schema → Types → API → Backend Logic → UI
5. Present the plan for approval - Show the user the complete ticket breakdown:
   • Display each planned ticket with title and description summary
   • Show the dependency graph (what blocks what)
   • Highlight parallelization opportunities
   • Ask the user to approve before proceeding
6. Wait for user approval - Use AskUserQuestion to get explicit confirmation:
   • Option to approve and create all tickets
   • Option to request modifications to the plan
   • Option to cancel
7. Create tickets in Linear (only after approval) using mcp__linear__create_issue for each ticket
8. Set up dependencies using the blocks parameter when creating issues
9. Summarize the created tickets to the user

Plan Presentation Format

Before creating tickets, present the plan to the user in this format:

## Proposed Implementation Plan for [Project Name]

### Summary
[Brief overview of the approach and total number of tickets]

### Ticket Breakdown

#### Layer 1: Database (X tickets)
1. **[Title]** - [One-line description]
2. **[Title]** - [One-line description]

#### Layer 2: Types (X tickets)
3. **[Title]** - [One-line description]
   - Blocked by: #1

#### Layer 3: API (X tickets)
4. **[Title]** - [One-line description]
   - Blocked by: #1, #3

[Continue for all layers...]

### Dependency Graph

    #1 Database Schema
     ├── #3 Types (blocked by #1)
     │    └── #5 Service (blocked by #3, #4)
     └── #4 API Endpoints (blocked by #1)
          └── #6 UI Components (blocked by #4)
    #2 Config Setup (independent)

### Parallelization Opportunities
- **Phase 1** (can start immediately): #1, #2
- **Phase 2** (after Phase 1): #3, #4
- **Phase 3** (after Phase 2): #5, #6