sdlc-plan

# Plan

## Overview

Create a structured implementation plan for the given task. This skill explores the codebase to understand existing patterns and conventions, gathers requirements, and produces a detailed plan with actionable tasks. Supports different plan types (feature, bug, chore) with type-specific guidance.

## Arguments

### Definitions

- **`[type]`** (optional): Plan type. Values: `feature`, `bug`, `chore`, `auto`. Defaults to `auto`.
- **`[explore-count]`** (optional): Override default explore agent count. Defaults to configuration value based on type.
- **`[--git]`** (optional): Commit plan file after creation.
- **`[context]`** (optional): Freeform context for argument inference (e.g., task description, requirements).

### Values

$ARGUMENTS

## Additional Resources

Load ONE of these based on the `[type]` argument (or detected type if auto):

- For feature plans, see [references/feature.md](references/feature.md)
- For bug fix plans, see [references/bug.md](references/bug.md)
- For chore plans, see [references/chore.md](references/chore.md)

## Configuration

This skill reads configuration from `.claude/configs/interactive-sdlc.json`:

- `planDirectory` (default: `"specs"`): Directory where plan files are saved
- `defaultExploreAgents.feature` (default: `3`): Number of explore agents for feature plans
- `defaultExploreAgents.bug` (default: `2`): Number of explore agents for bug fix plans
- `defaultExploreAgents.chore` (default: `2`): Number of explore agents for chore plans

## Core Principles

- Explore the codebase thoroughly before planning to understand existing patterns and conventions
- Generate plans as static documentation - never modify them during implementation
- Focus on specific, actionable tasks rather than time estimates or deadlines
- Use TodoWrite tool for progress tracking, not plan file updates
- Ask clarifying questions when requirements are unclear or context is insufficient
- Each task should be specific enough to execute withou