document
SolidRecord a decision, document existing code, or file a supplied research material. Modes: document decision (ADR, RFC, or rule), document code (spec, doc, guide, or scenario for existing behavior), document research (only when a finished report or one external material is already in hand). Use for 'we decided', 'record this decision', 'document why we chose X', 'make it our standard', 'draft an RFC', 'should we switch to Y' proposals, 'resolve the RFC', 'we accepted the proposal', 'document the auth module', 'capture how the payment system works', reference material, how-to instructions, or a user flow with examples over an existing spec. Name the type inside the subject to skip the type question. Planning a feature or an intended user journey → /archcore:plan. Checking docs against code or docs health → /archcore:review.
Install
Quality Score: 84/100
Skill Content
Details
- Author
- archcore-ai
- Repository
- archcore-ai/archcore
- Created
- 5 months ago
- Last Updated
- yesterday
- Language
- Shell
- License
- Apache-2.0
Similar Skills
Semantically similar based on skill content — not just same category
documenting-decisions
Architecture Decision Record format — capturing the context, decision, alternatives considered, and consequences of a significant technical choice. Load when recording an architectural decision or writing an ADR.
decision
Records and audits DECISIONS.md — the project's append-only ADR-lite decision log (why we chose X over Y, the alternatives weighed, the trade-offs accepted). Two modes: record (append one entry for a decision just made) and `audit` (find decisions made in code but never written down — a new dependency, a swapped library, a new architectural pattern; read-only). Record ONLY choices with lasting rationale and discarded alternatives — a routine change is a git commit, not an ADR. Generic — usable in any project. Do NOT use it for live status (PROGRESS.md), rules/conventions (CLAUDE.md), product non-goals (BUSINESS.md) or regulatory obligations (COMPLIANCE.md).
decision-record
Use when writing a new decision record (an ADR, or whatever the project calls its decisions artefact) or fleshing out one that is still planned. Covers classifying the change — new versus amendment versus superseding — the required structure and house style, the branch → Proposed → review-with-open-questions → Accepted → merge cycle, and the index and status updates. Not for implementation work.