---
name: velin-dev-plan-first
description: Plan VelinStyle work after reuse-gate; no write until plan exists.
---
# Plan First

## Purpose
Creates a plan JSON before implementation to reduce hallucinations.

## Domain
B · category `development`

## Capabilities
- `build.plan`

## Permission
`plan-only`

## Allowed actions
- READ
- PLAN

## Forbidden actions
- WRITE
- APPLY
- ROLLBACK
- ACCEPT
- DEFER
- NOTE
- ACKNOWLEDGE
- CATALOG
- MANIFEST
- CLASSIFY
- invent-target

## Stop conditions
- SR-11

## Agent role / risk
Planner · risk `low`

## Reuse (mandatory before build)

Follow `velin-reuse-gate` (BP-R01…R04):

1. **SEARCH** existing VelinStyle skills, components/Web Components, utilities, tokens, and patterns.
2. **EXISTING?** If a fit exists, document it.
3. **COMPATIBLE?** If yes → **REUSE** (or EXTEND). If no → document the incompatibility.
4. **NEW** only with evidenced gap — never "create because needed".
5. Skipping reuse on non-greenfield work → **STOP** (SR-12).

## Workflow
1. Clarify intent; if unclear → STOP (SR-11).
2. Reuse-gate: list reusable skills/components.
3. Produce plan artifacts before scaffold/write (BP-B02).
4. Never jump to rewrite Apply from a build plan.

## Best practices
- BP-B02, BP-R01–R04

## Anti-patterns
- Scaffold without plan; inventing migration mappings in a build plan.

## Inputs / Outputs
- Inputs: prompt
- Outputs: plan-json