← ClaudeAtlas

record-decisionlisted

Record an architecture decision into the repository's existing ADR convention: discovers the ADR directory, numbering scheme, and record shape in use and writes one record that follows them; when no convention exists it names what it searched, offers common shapes, and writes nothing until the human chooses. Use when: 'record this decision', 'write an ADR', 'architecture decision record', 'capture this decision', 'document why we chose X', or after a design handoff or interview resolves a decision worth keeping. Skip when: the decision is easily reversed and unsurprising (no ADR earned), or the ask is supersession, an index, or status lifecycle beyond what the convention already defines.
melodic-software/claude-code-plugins · ★ 15 · AI & Automation · score 73
Install: claude install-skill melodic-software/claude-code-plugins
## Repository context. Gather first Collect these with **individual** Bash calls, one command per call, never combined into a single invocation: - Current branch, `git branch --show-current` - Working tree status (empty = clean), `git status --porcelain | head -10` The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about. Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git. ## Variables Arguments: `$ARGUMENTS` ## Purpose Record one architecture decision into whatever ADR convention the repository already has. The convention is discovered and followed, never prescribed: this skill owns discovery, the next identifier, the record shape, and the single write. Where no convention exists it reports what it searched, offers common shapes, and defers to the human rather than inventing one. ## Input contract The decision comes from `$ARGUMENTS` and the conversation. A file path the user names is read verbatim. This skill never reads `design-threads.md`, `PLAN.md`, or any other planning artifact on its own; those formats belong to the planning capability, and c