Stage 4 · Backlog
Stage 4 converts your implementation specs into a validated backlog.json: an ordered queue of work items the autonomous loop will pick up and build one at a time.
What it does
Section titled “What it does”Turns the spec suite into a validated backlog.json — a queue of self-contained work items the autonomous loop will implement one at a time. Each item must be self-contained because the loop runs with a fresh context per item, so an item can’t rely on memory from previous ones.
Backlog authoring is delegated to the rauf:author-backlog skill. Spec references inside items are project-root-relative (e.g. specs/<feature>/00-core-definitions.md).
Command
Section titled “Command”/feature-forge:forge-4-backlog <feature-name>Inputs it consumes
Section titled “Inputs it consumes”- A completed PRD, tech spec, and all implementation specs
- The loop-runner config from
forge.config.json(defaults to rauf)
Artifacts it produces
Section titled “Artifacts it produces”backlog.json— by default atspecs/<feature>/backlog.json; ifbacklogDiris configured, at<backlogDir>/<feature>/backlog.json- Updates
.pipeline-state.json - Auto-commits if enabled
What you review & approve
Section titled “What you review & approve”You review the backlog plan (item breakdown, dependencies, priorities) and the validation result.
What comes next
Section titled “What comes next”/feature-forge:forge-verify <feature>— recommended before the loop implements the backlog. EnableautoVerify: trueto run it automatically after this stage. See Verify & Fix./feature-forge:forge-5-loop <feature>— see Stage 5 · Loop.
Notes & gotchas
Section titled “Notes & gotchas”- Stages forge-1, forge-2, and forge-3 must be complete before this runs.
- Validation runs the loop runner’s validate command. If the runner is missing or too old, validation is skipped with a warning and that fact is recorded in state.