imMamdouhaboammar/anti-slop-engineering / skills/decision-guard
decision-guard
VerifiedUse when an AI agent is deriving metrics or complex explanations while a direct answer may exist, choosing a software architecture or technology stack, or making consequential technical decisions with long-term operational costs and uncertain assumptions. Do not use for narrow, fully specified implementation or routine bug fixes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.4 KB |
| agents/openai.yaml | config | 332 B |
| evals/scenarios.json | config | 5.2 KB |
| examples/architecture-record.json | config | 1.9 KB |
| references/decision-method.md | markdown | 5.1 KB |
| references/decision-record.md | markdown | 2.6 KB |
| usecases/architect.md | markdown | 2.9 KB |
| usecases/investigate.md | markdown | 2.2 KB |
references/decision-record.md
View on GitHub# Decision record contract (version 1)
The JSON format is a portable checkpoint for consequential decisions. It is not a benchmark, source verifier, risk score or substitute for human authority. Save it near the active project's decision evidence, not automatically in every repository.
| Field | Required content |
| --- | --- |
| `kind` | `investigation` or `architecture` |
| `goal`, `proposal` | Desired result distinct from initially proposed method |
| `evidence[]` | `source`, `finding`, `level` (`observed`, `derived`, `inferred`) |
| `direct_check` | `status` (`found`, `not_found`, `unknown`, `not_applicable`), `source`, `finding` |
| `assumptions[]` | `claim`, `state` (`verified` or `unverified`), `basis` |
| `decision_axes[]` | Architecture only: `name`, 2+ distinct `considered` options, one selected value (or single candidate with `constraint_rationale`) |
| `alternatives[]` | Architecture only: at least 2 distinct credible options (or single candidate with `constraint_rationale`), each with `name`, `benefit`, `risk`, `reversal` |
| `horizons[]` | Architecture only: current and later `stage`, each with `scenario` and `consequence` |
| `decision` | `action` (`proceed`, `pause`, `stop`), `choice`, `reason`, `invalidated_by` |
When a direct answer is found and execution continues, add `decision.direct_path_handling` (`use` or `bypass`). A bypass also needs `decision.direct_override_reason`. Recording an unsupported reason does not make it true. When hard constraints eliminate alternatives, an axis specifies a single candidate with `constraint_rationale` directly on that axis. For an architecture-wide single-candidate decision, specify `single_candidate: true` and `constraint_rationale` at the record's top level (not under `decision`); eliminated candidates do not count as credible options. For an investigation that ends in `stop`, architectural alternatives and horizons are unnecessary.
The checker intentionally allows `pause` with `direct_check.status = unknown`. It blocks `proceed` with an unknown direct-path status and detects absent architectural comparisons. It checks for structurally present evidence, not whether source citations are authentic or projections make sense.
Exit codes: `0` structurally complete, `2` missing/contradictory record information, `1` malformed input or unreadable file. A `0` does not authorize implementation. The `decision_action` field distinguishes a complete `pause` record from a complete `proceed` record.
Example: [`examples/architecture-record.json`](../examples/architecture-record.json). The example is illustrative only, not observed performance or a real vendor recommendation.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |