decision-doc-sync

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

3,013
installs: 0 up / 0 down, score 0.00
votes: 3
repo stars
Updated: less than a month ago
In the catalog since: 12 Oct 2026
From: c3sc0-v4113/scaffold

Get it through your agent npx skills add c3sc0-v4113/scaffold@decision-doc-sync

Skill instructions

Rendered from the published SKILL.md, 38 lines.

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.

Get it through your agent

Call the Graph-of-Skills MCP server's retrieve_skill_bundle tool and it returns this skill's text inside your budget.

{
  "tool": "retrieve_skill_bundle",
  "arguments": {
    "query": "decision-doc-sync"
  }
}

New to this? Set up Graph-of-Skills or get a free key. The text on this page comes from its authors: how skills are sourced and what we check. If none fits your task, your agent can write a skill for your own library. To keep a skill from your own library on a machine, see how to install one of your skills.

Share on X Share on LinkedIn Share on Bluesky Share on Hacker News

Share on Reddit

Source

Source repository c3sc0-v4113/scaffold
Listing on skills.sh

From c3sc0-v4113/scaffold via skills.sh

Related skills

architecture-decision-records
Capture architectural decisions as numbered ADR markdown files in docs/adr/ with context, alternatives considered, consequences, and an index README. Use when the user says 'record this decision' or 'ADR this', chooses between frameworks or databases, discusses trade-offs, or asks why the codebase is shaped this way.
10,320 installs
sync
Run /sync as the last step after a change is complete, around merge, to keep durable knowledge current. Updates root and nested AGENTS.md, reconciles the scope from repo evidence, and flags specs the change made stale. Surgical edits only: it adds lines, and rewrites single lines it owns. Never a whole section, never curated prose.
4,294 installs
documentation-and-adrs
Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
63,201 installs
create-architectural-decision-record
Create an Architectural Decision Record (ADR) document for AI-optimized decision documentation.
10,176 installs
project-architecture
Trigger: UI change, layout, component architecture, state flow, theming, server/client boundary, Astro island. Keep Next.js or Astro apps server-first.
3,015 installs