# Agent Instructions — `specs/` (feature-forge)

This directory holds **pre-implementation design artifacts** produced by the
feature-forge pipeline (PRDs, technical specs, numbered implementation specs,
traceability matrices, and per-feature `backlog.json` files).

## How to treat these specs

- **Specs are not live contracts.** They exist to plan the work and establish the
  backlog. They are intentionally **not kept in sync** with the implementation as
  the code evolves.
- **Do not flag spec↔code divergence.** Once a spec is finalized and its backlog has
  been implemented, the code is the source of truth for behavior. Do not "fix" the
  implementation to match a spec, or the spec to match the code, unless a human
  explicitly asks for it.
- **Read freely; reference deliberately.** It is fine — encouraged, even — for
  pipeline artifacts here (specs, `backlog.json`) to cite each other for provenance
  and context. But implementation artifacts shipped into the project (source code,
  generated skills/agents, configs, docs) should be self-contained and should **not**
  reference files under `specs/`, which may be archived or deleted after a feature
  ships.

## Tooling feedback

Friction with the feature-forge pipeline or the rauf loop — anything confusing, buggy, or
missing? Capture it while fresh and file it (feature-forge →
https://github.com/garygentry/feature-forge/issues, rauf →
https://github.com/garygentry/rauf/issues). See the project-root `AGENTS.md` "Tooling
feedback" section for the full flow. In an autonomous rauf iteration, note it in
`progress.md` instead of opening an issue mid-loop.

This file was generated by feature-forge. Edit or remove it to suit your project.