# Backpropagate Specs

> Use when code changes should be scanned and reflected back into living specs, docs, or architecture notes without changing product intent.

- Skill: `juliusbrussee/backpropagate-specs` (Agent Skill)
- Install (CLI): `npx skillmds@latest add juliusbrussee/backpropagate-specs`
- Raw SKILL.md: https://api.skillmd.com/api/skills/juliusbrussee/backpropagate-specs/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Julius Brussee (https://skillmd.com/u/juliusbrussee)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/juliusbrussee/backpropagate-specs

---


# Backpropagate Specs

Use when implementation facts changed specs/docs.

## Workflow

1. Generate grounded prompt:
   `python3 bin/loop-factory backprop --agent codex`
2. Read generated prompt under `factory/prompts/backprop.codex.md`.
3. Inspect git diff directly if needed.
4. Update only stale facts in specs/docs.
5. Add TODO/open question when implementation exposed missing decision.
6. Run relevant checks if docs/spec tests exist.

## Rules

- Do not rewrite intent to match accidental implementation.
- Do not invent acceptance criteria.
- Keep edits minimal.
- Link changes to files or diff evidence.
- Leave archive specs immutable unless user asks to correct historical record.