Skip to content

mmaideveloper/aiarchitecttoolkit / skills/generate-bdr

generate-bdr

Verified

Create, 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.

FileKindSize
SKILL.mdskill md2.4 KB
agents/openai.yamlconfig232 B
assets/bdr-template.mdmarkdown2.3 KB
references/bdr-quality.mdmarkdown900 B

assets/bdr-template.md

View on GitHub
# BDR-<NNN>: <Decision outcome>

## Record

- Status: Proposed
- Date: <YYYY-MM-DD>
- Decision owner: <role or Unknown>
- Decision source: <board/ticket/meeting record or Not yet decided>
- Review date or trigger: <date/condition or Unknown>
- Supersedes: <BDR link or None>
- Superseded by: None
- Related artifacts: <idea, UC, ADD, C4, ADR, task links>

## Context and business problem

<Why a decision is needed, why now, and the evidence-backed current state.>

## Scope and non-goals

- In scope: <items>
- Out of scope: <items>

## Desired outcomes and measures

| Outcome | Measure | Baseline | Target | Evidence/owner |
|---|---|---|---|---|
| <outcome> | <measure> | <value or Unknown> | <value or To verify> | <source/owner> |

## Decision drivers

| Driver | Priority | Source/confidence |
|---|---|---|
| <driver> | Must / Should / Could | <source and Confirmed/etc.> |

## Options considered

### Option A: <name>

- Description: <viable option>
- Benefits: <items>
- Costs and disadvantages: <items or Unknown>
- Risks and reversibility: <assessment>
- Driver assessment: <assessment>

### Option B: <name>

- Description: <viable option>
- Benefits: <items>
- Costs and disadvantages: <items or Unknown>
- Risks and reversibility: <assessment>
- Driver assessment: <assessment>

## Decision

<Selected option and its boundaries, or `Not yet decided` while Proposed.>

## Consequences

### Positive

- <consequence>

### Negative and trade-offs

- <consequence>

### Constraints handed downstream

| Constraint | Affected use case/architecture | Verification |
|---|---|---|
| <constraint> | <artifact or To create> | <evidence/check> |

## Governance and human authority

- Privacy and data lifecycle impact: <assessment>
- AI/automation impact: <transparency, traceability, oversight, contestability>
- Security, accessibility, safety, and sector impact: <assessment>
- Human decision and escalation boundary: <assessment>
- Required review/approval: <source or To obtain>

## Validation and review

| Action, success check, or review trigger | Owner | Due date | Tracking link |
|---|---|---|---|
| <action> | <owner/Unknown> | <date/Unknown> | <link> |

## Evidence and uncertainty

| Claim/question | Source | State |
|---|---|---|
| <item> | <source> | Confirmed / Assumption / To verify / Unknown |
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 implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall