Create a complete Linear project from a natural-language description. Use this skill when the user wants to plan a project, set up a project in Linear, scaffold project milestones and issues, bootstrap a project plan, or create a structured project from a description. Also use when the user mentions creating epics, milestones, or issue hierarchies in Linear.
npx claudepluginhub toolwright-adk/toolwright-monorepo --plugin linear-project-managerThis skill is limited to using the following tools:
Create a fully structured Linear project — milestones, epics, issues, labels, and dependency chains — from a plain-English description.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Create a fully structured Linear project — milestones, epics, issues, labels, and dependency chains — from a plain-English description.
Before starting, confirm the linear-bootstrap MCP tools are available by checking that mcp__linear-bootstrap__list-teams is callable. Attempt to list teams.
If the tool is not found or the call fails:
The linear-bootstrap MCP server is not running. To fix this:
- Check
/pluginfor MCP server errors- Verify the server is configured in
.mcp.jsonwith validLINEAR_API_KEY,LLM_API_KEY,LLM_BASE_URL, andLLM_MODEL- Try restarting Claude Code
- Test manually:
npx @toolwright-adk/linear-bootstrap(orbunxif npx is broken)
Stop here if the server is unavailable — do not attempt to proceed without it.
Use the team list from the prerequisite check. If there is only one team, use it. If there are multiple, ask the user which team to target.
The server automatically reads your team's existing labels, workflow states, and active projects before generating a plan. No extra step needed.
Use the description from $ARGUMENTS if provided. Otherwise, ask the user what project they want to create.
Determine the project type from the description:
Determine the complexity:
Generate a project plan using the description, team, project type, and complexity. You will receive a plan reference and a summary with counts of milestones, epics, issues, and estimated points.
Show the user the summary. Ask: "Does this look right, or should I adjust the scope?"
If generation fails: Report the error to the user. Common causes:
LLM_API_KEYLLM_BASE_URLValidate the plan for structural issues (circular dependencies, orphaned references, etc.). If there are errors, report them and stop. If there are only warnings, show them and ask whether to proceed.
Create the project in Linear using the plan reference and team. Report what was created:
If creation partially fails: The server tracks what was created vs. what failed. Report both lists to the user. The successfully created items remain in Linear — do not retry the entire bootstrap. Instead, suggest using add-epic to fill in missing pieces, or fixing the issue in Linear directly.
If the project already exists: The server detects this and returns the existing project ID without making changes. Report this to the user.
If the user says "just do it," "don't ask," or otherwise indicates they want unattended creation, use generate-and-bootstrap to generate the plan and create the project in a single step without intermediate review.
User: /linear-bootstrap CLI tool for managing database migrations
Agent: Found team "Engineering" (ENG). I'll generate a feature project plan...
Plan ready: 3 milestones, 4 epics, 14 issues, ~28 points.
Does this look right, or should I adjust the scope?
User: Looks good, go ahead.
Agent: Created "Database Migration CLI" in Linear:
- 3 milestones, 4 epics, 14 issues, 8 dependencies
- Reused 5 existing labels, created 2 new ones
User: /linear-bootstrap just do it — webhook subscriptions API
Agent: Created "Webhook Subscriptions API" in Linear:
- 4 milestones (API design → GA), 5 epics, 18 issues
- 12 dependencies, 6 labels reused
User: /linear-bootstrap shared logging library for the monorepo, infrastructure type
Agent: Found team "Platform" (PLT). Generating an infrastructure project plan...
Plan ready: 2 milestones (Core library ready → Org-wide adoption),
4 epics, 14 issues.
Proceed?