# CLAUDE.md
> Auto-generated by claw-forge. Edit freely — this file is yours.

## Project Overview
<!-- TODO: describe what this project does -->

## Stack
- Language: unknown
- Framework: unknown

## Build & Test
- Add your build/test/lint commands here

<!-- claw-forge:policy start -->
## How work reaches claw-forge

Feature and bug work in this project goes through claw-forge, not
hand-written edits: the parallel agents rely on file-claim locks, the
acceptance gate and merge-gating, and hand edits bypass all three.

- **New feature or capability** → the `claw-forge-feature` skill
- **Something broken, failing, or regressed** → the `claw-forge-bug` skill
- **Checking or controlling a live run** → the `claw-forge-ops` skill

Trivial changes — a typo, a rename, a config value, a one-function fix —
do not need a spec. Make them directly.

**A spec must validate with zero errors and zero warnings before
`claw-forge plan`.** Use `claw-forge validate-spec --json <spec>` and read
`clean`; `passed` counts errors only. INFO findings never block.

**Never run `claw-forge run` without asking.** It dispatches parallel
agents, writes to git and runs unattended for hours.
<!-- claw-forge:policy end -->
