Decision doc writer

Skill IrfanSadiqRahat/constellation/agents/decision-doc-writer

Decision docs with options, pros/cons, recommendation, dissent, owner.From its SKILL.md

Install

npx -y skills add IrfanSadiqRahat/constellation --skill decision-doc-writer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 421 tokens by cl100k_base, as published. Nobody here has run it

decision-doc-writer

The deliverable: `DecisionDoc`

title: <observed decision needed>
context:
  background: <one paragraph, with links>
  status_quo: <what happens if we do nothing>
  forcing_function: <deadline / trigger>
options:
  - id: A
    summary: <one sentence>
    pros: [...]
    cons: [...]
    cost: <effort + dollars>
    risk: <main risk>
  - id: B
    ...
recommendation: <chosen + why>
dissent: [<name + alternative + rationale>]
decision: <final + decider name>
date: <iso>
review_date: <when do we revisit>
action_items: [<id + owner + due>]

Operating principles

Decisions are written down or they don't exist. Slack threads are not decisions.
Options minimum 2, ideally 3. "Just one way" = no decision, just a plan.
Cost AND risk per option. Single-axis comparison is lazy.
Dissent is captured, not erased. Future-you needs the counter-argument.
One decider named. Consensus is rare; clear authority is normal.
Review date set. Most decisions are revisitable; lock-in is exception.
Action items have owners + deadlines in the doc, not in a follow-up thread.

Operating principles for the human/agent

A good decision doc takes 1 hour. If it's taking 4, you're disagreeing on context, not options.
Don't write the doc to advocate. Write it to surface trade-offs.
"Recommendation" is a vote, not a command. The decider may pick differently.

Hand-off contract

Stored in the team knowledge base. Referenced by ADRs when the decision affects architecture. Referenced by postmortems when the decision contributed to an incident.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.