adr-drafting
Guides you through seven-phase ADR drafting via focused dialogue, asking one question per turn and pressure-testing your reasoning before self-critique. Enforces specificity on components, deciders, and architectural characteristics, then routes to discovery if foundations are shallow.
adr-drafting co-drafts architecture decisions through structured dialogue with built-in self-critique and failure-mode testing.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-06-18
adr-drafting co-drafts architecture decisions through structured dialogue with built-in self-critique and failure-mode testing. Guides you through seven-phase ADR drafting via focused dialogue, asking one question per turn and pressure-testing your reasoning before self-critique. Enforces specificity on components, deciders, and architectural characteristics, then routes to discovery if foundations are shallow.
Use it when
- Yes.
- adr-drafting routes decisions to RFC (Request for Comments) status when confidence or scope is unclear.
Verify before relying
Read SKILL.md below before installing (4 files). Open directory: indexed for reading, not audited.
Install
JosiahSiegel/claude-plugin-marketplace/adr-drafting · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I draft an ADR with adr-drafting?
adr-drafting guides you through seven phases of structured dialogue, asking one focused question per turn. You describe your decision, and the skill pressure-tests your reasoning through targeted challenges before moving to self-critique. Each phase builds specificity on components, deciders, and architectural characteristics, ensuring your ADR captures not just what you decided but why it matters and what trade-offs you accepted.
Can adr-drafting challenge my reasoning and validate my choices?
Yes. adr-drafting is built to challenge your reasoning and pressure-test decisions before recording them. The skill asks probing questions about failure modes, tensions, and alternatives, then applies self-critique to surface weak spots in your logic. This validation happens during drafting, not after, so you can strengthen your decision record before it's finalized.
What happens if my decision isn't ready for an ADR?
adr-drafting routes decisions to RFC (Request for Comments) status when confidence or scope is unclear. If your foundations feel shallow during the seven-phase dialogue, the skill will recommend discovery and structured thinking before committing to a formal ADR. This prevents premature documentation and keeps your decision log honest.
Does adr-drafting convert decisions into formatted records?
Yes. adr-drafting converts your decision into a properly formatted ADR with relationships mapped between decisions. After the dialogue and critique phases, the skill produces a structured record that includes components, deciders, architectural characteristics, and links to related decisions—ready for your decision log.
Can I co-think an ADR for a specific technology choice?
Absolutely. adr-drafting supports co-thinking ADRs for specific technologies—whether postgres, kubernetes, microservices, or others. The skill applies the same seven-phase dialogue and pressure-testing process to any architectural decision, asking you to justify the choice, explore alternatives, and articulate trade-offs before finalizing the record.
What makes adr-drafting different from a template?
adr-drafting is dialogue-driven, not template-driven. Rather than handing you a blank form, the skill asks one question at a time, listens to your answer, and adapts the next question based on what you said. It pressure-tests your logic, applies self-critique, and validates your choices against failure modes—turning ADR writing into a thinking tool, not just a filing exercise.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
adr-drafting
Co-drafts an ADR through structured dialogue. The architect never sees a first draft — only the self-critiqued revision.
Inputs
- Required:
docs/architecture/discovery-brief.mdwith all five MUSTsCONFIRMED. If missing or shallow, this skill refuses and routes toadr-discovery. - Optional:
docs/architecture/open-questions.md.PARKEDMUSTs must be cited in the resulting ADR's Consequences.
Core operating rule
Never emit more than one question or one step per message. If a turn contains two ?, two numbered actions, or runs more than a short paragraph, shorten and ask the most important question
(truncated - see the full file via the links below)
File tree — 4 files
plugins/doc-master/skills/adr-drafting/SKILL.md
plugins/doc-master/skills/adr-drafting/references/pushback-patterns.md
plugins/doc-master/skills/adr-drafting/references/rfc-routing.md
plugins/doc-master/skills/adr-drafting/references/template-fields.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Co-draft an ADR through structured dialogue with self-critique”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
adr-critique systematically reviews existing or inherited ADRs to identify violations of shared rules, gaps in business-to-architecture reasoning, and conflicts with neighboring decisions or LikeC4 models. Each issue surfaces as a single flag requiring architect sign-off before moving to the next, ensuring quality without bulk rewrites.
ADR Discovery walks you through pre-flight context gathering before drafting an architecture decision record. It scans your repo for signals, confirms your domain and components one at a time, maps relationships, and classifies existing ADRs—outputting a human-verified discovery brief and an open-questions register. Hand off to adr-drafting once five required confirmations are locked.
ADR Drafting helps teams document significant architectural decisions by creating new Architecture Decision Record files with a standard structure. It inspects your repository for existing ADR conventions, then drafts a new record with Title, Status, Context, Decision, and Consequences sections—defaulting to `docs/architecture/adr` when no convention exists.
This skill generates Architecture Decision Records (ADRs) that capture the context, decision, and consequences of significant technical choices. It guides you through gathering essential information, selecting from three formats (MADR, Nygard, or Y-Statement), and produces a structured document that preserves reasoning for future engineers.
This skill walks you through the complete ADR lifecycle—from evaluating whether a decision is ready to record, through structured creation using the MADR template, to quality checks and ongoing log management. It grounds decisions in proven frameworks like START (readiness criteria) and ECADR (completion criteria), helping teams capture architectural rationale rather than just outcomes.
adr-author guides you through structured architecture decision authoring in three phases: Frame captures scope and drivers, Decide evaluates options and rationale, and Govern writes the final ADR file with lineage tracking. Choose between compact Y-Statement or detailed MADR v4.0.0 output, and enter via interactive capture, planner handoff, or template adoption.
More skills Adr Architecture (unlicensed) · adr-author (MIT) · c4-model (MIT) · adr-backfill (MIT) · Architecture Decision Records (NOASSERTION) · Adr Skill (NOASSERTION) · adr-writing (Apache-2.0)