decide

Records technical decisions as Architecture Decision Records with structured trade-off reasoning.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/MohamedSayedK/omnigrid --skill decide-mohamedsayedk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: decide
Source: https://github.com/MohamedSayedK/omnigrid/tree/main/assets/core/skills/decide
Command: npx skills add https://github.com/MohamedSayedK/omnigrid --skill decide-mohamedsayedk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical decisions often get made in chat threads or meetings and the reasoning behind them is lost, forcing teams to re-litigate choices or guess at past intent. This Skill forces a decision through structured reasoning and captures the rationale as a durable ADR file in the repository. ## Core Features & Use Cases - Structured Decision Process: Parses the decision topic, gathers only decision-relevant context (existing code, prior ADRs), lays out 2-4 options with trade-offs, and commits to one with explicit rationale. - ADR Authoring: Fills the shipped ADR template and writes it to omnigrid/artifacts/adrs/ADR-NNNN-<slug>.md with the next free sequence number, archiving prior versions on re-runs. - Security Escalation: Pulls in a security-reviewer sign-off before finalizing any decision touching auth, crypto, secrets, or PII. - Use Case: A tech lead debating PostgreSQL versus SQLite for a new service runs the Skill, gets the trade-offs laid out, and ends with ADR-0007-use-postgresql.md documenting why PostgreSQL won. ## Quick Start Ask the AI to decide which database to use for the new billing service and record the decision as an ADR.

Frequently Asked Questions about decide

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

FAQPage Schema
How do I create an Architecture Decision Record for a technical choice?▼

Invoke the decide Skill with the topic you are deciding, and it gathers relevant context, lays out 2-4 options with trade-offs, picks one with explicit rationale, and writes a numbered ADR file to omnigrid/artifacts/adrs/ using the shipped template.

What is an ADR and when should I write one?▼

An ADR (Architecture Decision Record) is a short document capturing a technical decision and its rationale so the reasoning survives after the conversation ends. Write one whenever a choice between meaningful alternatives would be hard to reconstruct later.

Does the decide Skill work without an orchestrator agent?▼

Yes, the Skill is self-sufficient and can be invoked directly with a topic. It activates the tech-lead role in-thread and runs the full decision process, producing the same ADR output as an orchestrated run.

How are security-related decisions handled in an ADR workflow?▼

When a decision touches auth, crypto, secrets, or PII, the Skill pulls in a security-reviewer role for sign-off on the chosen option before the ADR is finalized. The decision itself still runs as the tech-lead role.

What happens if I re-run a decision that already has an ADR?▼

Re-running for an existing slug archives the old canonical ADR to a dated file and writes a refreshed canonical version. A file whose footer was manually removed is treated as hand-owned and is never auto-overwritten.