consolidate-adrs
Reconcile an ADR archive with the repository's current design and its surviving rationale.
- License 许可
- MIT
- 最近更新
- 2026-11-08
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- consolidate-adrs
- description
- Reconcile an ADR archive with the repository's current design and its surviving rationale.
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml155 B
03 SKILL.md 正文
Consolidate ADRs
Reconcile the ADR archive into a concise account of the repository's current design and the rationale that still explains it. Historical detail earns a place only when it helps a future reader understand why the current design exists.
Prepare the review
- Read the complete
domain-modelingskill and the ADR format it points to. Use its context-map rules to locate every applicableCONTEXT.mdand ADR archive. If the repository has no context or ADR archive, report that this skill has nothing to consolidate. - Read the applicable
CONTEXT.mdfiles and every current ADR before judging any one ADR. TreatCONTEXT.mdas vocabulary and domain-boundary context; the review targets are the ADRs.
Completion criterion: every ADR has been read in the context of the complete archive and the applicable domain context.
Build the change set
Review every ADR for:
- claims that contradict another ADR or the domain language;
- decisions that another ADR corrects, updates, or subsumes;
- duplicated rationale or current-state descriptions with more than one home;
- historical narration that does not justify the current design; and
- links or other references to material under
docs/honist-v/ordocs/mattpocock/.
For a corrected, updated, or subsumed decision, choose one authoritative ADR to carry the consolidated current decision and its useful rationale. Update that ADR and remove stale or duplicate claims from the others. Retain a brief account of an earlier choice only when it explains the current design. When an ADR has no useful current decision or rationale left, propose deleting it.
Replace each dependency on a provisional document with the specific context, decision, trade-off, or constraint the ADR needs to stand on its own. Verify that information against the repository rather than copying the provisional document's account. The provisional documents themselves are outside this review's change set.
After identifying a candidate change, inspect only the implementation, configuration, and tests that bear on the affected ADR's claims. Bound repository inspection to the evidence needed to verify the content that ADR would keep, rewrite, move, or remove. Current repository behavior, plus user-confirmed constraints that cannot live in code, is the evidence for its present-tense claims. Claims in ADRs outside the intended change set are outside this correctness review.
Record every intended change with:
- the ADR files it changes or removes;
- the contradiction, stale statement, or provisional reference being resolved;
- the repository evidence for the proposed current account;
- the exact information to keep, move, rewrite, or remove; and
- any historical context retained and why it still justifies the design.
Completion criterion: every finding is either represented by an intended change or explicitly recorded as needing no change, and every current-state claim in the intended change set has repository evidence or a user-confirmed non-code constraint.
Reach agreement
Before editing, read and follow the complete grilling skill. Treat the intended changes as its design tree. Ask about every intended change, grouping independent decisions into the same frontier round, and include the evidence and your recommended resolution. Investigate facts yourself; reserve questions for decisions. Recompute the change set when an answer affects other ADRs.
Editing may begin only after the user confirms shared understanding for every intended change. Exclude rejected changes from the approved set.
Apply and commit
Apply exactly the approved set. Re-read the complete resulting ADR archive and verify that:
- content changed by the approved set agrees with the current repository and applicable domain language;
- no contradictory or stale account addressed by the approved set remains;
- each retained historical detail justifies the current design;
- the ADRs are self-contained and contain no references to
docs/honist-v/ordocs/mattpocock/; and - the files still follow the
domain-modelingADR format.
Run relevant repository checks. Review the diff, stage only the approved ADR changes, and commit them without including unrelated worktree changes. Use one coherent consolidation commit unless the approved change set or repository conventions require separate commits. If the approved set is empty, report that outcome without creating an empty commit.
Completion criterion: all approved changes pass the final archive review and relevant checks, and the resulting ADR-only commit or commits exist.
04 同仓库更多 Skills
sync-skills-openai-yaml
Sync every skill's agents/openai.yaml with its SKILL.md — display name, short description, and implicit-invocation policy.
streamlined-setup-matt-pocock-skills
Configure this repo for the engineering skills using one fixed set of choices: local-markdown issue tracker, default triage labels, single-context domain docs. Overwrites any earlier setup. Run once per repo.
retire-provisional-documents
Retire provisional documentation after making its consumers self-contained and preserving only durable domain language and decision rationale.
coding-agent-sessions
Find, read, list, search, inspect, fetch, export, or reconstruct coding-agent sessions across various agents.
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wait-what
Stop. That last message did not land: re-pitch it.