agentleFS
Sign inStart free
hardness1020hardness1020/VibeFlow/.claude/skills/record-decision/SKILL.md

record-decision

Skill8 starsChanged 8 months agoMITView on GitHub

Document ADRs for non-trivial choices at Stage D of the VibeFlow docs-first workflow

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use verify and handoff.

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.
  • Microsoft AzureSkill

    verify

    End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.

    Also in 3 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

6 rules. 0 are common, 2 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 8 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Document ADRs for non-trivial choices at Stage D of the VibeFlow docs-first workflow.

    line 14
  2. Distinctive:

    Document non-trivial architectural decisions

    line 19
  3. Very specific:

    Follow the workflow in .claude/rules/context7-research.md to fetch current library documentation.

    line 73
  4. Very specific:

    After completing Stage D, update docs/workflow-state.yaml:

    line 84
  5. Distinctive:

    After completing this stage, ask the user for permission before committing:

    line 95
  6. Very specific:

    After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage.

    line 106

“Common” is measured: kept by at least 6 in 10 of the 8 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

record-decision

Document ADRs for non-trivial choices at Stage D of the VibeFlow docs-first workflow.

Purpose

This skill creates ADR (Architecture Decision Record) documents for Stage D:

  • Document non-trivial architectural decisions
  • Record alternatives considered and consequences
  • Include rollback plans

Workflow

Stage D: Decide
    │
    ├── Create ADRs for non-trivial decisions
    ├── Document alternatives and consequences
    └── Include rollback plans

Usage

Create ADR

/record-decision <ID> <slug>

Creates docs/adrs/adr-<ID>-<slug>.md.

Example:

/record-decision 001 backend-framework

Document Requirements

ADR (docs/adrs/adr-<ID>-<slug>.md)

Required sections:

  • Title with decision summary
  • Header (File, Status)
  • Context
  • Decision
  • Consequences (+/-)
  • Alternatives
  • Rollback Plan
  • Links (PRD/SPEC/FEATURE references)

Validation

  • scripts/validate_adr.py — Validate ADR

References

See assets/:

  • adr-template.md — ADR template

Context7 Library Research

Follow the workflow in .claude/rules/context7-research.md to fetch current library documentation.

What to look for: capabilities, limitations, compatibility, migration effort, maintenance status.

Where to incorporate findings:

  • Decision — ground the chosen option in verified library capabilities
  • Consequences — cite actual limitations and version constraints from docs
  • Alternatives Considered — compare alternatives using current feature sets, not assumptions

Manifest Update

After completing Stage D, update docs/workflow-state.yaml:

  • Set stage: D
  • Append to docs.adrs[]: docs/adrs/adr-<ID>-<slug>.md

Checkpoint #1 (after Stage D):

  • Set checkpoint: 1 after passing validation
  • Criteria: PRD exists with all required sections, discovery doc exists, at least one tech spec, at least one ADR

Git Commit

After completing this stage, ask the user for permission before committing:

git add docs/adrs/adr-<ID>-<slug>.md docs/workflow-state.yaml
git commit -m "feat(adr): record <slug> decision (#ft-<ID>)"

Replace <ID> and <slug> with actual values.

Auto-Advance

After the commit is complete, directly run /manage-work advance <ID> to advance to the next stage. The advance command will automatically validate Checkpoint #1 at the D→E boundary.

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