decision-doc-sync

Original：🇺🇸 English

Translated

Trigger: architecture change, new convention, UI/UX standard, quality gate change, ADR. Keep existing project docs in sync with structural decisions.

39installs

Sourcec3sc0-v4113/scaffold

Added on2026-09-25

NPX Install

npx skill4agent add c3sc0-v4113/scaffold decision-doc-sync

SKILL.md Content

View Translation Comparison →

Decision Documentation Sync

Activation Contract

Load this skill when a change introduces or changes a structural decision: architecture, UI/UX standards, scripts or quality gates, or a cross-cutting convention.

Hard Rules

Check which documents exist before editing; update only documents that exist, and create one only when a rule below requires it.
Keep each fact in one document and link to it from others instead of duplicating it.
Record the decision itself, not the change history.
Never leave a document contradicting the code after the change.

Decision Gates

Change type	Document
Architecture, folder structure, scripts	`README.md`
Visual or UX standard, tokens, component usage	`DESIGN.md`
Agent workflow, commands, operational guidance	`AGENTS.md`
Durable decision with alternatives and consequences	new record in `docs/adr/`

Execution Steps

Check which of
```
README.md
```
,
```
DESIGN.md
```
,
```
AGENTS.md
```
, and
```
docs/adr/
```
exist.
Classify the change with the table above; one change may hit several rows.
Update each affected document that exists.
For an ADR, follow the existing numbering and format in
```
docs/adr/
```
; see references/doc-map.md.
Reread the edited sections against the code.

Output Contract

List every document updated, created, or deliberately skipped, with a one-line reason each.

References

references/doc-map.md — ADR format and edge cases.