alignment-workflow

Automates Organizational Decision Record consensus workflows from draft to final approval.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/arbgjr/smart_alarm --skill alignment-workflow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: alignment-workflow
Source: https://github.com/arbgjr/smart_alarm/tree/main/.claude/skills/alignment-workflow
Command: npx skills add https://github.com/arbgjr/smart_alarm --skill alignment-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) components.

What problem does it solve?

This Skill formalizes the consensus process for Organizational Decision Records (ODRs), ensuring that every relevant stakeholder is consulted and that decisions follow a repeatable, auditable workflow.

Core Features & Use Cases

  • Structured ODR lifecycle from draft to approved or superseded.
  • Deterministic state transitions and an auditable history of actions.
  • Scripts and tooling to automate input collection, approvals, and escalation.

Quick Start

Create a new ODR with a clear title and stakeholder roster, then transition to pending_input to start collecting inputs. When all inputs are received, transition to pending_approval and have the decision maker approve or reject. If approved, leverage derived ADRs to document follow-on work.

Frequently Asked Questions about alignment-workflow

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

FAQPage Schema
How do I track stakeholder approvals for Organizational Decision Records?

An auditable consensus workflow for Organizational Decision Records enforces deterministic state transitions across the ODR lifecycle, ensuring every relevant stakeholder is consulted through a repeatable process before a decision is finalized.

How do I automate input collection and escalation for ODR consensus workflows?

You can automate input collection, approvals, and escalation timeouts for ODR consensus workflows by executing Python scripts like consensus_manager.py to handle deterministic state transitions without manual tracking.

What is the step-by-step process to move an ODR from draft to approved?

To move an ODR from draft to approved, create a title and stakeholder roster, transition to pending_input to collect inputs, then transition to pending_approval for the decision maker to approve or reject the record.

Do I need YAML to manage Organizational Decision Record workflows?

YAML is required as a dependency to configure and run the consensus workflow scripts that manage Organizational Decision Records, enabling deterministic state transitions and auditable stakeholder input tracking.

Can I generate Architecture Decision Records after an Organizational Decision Record is approved?

Yes, after an Organizational Decision Record is approved, you can leverage derived Architecture Decision Records to document and track the follow-on technical work required by the final consensus decision.