Will it automatically change my files without asking?

For documents already in your current PR scope, it proceeds with the update; however, it will explicitly ask for permission before modifying out-of-scope documents.

Can it handle contradictory feedback in PR threads?

Yes, it performs a mandatory scan of all threads first to identify final positions and synthesize themes before applying any changes.

How does it distinguish between a requirement and a design choice?

It uses a 'litmus test' asking if the team has a choice. No choice (external constraints) means a requirement; a strategic choice means design or an ADR.

What documents does this skill help maintain?

It specifically manages requirements.md, design.md, design-approach.md, and decisions.md, ensuring each contains the correct level of detail.

Document Update Discipline

Name: Document Update Discipline
Author: flox

byflox

•

Aprendizaje y Documentación

Enforces strict abstraction levels when updating project requirements, design documents, and architecture decisions from external feedback.

The Document Update Discipline skill provides a rigorous framework for Claude to process incoming changes from PR comments, meeting transcripts, and interactive reviews. It ensures that technical information lands in the correct document—requirements.md, design.md, design-approach.md, or decisions.md—at the appropriate level of abstraction. By applying a 'translate, don't copy-paste' principle, the skill prevents implementation details from leaking into requirements while ensuring that strategic choices are captured as Architecture Decision Records (ADRs).

Características Principales

01Multi-thread synthesis to group related PR discussions into unified conclusions

02Structured ADR generation for significant architectural decision reversals

03Automatic classification of feedback into requirements, design, or rationale

04Context-aware routing between four core project documentation types

05Implementation-leakage detection for clean, behavioral requirements

061 GitHub stars

Casos de Uso

01Applying complex PR review feedback across multiple architectural documents simultaneously

02Extracting structured requirements and design mechanisms from unstructured meeting transcripts

03Maintaining document integrity when reversing strategic technical decisions

Características Principales

01Multi-thread synthesis to group related PR discussions into unified conclusions

02Structured ADR generation for significant architectural decision reversals

03Automatic classification of feedback into requirements, design, or rationale

04Context-aware routing between four core project documentation types

05Implementation-leakage detection for clean, behavioral requirements

061 GitHub stars

Casos de Uso

01Applying complex PR review feedback across multiple architectural documents simultaneously

02Extracting structured requirements and design mechanisms from unstructured meeting transcripts

03Maintaining document integrity when reversing strategic technical decisions