Create a Jira Story with flat Subtasks for a new feature
Creates a Jira Story with flat Subtasks for a new feature based on user input.
/plugin marketplace add jclfocused/claude-agents/plugin install jira-planning-workflow@laserfocused-plugins<feature description>You are about to create a comprehensive Jira feature with a parent Story and flat Subtasks.
$ARGUMENTS
First, identify the current user for assignment:
mcp__mcp-atlassian__jira_search with JQL assignee = currentUser() and limit: 1display_name and email from the resultGet available sprints and let user choose:
Use mcp__mcp-atlassian__jira_get_agile_boards to get boards
For each board (typically just one), use mcp__mcp-atlassian__jira_get_sprints_from_board with state: "active" to get active sprints
Also get future sprints with state: "future" if needed
Use AskUserQuestion to prompt the user:
{ label: "[Sprint Name]", description: "[State]: [Start Date] - [End Date]" }{ label: "No sprint (Backlog)", description: "Create issues without sprint assignment" }If user selects a sprint:
If user selects "No sprint":
AskUserQuestion to ask about team:
{ label: "No team assignment", description: "Create issues without team ownership" }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.
Use the jira-planning-workflow:jira-mvp-story-creator agent to create this feature. Pass:
The agent will:
MVP SCOPE: Focus on what makes the feature functional, NOT comprehensive solutions.
FLAT SUBTASKS: Jira subtasks cannot have nested subtasks. Use naming conventions to show logical grouping:
TEAM + SPRINT: Both customfield_10001 (Team) and customfield_10020 (Sprint) should be set on all issues when provided.
JIRA DISCIPLINE (will be in Story description):
Begin by getting the current user and prompting for sprint selection.