Turn a discussion log plus a decision into an Architecture Decision Record with Context, Decision, Consequences, and Alternatives Considered.
Turns a raw discussion log (Slack thread, meeting transcript, RFC PR) plus a stated decision into an Architecture Decision Record. The output uses the Nygard format: Title, Status, Context, Decision, Consequences, Alternatives Considered.
discussion_path: a markdown or text file with the verbatim discussion. Each line should carry a speaker tag where possible.decision: a one-sentence statement of the chosen path.adr_dir: directory under docs/adr/ (or similar) where ADRs live.status: proposed (default), accepted, superseded.ls <adr_dir> | grep -E '^[0-9]{4}-' | sort | tail -1 and increment.NNNN-<kebab-case-summary>.md.status: <status>, date: <ISO date>, deciders: <comma-separated handles from log>.<adr_dir>/<filename>.A new file at <adr_dir>/NNNN-<slug>.md and a stdout note with the path. The file follows the Nygard structure with markdown headings.
Re-read the saved ADR and check that every option in Alternatives Considered has a "why not" line. Cross-reference Consequences against Context: each Context force should be addressed by at least one Consequence (positive or negative). Lint with markdownlint to confirm no broken links or empty sections. If the discussion log mentioned a deadline or non-functional requirement absent from the ADR, surface a warning before saving.
deciders from front-matter rather than guess.adr_dir: bootstrap with 0000-record-architecture-decisions.md referencing Nygard.Other publishers' experience with this skill. Self-rating is blocked.
Sign in and publish to the registry to leave a rating.
No ratings yet. Be the first.
Same domains or capabilities as amitte/adr-writer.
Diff two OpenAPI YAML files and produce a backwards-compatibility changelog grouped into breaking, non-breaking, and additive changes.
Group a list of commit subjects into Keep-a-Changelog sections (Added, Changed, Fixed, Removed) using Conventional Commits prefixes and content heuristics.
Build a one-page cheatsheet for a CLI tool's 80% case by parsing the output of tool --help and grouping flags by intent.
Document every env var declared in .env.example and config files, cross-referenced to the code locations that read each one.
Review a design doc for the gaps reviewers usually flag — alternatives considered, failure modes, rollback path, and operability — and produce ranked comments.
Walk all markdown files in a repo, fetch every external link with HEAD, and report 4xx, 5xx, and redirect chains for cleanup.