decision

Identify source flows and produce SDR documents with decision rationale.

Updated Mar 10, 2026

Search Tags:#workflow #architecture #documentation #decision #story #backlog #sdr

Ready to run

npx skills add https://github.com/iamsteveholmes/momentum --skill decision-iamsteveholmes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: decision
Source: https://github.com/iamsteveholmes/momentum/tree/main/skills/momentum/skills/decision
Command: npx skills add https://github.com/iamsteveholmes/momentum --skill decision-iamsteveholmes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Decision making for software projects often lacks structured capture, traceability, and linkage to sources and downstream work. This skill records what was decided, ties it to source materials, and creates linked SDR documents to maintain a clear decision history.

Core Features & Use Cases

Capture and archive decisions from assessments or research and link to SDR.
Enforce a single-source SDR workflow with stepwise decisions, rationale, and traceability to source research.
Bridge decisions to backlog stories and architecture decisions, enabling downstream story creation.

Quick Start

Run momentum:decision to begin recording decisions and generate an SDR document.

Frequently Asked Questions about decision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I capture strategic decisions and link them to backlog stories?▼

Capture strategic decisions by presenting findings stepwise for a definite adopt, reject, defer, or adapt choice with rationale. This generates an SDR document with correct frontmatter and updates upstream links and the registry to bridge decisions to backlog stories.

What is the best way to maintain traceability between architecture decisions and source research?▼

Maintain traceability by loading relevant source materials and enforcing a single-source SDR workflow. Each decision is recorded with rationale and linked directly to source research, ensuring a clear and traceable decision history.

How do I record a definite decision outcome for each finding during an assessment?▼

Record definite decision outcomes by presenting each finding or recommendation one at a time. You select an outcome of adopt, reject, defer, or adapt, provide a rationale, and the skill produces the SDR document.

Can I generate SDR documents from developer conversations and research materials?▼

Yes, you can generate SDR documents from developer conversations and research materials. The skill identifies the source flow, loads relevant materials, and produces an SDR document with correct frontmatter and body.

Do I need any dependencies to run the decision workflow?▼

No dependencies are required to run the decision workflow. The skill operates independently to identify the source flow, present findings for a definite decision, and produce the SDR document with updated registry links.

When should I not use a stepwise decision capture workflow?▼

Avoid using a stepwise decision capture workflow when you need rapid, informal decisions without traceability or when upstream source research and backlog linkage are not required for the project's decision history.