mmaideveloper/aiarchitecttoolkit / skills/generate-bdr
generate-bdr
UnverifiedCreate, update, and review source-backed Business Decision Records (BDRs) for material product, investment, scope, ownership, policy, sourcing, operating-model, or risk-acceptance choices. Use when a business choice must authorize or constrain use cases and architecture, or when a BDR reference such as BDR-001 is supplied.
Generate Business Decision Record
Workflow
- Read
AGENTS.md,architecture/toolkit-profile.yamlwhen present, the idea and related use cases, existing BDRs, stakeholder evidence, and relevant business documentation. - Decide whether a BDR is required. Use it for a material business choice; do not create one merely to repeat requirements or technical design. Record a concise skip reason when no such choice exists.
- Resolve the next unused
BDR-NNNor the referenced record. Never reuse or renumber an identifier. - Copy assets/bdr-template.md, replace every placeholder, and remove irrelevant optional sections.
- Separate current state, target state, transition, confirmed facts, proposals, assumptions, and open questions.
- Compare viable options against the same decision drivers. Apply references/bdr-quality.md; do not invent weak alternatives.
- Keep status
Proposeduntil authoritative decision evidence exists. Never infer an approver or acceptance. - Save under
architecture/business-decisions/BDR-NNN-<slug>.mdunless the project profile or repository establishes another path. - Link the source idea/evidence and downstream use cases, ADDs, ADRs, C4 views, and tasks reciprocally when those artifacts exist.
Rules
- Keep one primary, independently changeable business decision per BDR.
- Define measurable outcomes and review conditions, including when the decision should be revisited.
- Apply applicable privacy, AI, security, accessibility, safety, and sector governance without guessing applicability or classification.
- Record human decisions and automation boundaries for material outcomes.
- Do not invent cost, benefit, owner, deadline, approval, classification, or policy values.
- Exclude personal records, credentials, secrets, and sensitive operational details.
Output
Return path, status, selected option or Not yet decided, affected use cases, constraints handed to architecture, assumptions, governance result, approval gaps, and recommended next step.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 318k | Updated | Claude CodeCodex | Unverified | Install |