Create a Linear MVP parent issue with nested sub-issues for a new feature
Creates a comprehensive Linear MVP feature with a parent issue and nested sub-issues. Investigates your codebase in parallel to understand existing patterns, then guides you through iterative clarification before generating a complete feature plan with atomic sub-issues.
/plugin marketplace add jclfocused/claude-agents/plugin install linear-planning-workflow@laserfocused-plugins<feature description>You are about to create a comprehensive Linear feature with a parent issue and nested sub-issues.
$ARGUMENTS
First, list all existing Linear projects with their current status:
mcp__linear__list_projects with limit: 250 to fetch all projectsstatus.name is "Completed" or "Canceled"AskUserQuestion to prompt the user with all active/planned projects:
{ label: "No Project Association", description: "Create issues without linking to any project" }label: "[Project Name] - [Status Name]"description: Project summary if available (truncate to 100 chars), or "No description"Before creating the feature issues, investigate the codebase using parallel code-explorer agents:
Dynamically Identify Investigation Areas: Based on the feature description, determine which 2-4 specific areas of the codebase need investigation:
Spin Up Parallel Code Explorer Agents: Use the Task tool with subagent_type='feature-dev:code-explorer' to launch multiple agents in parallel:
feature-dev:code-explorer (plugin prefix required)Consolidate Investigation Findings: After all parallel agents complete, review and consolidate their findings into a structured summary that will be passed to the linear-mvp-project-creator agent.
Use the linear-planning-workflow:linear-mvp-project-creator agent to create this feature. Pass:
IMPORTANT: The agent will ensure the parent issue is labeled with "Feature Root" for easy identification and filtering of all root feature issues.
The agent will:
Iterative Clarification Loop - The agent will ask you clarifying questions to ensure full understanding:
Create a parent issue with description structured as:
Create nested issues following these principles:
MVP SCOPE: Focus on what makes the feature functional, NOT comprehensive solutions. Ship something that works, iterate later.
REFACTOR AS YOU TOUCH: If bad patterns are found, create refactor issues to fix them as we work in that area.
ATOMIC DESIGN FOR UI: Use existing components or create new ones following atomic design principles (atoms/molecules/organisms).
LINEAR DISCIPLINE (will be in parent issue description):
Begin by listing projects and prompting for selection.