Help us improve
Share bugs, ideas, or general feedback.
From billy-milligan
Creates a new Architecture Decision Record (ADR) in docs/adr/ with formal professional format. Runs team discussion if Billy active, then writes clean ADR.
npx claudepluginhub rnavarych/alpha-engineer --plugin billy-milliganHow this command is triggered — by the user, by Claude, or both
Slash command
/billy-milligan:adr-newThis command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
# /billy:adr-new — Create a New Architecture Decision Record ## Usage ## Instructions When the user invokes `/billy:adr-new "<title>"`, create a formal ADR in `docs/adr/`. **CRITICAL RULE:** The ADR output is ALWAYS formal and professional, regardless of whether Billy is active. No roasts, no agent pet names, no inside jokes, no informal language. The ADR is written for any developer reading the repo — including people who have never heard of Billy. ### Step 1: Check Billy State Read `.claude/billy-active.txt` to determine if Billy is ON or OFF. ### Step 2A: If Billy is ON — Team Di...
/write-adrInteractively creates an Architecture Decision Record (ADR) in docs/adr/ using Michael Nygard format, gathering context, options, decision, consequences, and status; auto-numbers sequentially.
/adrInteractively creates Architecture Decision Records (ADRs) through guided conversation, documenting context, options, rationale per template, and updates architecture overview.
/adrGenerates a new Architecture Decision Record (ADR) documenting a technical decision, numbers it sequentially from existing ADRs, researches codebase context, and creates the Markdown file in docs/adr/.
/generateGenerates final ADR document from prior analysis: prompts for decision details, analyzes consequences, writes MADR-formatted file to docs/adr/ or specified path, cleans session.
Share bugs, ideas, or general feedback.
/billy:adr-new "API versioning strategy"
/billy:adr-new "caching approach"
/billy:adr-new "CI/CD pipeline choice"
When the user invokes /billy:adr-new "<title>", create a formal ADR in docs/adr/.
CRITICAL RULE: The ADR output is ALWAYS formal and professional, regardless of whether Billy is active. No roasts, no agent pet names, no inside jokes, no informal language. The ADR is written for any developer reading the repo — including people who have never heard of Billy.
Read .claude/billy-active.txt to determine if Billy is ON or OFF.
Run the team discussion before writing the ADR. The team:
Example team discussion for /billy:adr-new "API versioning strategy":
Viktor: три варианта: URL path versioning (
/v1/), header versioning (Accept: application/vnd.api+json;version=1), query parameter (?version=1). Нарисовал диаграмму эволюции каждого подхода через 3 года.Sasha: query parameter версионирование — это антипаттерн с точки зрения кэширования. CDN будет кэшировать неверно. Категорически против.
Dennis: url path это просто работает. Я знаю как это имплементировать, я делал это 5 раз. Header versioning элегантен в теории, но когда ты дебажишь в curl — ты ненавидишь себя.
Lena: пользователи не видят версию API напрямую, но SDK должны быть понятны разработчикам. URL path читаем в документации.
Max: сколько версий мы планируем поддерживать одновременно? Потому что от этого зависит complexity.
After the discussion concludes, one agent confirms the decision and signals transition to formal output:
Viktor: "итого: URL path versioning, поддержка N-1 версий, deprecation policy 6 месяцев. Записываю формально."
Claude writes the ADR directly, asking clarifying questions if needed:
Run: bash ./plugins/billy-milligan/scripts/adr-new.sh "<title>" PROPOSED
The script outputs the new file path (e.g., docs/adr/004-api-versioning-strategy.md).
Open the file and write the formal ADR. The content must:
Good ADR content:
"The team debated three versioning approaches and selected URL path versioning due to its simplicity, debuggability, and CDN caching compatibility."
Bad ADR content (NEVER write this):
"Dennis refused to implement header versioning because he 'made that mistake before.' Sasha yelled about CDN caching. Viktor drew 3 diagrams."
Use the information from the team discussion to INFORM the rationale, but strip all personality.
Show the created ADR file content and ask:
ADR-NNN has been created at docs/adr/NNN-<slug>.md
Status: PROPOSED
Review it and let me know if anything needs adjustment.
Run /billy:adr-status NNN ACCEPTED when the decision is finalized.
If Billy is ON, append to today's session log in Billy memory:
**Formal decision recorded:** → ADR-NNN: <title> (docs/adr/NNN-<slug>.md)
Run bash ./plugins/billy-milligan/scripts/adr-list.sh --update-readme to refresh the index table.