Add structured work (epics with child issues) to an existing Linear project. Use when the user wants to expand a project's scope, add an epic, add a batch of related issues to a project, or says something like "add these issues to the project" with 3 or more items.
How this skill is triggered — by the user, by Claude, or both
Slash command
/linear-project-manager:linear-expandThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Add an epic with child issues to an existing project using `add-epic` — one call that gets parent/child structure, milestone wiring, and labels automatically.
Add an epic with child issues to an existing project using add-epic — one call that gets parent/child structure, milestone wiring, and labels automatically.
add-epic)mcp__linear__save_issue directly/linear-bootstrap insteadConfirm mcp__linear-bootstrap__add-epic is available. If not, tell the user the linear-bootstrap MCP server is not running and suggest troubleshooting.
Use $ARGUMENTS or ask the user which project to expand. Use mcp__linear__list_projects if needed.
Gather in parallel:
mcp__linear__get_project — project overviewmcp__linear__list_milestones — existing milestones (to wire the new epic to one)mcp__linear__list_issues — existing issues (to avoid duplicates and understand naming patterns)mcp__linear-bootstrap__introspect-workspace — team labels and workflow states (for label reuse)From the user's description, determine:
Show the user a summary: "I'll add epic 'Payment Retry Logic' with 5 issues to milestone 'M3: Checkout Flow'. Sound right?"
Use mcp__linear-bootstrap__add-epic with:
project_id — from step 2team_id — from the project's teamepic — the designed structuremilestone_id — from step 2label_ids — map of label name → ID from introspectionReport what was created: epic ID, child issue count, milestone, labels applied.
If add-epic fails partially, report what was created vs. what failed. The successfully created items remain in Linear.
User: /linear-expand Add payment retry handling to the Checkout Redesign project
Agent: Found project "Checkout Redesign" with 3 milestones.
I'll add to M3: Checkout Flow.
Epic: "Payment Retry Logic" (5 issues)
- Detect failed payment attempts (P1)
- Implement exponential backoff retry (P1)
- Add retry status UI component (P2)
- Send retry notification email (P3)
- Add retry metrics dashboard (P3)
Labels: "payments" (existing), "reliability" (existing)
Sound right?
User: Yes, go ahead.
Agent: Created epic "Payment Retry Logic" in Checkout Redesign:
- 5 child issues under M3: Checkout Flow
- Reused 2 existing labels
npx claudepluginhub toolwright-adk/toolwright-monorepo --plugin linear-project-managerManages Linear issues via MCP or GraphQL API: query by key, create/update, transition states, author/audit VantageEx epics, attach GitHub PRs.
Creates structured Linear tickets for project planning, feature breakdowns, and bug fixes. Uses Linear as an agent control plane with complete work briefs, status tracking, and dependency management.
Creates structured Linear issues (1 main + N sub-issues) with project linking, title prefixing, and labeling. Supports two workflows: Generic (code tasks) and PRD Pipeline (Korean-language product requirements with content strategy principles).