plan-build-validate

# Plan-Build-Validate

## Overview

Execute the complete development workflow from planning through implementation to validation, creating a draft PR if all checks pass.

## Arguments

### Definitions

- **`[explore-count]`** (optional): Override explore agent count for planning phase. Defaults to configuration value.
- **`[--git]`** (optional): Auto-commit throughout workflow (plan file, build checkpoints).
- **`[--pr]`** (optional): Create draft PR when validation passes.
- **`[context]`** (optional): Task description to reduce prompts.

### Values

$ARGUMENTS

## Core Principles

- This is the recommended workflow for non-trivial tasks
- Each step must complete successfully before proceeding
- Plan file is saved and can be referenced later
- PR is only created if validation passes
- Use --git to maintain atomic commits throughout
- Always run validation, regardless of --pr flag
- Fix all validation issues before creating a PR
- Review the generated plan before proceeding to build

## Skill-Specific Guidelines

### Workflow Summary

Determine Task Type -> Plan -> Create Branch -> Commit Plan -> Build -> Validate -> Create PR (if --pr and passes)

**Step details:**

1. **Determine Task Type**: Analyze context or ask user (chore/bug/feature)
2. **Plan**: Execute appropriate planning skill, saves plan file
3. **Create Branch**: Create a new branch using `/git-branch` (if --git or --pr)
4. **Commit Plan**: Commit the plan file using `/git-commit` (if --git or --pr)
5. **Build**: Implement all tasks from the plan
6. **Validate**: Run tests, code review, build verification, plan compliance
7. **Create PR**: If `--pr` flag and validation passes, create draft PR using `/git-pr`

## Instructions

### 1. Determine Task Type

- If `[context]` is provided, analyze to determine type
- Otherwise, ask user:
  - Is this a chore (maintenance task)?
  - Is this a bug fix?
  - Is this a new feature?

### 2. Execute Planning Skill

Based on task type, invoke the planning skill:

```