propagate-changes

Propagates changes bidirectionally across SDLC artifacts to restore traceability consistency.

11|1|Updated Jul 25, 2025

Search Tags:#code review #documentation #consistency #requirements #traceability #sdlc #propagation

Ready to run

npx skills add https://github.com/tomzx/agents --skill propagate-changes-tomzx

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: propagate-changes
Source: https://github.com/tomzx/agents/tree/main/skills/propagate-changes
Command: npx skills add https://github.com/tomzx/agents --skill propagate-changes-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A change made in one SDLC artifact silently invalidates everything built from it and everything it was built from, leaving requirements, specifications, plans, tasks, tests, code, and documentation out of sync. This Skill runs a bidirectional propagation pass over the artifact graph so drift is detected, dependents are updated, and ambiguous conflicts are escalated to humans instead of guessed. ## Core Features & Use Cases - Bidirectional Propagation: Walks the artifact graph downward to rewrite stale dependents and upward to re-check premises, flagging drift for human decision. - Traceability and Orphan Detection: Builds a full traceability matrix from issue to code, classifying findings as orphan upstream, orphan downstream, or broken references with severity levels. - Safe Fix Mode: With `--fix`, applies mechanical rewrites, bumps revision counters, and regresses stale review verdicts so the forward pipeline resyncs artifacts. - Use Case: After renaming an API endpoint mid-review, run `/propagate-changes FEAT-7 --entry code --fix` to update docs and test expectations, refresh the PR description, and flag the outdated specification for re-review. ## Quick Start Ask the agent to run /propagate-changes for a feature after a code change, optionally with --fix, to bring all SDLC artifacts back in sync.

Frequently Asked Questions about propagate-changes

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I keep SDLC artifacts in sync after a code change?▼

Run /propagate-changes with the feature ID and --entry code --fix. The skill walks the artifact graph downward to rewrite stale docs, tests, and PR descriptions, and upward to flag premises that conflict with the change.

What is the difference between propagate-changes and sync-sdlc?▼

sync-sdlc compares the codebase against requirements and specification for one feature, covering two layers. propagate-changes walks every adjacent pair in the artifact graph in both directions and updates dependents instead of only flagging them.

Does propagate-changes modify requirements or specifications automatically?▼

No. Upstream artifacts are never rewritten; the skill only regresses their review verdict to changes-requested with --fix and raises questions for humans. Downstream dependents are rewritten only when a single mechanical resolution follows from the change.

What prerequisites does propagate-changes require?▼

The working directory must be the repository root with a populated .sdlc directory containing at least one feature with requirements.md or specification.md. Run /sync-sdlc first if the .sdlc directory is absent.

When should I run a full propagation pass?▼

Run /propagate-changes all periodically at sprint end, before a release as a gate, after merging a PR, or when inheriting an existing .sdlc directory to establish a traceability trust baseline across all features.