/arn-code-batch-planning

name: arn-code-batch-planning
description: >-
  This skill should be used when the user says "batch planning", "batch plan",
  "arness batch planning", "arn-code-batch-planning", "plan multiple features",
  "plan all features", "plan unblocked features", "plan the backlog",
  "plan from backlog", "batch spec and plan", "plan next features",
  "sequential planning", "multi-feature plan", "plan the next batch",
  "plan these features", "batch plan GitHub issues", "batch plan from Jira",
  "plan issues in batch",
  or wants to plan multiple features from the greenfield Feature Tracker,
  GitHub issues, or Jira issues in a single session. Pre-analyzes all
  selected features in parallel, then guides sequential spec review with
  pipelined plan generation. This skill is
  typically invoked directly or after arn-brainstorming completes and
  chains to arn-code-batch-implement upon completion. For single-feature
  planning, arn-planning is the correct entry point.
version: 1.0.0

Arness Batch Planning

Plan multiple features in a single session with parallel pre-analysis and pipelined plan generation. Supports features from greenfield Feature Tracker (F-NNN), GitHub issues, Jira issues, or plain descriptions. Pre-analyzes all selected features in parallel using `arn-code-batch-analyzer` agents to generate draft specs, then guides the user through sequential review. Plans are generated in the background while the user reviews the next spec.

This skill is a **sequencer**. It MUST NOT duplicate sub-skill logic. All pipeline work is done by the invoked skills and agents (`arn-code-batch-analyzer`, `arn-code-feature-spec`, `arn-code-feature-planner`, `arn-code-save-plan`). Arness-code-batch-planning handles: source detection, feature selection, parallel pre-analysis orchestration, sequential spec review, pipelined plan generation, plan review, and chaining.

Pipeline position:

Sources:
  arn-spark (greenfield) -> feature-backlog.md ─┐
  GitHub issues ─────────────────────────────────┤
  Jira issues ───────────────────────────────────┤
                                                  v
                                  **arn-code-batch-planning**
                                    |
                                    +-- Step 2.5: scope assessment (score each feature → swift/standard/thorough)
                                    +-- Step 2.6: generate SWIFT/STANDARD plans (auto, no review)
                                    +-- Step 2.7: parallel arn-code-batch-analyzer (thorough only → draft specs)
                                    +-- Step 3: per thorough feature: arn-code-feature-spec (resume from draft)
                                    +-- Step 3.5: per thorough feature: plan review → save-plan
                                    |
                                    v
                                  arn-code-batch-implement

Step 0: Ensure Configuration

Read `${CLAUDE_PLUGIN_ROOT}/skills/arn-code-ensure-config/references/step-0-fast-path.md` and follow its instructions. This guarantees a user profile exists and `## Arness` is configured with Arness Code fields before proceeding.

After configuration is ensured, extract the following from `## Arness`:

• **Plans directory** — base path where project plans and PLAN_PREVIEW files are stored
• **Specs directory** — path to the directory containing specification files
• **Code patterns** — path to the directory containing stored pattern documentation
• **Vision directory** (if exists) — path to greenfield vision artifacts
• **Use cases directory** (if exists) — path to UC documents
• **Issue tracker** — determines remote issue tracker type (`github`, `jira`, or `none`)
• **Template path** — path to report templates

---

Step 1: Detect Feature Sources

Batch planning supports multiple feature sources. Check them in order — the first match determines the primary source.

1a. Check for Greenfield Feature Tracker

Read the backlog-selection reference: `${CLAUDE_PLUGIN_ROOT}/skills/arn-code-batch-planning/references/backlog-selection.md`. Follow its procedure to scan the Feature Tracker and identify unblocked features.

**If greenfield backlog exists with 2+ unblocked features:** Proceed to Step 2 with greenfield features (input_type: `greenfield` for each).

**If greenfield backlog exists with exactly 1 unblocked feature:**

Inform the user: "Only 1 unblocked feature found: **F-XXX [Feature Name]**. Batch planning is designed for 2+ features."

Ask (using `AskUserQuestion`):

**"How would you like to proceed?"**

Options: 1. **Plan this feature** — Switch to arn-planning with F-XXX 2. **Proceed with batch anyway** — Use the batch pipeline for this single feature 3. **Exit**

If **Plan this feature**: invoke `Skill: arn-code:arn-planning` with the F-XXX reference. Exit batch-planning. If **Proceed with batch anyway**: continue to Step 2 with the single feature pre-selected. If **Exit**: STOP.

**If greenfield backlog exists with zero unblocked features:**

Inform the user: "No unblocked features found. All pending features have incomplete dependencies." Present the summary counts.

Ask (using `AskUserQuestion`):

**"No features are available for batch planning. What would you like to do?"**

Options: 1. **Switch to single-feature planning** — Run arn-planning to describe a feature or report a bug 2. **Exit** — I'll wait for dependencies to complete

If **Switch**: invoke `Skill: arn-code:arn-planning`. Exit batch-planning. If **Exit**: STOP.

1b. Check for Remote Issues (Non-Greenfield Fallback)

**If no greenfield Feature Tracker exists** (no Vision directory field, or no `feature-backlog.md`) BUT Issue tracker is `github` or `jira`:

Ask (using `AskUserQuestion`):

**"No greenfield feature backlog found, but [GitHub/Jira] issues are available. How would you like to select features?"**

Options: 1. **Browse [GitHub/Jira] issues** — Select multiple issues to plan in batch 2. **Switch to arn-planning** — Plan a