agentleFS
Sign inStart free
Renozoic-FoundryRenozoic-Foundry/forge-public/.claude/skills/decision/SKILL.md

decision

Skill0 starsChanged 3 months agoMITView on GitHub

Create a new Architecture Decision Record (ADR)

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use brief, plan and 3 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    brief

    Generate contextual briefings for legal work — daily summary, topic research, or incident response. Use when starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context.

    Also in 3 projects that use this

  • BlockSkill

    plan

    Draft a TDD, PRD, or lightweight plan in the conversation without committing it.

    Also in 4 projects that use this

  • OpenAISkill

    audit

    Audit or critique a product flow, journey, workflow, funnel, onboarding path, checkout path, settings path, screen, or multi-step product experience by capturing screenshots first, then reporting UX, design, and accessibility findings inline from that evidence. Use Figma only when the user explicitly asks for a board. Use when the user asks to audit, review, critique, inspect, assess, analyze, evaluate, or give feedback on a product experience.

    Also in 3 projects that use this

  • SentrySkill

    review

    Fixture review skill.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new Architecture Decision Record (ADR) from the template.

    line 14
  2. Very specific:

    If $ARGUMENTS is ? or help: Print:

    line 16
  3. Distinctive:

    Stop — do not execute any further steps.

    line 28
  4. Very specific:

    Read docs/decisions/_template.md to load the ADR template.

    line 34
  5. Very specific:

    Look for files matching the pattern ADR-NNN-*.md (e.g., ADR-028-spec-status-source-of-truth.md).

    line 36
  6. Very specific:

    If no ADR files exist, start at ADR-001.

    line 39
  7. Very specific:

    Create the new ADR file at docs/decisions/ADR-NNN-slug.md with:

    line 41

“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md
<!-- forge:paths-note (Spec 575): process-state paths in this command (docs/specs, docs/sessions, docs/decisions, docs/research, docs/process-kit, docs/backlog.md) are the CLASSIC-DEFAULT spellings, not fixed locations. When the project configures forge.paths (e.g. the `contained` layout), resolve each key before use — bash: `forge_path <key>` (source ${CLAUDE_PLUGIN_ROOT:-.}/.forge/lib/config.sh, forge_config_load AGENTS.md); python: `${CLAUDE_PLUGIN_ROOT:-.}/.forge/bin/forge-py .../runtime_config.py path <key>`. -->

Framework: FORGE

Create a new Architecture Decision Record (ADR) from the template.

If $ARGUMENTS is ? or help: Print:

/decision — Create a new Architecture Decision Record (ADR).
Usage: /decision <short title or description of the decision>
Arguments: title (required) — a short description of the architectural decision.
Examples:
  /decision Use Copier instead of Cookiecutter for template rendering
  /decision Switch from REST to gRPC for inter-service communication
Output: docs/decisions/ADR-NNN-short-title.md
See: docs/decisions/_template.md, docs/decisions/README.md

Stop — do not execute any further steps.

Usage: /decision <short title or description>

  1. Read docs/decisions/_template.md to load the ADR template.
  2. Scan docs/decisions/ for existing ADR files. Determine the next ADR number:
    • Look for files matching the pattern ADR-NNN-*.md (e.g., ADR-028-spec-status-source-of-truth.md).
    • Extract the numeric portion from each filename and find the maximum.
    • The next ADR number is max + 1, zero-padded to three digits.
    • If no ADR files exist, start at ADR-001.
  3. Generate a kebab-case slug from the title (e.g., "Use Copier for templates" becomes use-copier-for-templates).
  4. Create the new ADR file at docs/decisions/ADR-NNN-slug.md with:
    • Title: # ADR-NNN: <title>
    • Date: today's date (YYYY-MM-DD)
    • Status: proposed
    • Spec: fill in if the user mentions a spec number, otherwise leave as (none)
    • Context section: pre-filled with a summary based on the user's description
    • Decision, Consequences, and References sections: left as template placeholders for the user to complete
  5. Confirm the file was created and display the full path.
  6. Present a context-aware next action: "Review the draft ADR and fill in the Decision and Consequences sections. Update status to accepted when the team agrees."

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free