document

Solid

Record 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.

Data & Documents 64 stars 10 forks Updated yesterday Apache-2.0

Install

View on GitHub

Quality Score: 84/100

Stars 20%
60
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# /archcore:document Record the present state: a technical decision, existing code, or a supplied research material. The first word of the arguments selects the mode; a gate inside the mode's track selects the document type. Write affinity: knowledge types; a filed `research` and the decision cascade's `plan` belong to vision. The standard cascade can add a `cpat` (experience). Command tense: `/archcore:plan` declares a future canon delta, `/archcore:document` records the present state — including work that shipped without a plan — and `/archcore:review` reconciles a past declared delta. Δ vocabulary: `skills/_shared/delta-routing.md`. Load `skills/_shared/gate-contract.md` and `skills/_shared/elicitation-contract.md` before executing any gate. ## Modes | Mode | Track and entry | Types the entry gate selects | |---|---|---| | `decision` | `skills/_shared/tracks/decision.md`, `decision.classify` | `adr`, `rfc`; `rule` through the standard cascade; an existing `rfc` draft on the topic → `decision.resolve`, which records an `adr` on an accepted verdict | | `code` | `skills/_shared/tracks/describe.md`, `describe.read` | `spec`, `doc`, `guide`, `scenario` | | `research` | `skills/_shared/tracks/research.md`, `research.frame` | `research`, `rnd` by the closing test; one external material → `evidence` | A document type name is not a mode. When the subject text names a type (`skills/_shared/gate-contract.md`, Entry terms) that the mode's track produces, the selecting gate treat...

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

Data & Documents Listed

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.

11 Updated today
bostonaholic
Code & Development Listed

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).

0 Updated today
radozaprazny
AI & Automation Listed

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.

0 Updated 1 months ago
nanatsusaya