Records, queries, and checks architectural decisions for conflicts.
npx skills add https://github.com/OmniNode-ai/omniclaude --skill decision-store
Please help me install this Agent Skill. Skill: decision-store Source: https://github.com/OmniNode-ai/omniclaude/tree/main/plugins/onex/skills/decision-store Command: npx skills add https://github.com/OmniNode-ai/omniclaude --skill decision-store
This Skill provides a structured way to record, query, and conflict-check architectural and design decisions, ensuring consistency and preventing contradictions across the OmniNode platform.
Record a new technical stack choice for the infrastructure domain.
High-intent search queries and answers about installing and using this skill.
To manage architectural decisions and prevent contradictions, you can record new design choices with detailed context and automatically check them against existing decisions for structural and semantic conflicts. This enforces consistency across platform domains and layers.
Structural and semantic conflict detection for design patterns is an automated mechanism that checks newly recorded architectural decisions against existing ones. It flags HIGH severity issues to prevent contradictions across different platform layers and services.
To record new architectural decisions, you persist design choices by specifying detailed context including type, domain, layer, services, summary, and rationale. This structured documentation ensures decisions are queryable and conflict-checked.
Yes, you can query past architectural decisions by using flexible filtering options. You can retrieve records by filtering based on domain, layer, type, service, or status to review historical design choices.
Slack integration works for conflict resolution in architectural governance by gating HIGH severity conflicts. It requires operator approval via Slack before proceeding, ensuring automated conflict resolution is properly reviewed.
Automated conflict detection for architectural documentation is limited to identifying structural and semantic contradictions between recorded decisions. It requires Slack gating and operator approval to resolve HIGH severity issues, meaning human governance is still necessary.
LucasMalessaDefine technology-agnostic architecture decisions and gating before technology selection.
fredrick84823Automate post-implementation wrap-up across git, Google Sheets, and Slack.
GeargrindadminAnalyze architectural trade-offs and document decisions with ADR templates.
dralgorhythmDocument architectural decisions using ADR format with Title, Status, Context, Decision, Rationale, and Consequences.
