Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

backpropagate-specs

Sterne12

Forks5

Aktualisiert8. Juni 2026 um 19:13

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

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

JuliusBrussee

JuliusBrussee/Loop-Factory

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

SoftwareentwicklerInformatik- und Mathematikberufe·SOC 15-1252

SKILL.md

readonly

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

Backpropagate Specs

Use when implementation facts changed specs/docs.

Workflow

Generate grounded prompt: python3 bin/loop-factory backprop --agent codex
Read generated prompt under factory/prompts/backprop.codex.md.
Inspect git diff directly if needed.
Update only stale facts in specs/docs.
Add TODO/open question when implementation exposed missing decision.
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.

Mehr aus diesem Repository

gleiches Repository

loop-factory

JuliusBrussee/Loop-Factory

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work to Codex or Claude agents, generating implementation prompts, or deciding next loop state.

2026-06-0812

loop-factory

JuliusBrussee/Loop-Factory

Use when orchestrating Loop Factory specs from factory/specs/inbox or factory/specs/active, dispatching work, generating implementation prompts, or deciding next loop state.

2026-06-0812

review-and-archive

JuliusBrussee/Loop-Factory

Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.

2026-06-0812

backpropagate-specs

JuliusBrussee/Loop-Factory

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

2026-06-0812

review-and-archive

JuliusBrussee/Loop-Factory

Use when reviewing active Loop Factory specs against the working tree, checking verification evidence, deciding ACCEPTED or CHANGES_REQUESTED, and archiving accepted specs.

2026-06-0812

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

Backpropagate Specs

Use when implementation facts changed specs/docs.

Workflow

Generate grounded prompt: python3 bin/loop-factory backprop --agent codex
Read generated prompt under factory/prompts/backprop.codex.md.
Inspect git diff directly if needed.
Update only stale facts in specs/docs.
Add TODO/open question when implementation exposed missing decision.
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.