decision-propagation

Propagate architectural decisions across interconnected project documents and flag conflicts.

2|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/DojoGenesis/gateway --skill decision-propagation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-propagation
Source: https://github.com/DojoGenesis/gateway/tree/main/plugins/agent-orchestration/skills/decision-propagation
Command: npx skills add https://github.com/DojoGenesis/gateway --skill decision-propagation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions recorded in one place often leave other documents out of sync, creating contradictions, missed deferrals, and incoherent master tracking. This Skill identifies where a decision echoes across scouts, specs, and master plans and produces minimal, reviewable edits so the repository's narrative remains consistent.

Core Features & Use Cases

  • Trace dependencies across master plans, scouts, implementation specs, and prompts to find every reference to a decision.
  • Surgical edits: generate focused change suggestions for source documents and implementation prompts without wholesale rewrites.
  • STATUS.md coherence: produce a decisions block and update summaries and scheduling last, serving as the final checkpoint.
  • Edge handling: flag in-flight conflicts, record deferrals, and sync copies across multiple locations.

Quick Start

Propagate the decision skip production auth in v0.2.0 and move auth to v0.2.2 from the auth scout through all dependent documents and update STATUS.md.

Frequently Asked Questions about decision-propagation

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

FAQPage Schema
How do I propagate architectural decisions across interconnected project documents?

Propagating architectural decisions involves tracing dependencies across master plans, scouts, and implementation specs to produce surgical edit suggestions and a STATUS.md decisions block, ensuring repository narrative coherence.

What is traceability for architectural decisions in change management?

Traceability for architectural decisions is the process of finding every reference to a decision across interconnected project documents to maintain consistency and flag in-flight conflicts or deferrals when scope changes.

How do I update STATUS.md when architectural decisions change scope or scheduling?

Updating STATUS.md requires generating a decisions block and syncing summaries and scheduling last, serving as the final checkpoint after applying surgical edits to dependent source documents and implementation prompts.

Can I apply surgical edits to implementation specs without wholesale rewrites?

Yes, surgical edits generate focused change suggestions for source documents and implementation prompts without wholesale rewrites, ensuring minimal, reviewable updates across scouts, specs, and master plans.

How are in-flight conflicts and deferrals handled during decision propagation?

Handling in-flight conflicts involves flagging contradictions across dependent documents, recording deferrals explicitly, and syncing decision copies across multiple locations to maintain master tracking coherence.