From aai-pm-linear
Generates actionable implementation plans for Linear tickets by gathering full context, exploring codebase patterns with rg, clarifying ambiguities, and outlining steps.
npx claudepluginhub bradtaylorsf/alphaagent-teamThis skill uses the workspace's default tool permissions.
Transform Linear tickets into actionable implementation plans through systematic investigation and collaborative planning.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Transform Linear tickets into actionable implementation plans through systematic investigation and collaborative planning.
Transform uncertainty into clarity by:
# Get complete ticket information
mcp__linear__get_issue --id "$ticket_id"
Parse from ticket:
Flag for clarification:
# Find existing related code
rg "keyword" --type ts --files-with-matches
# Find similar implementations
rg "pattern-keyword" --type ts -A 5
For each relevant file:
Extract from codebase:
# Review CLAUDE.md for requirements
cat CLAUDE.md | grep -A 10 "relevant-section"
Present 2-4 questions at a time with:
Format:
### Question: [Topic]
**Context**: [What codebase exploration revealed]
**Options**:
A) **[Option Name]** - [Description]
- Pros: [Benefits]
- Cons: [Drawbacks]
B) **[Option Name]** - [Description]
- Pros: [Benefits]
- Cons: [Drawbacks]
**Recommendation**: Option [X] because [reasoning]
**Your choice?** (A/B)
# Implementation Plan: {ticket-id} - {title}
## Overview
[1-2 sentence summary]
## Approach
[3-5 bullet points on technical approach]
## Decisions
[List of decisions made during clarification]
## Complexity
[Simple/Moderate/Complex with justification]
For each step:
### Step N: [Title] (Est. complexity)
**What**: [Brief description]
**File(s)**: [Paths]
**Key points**:
- [Critical implementation detail]
- [Pattern to follow]
**Dependencies**: Step [X]
**Testing**: [How to verify]
Define:
| Risk | Impact | Mitigation |
|---|---|---|
| [Risk] | High/Med/Low | [Strategy] |
Checklist covering:
## Git Strategy
**Branch**: {type}/{ticket-id}-{sanitized-title}
**Base**: main or staging
**Commits** (logical units):
1. `feat({ticket}): [description]`
2. `test({ticket}): [description]`
3. `docs({ticket}): [description]`
Used by agents:
linear-ticket-planner - Autonomous ticket planninglinear-ticket-creator - Ticket creation with explorationBefore completing plan: