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 |
usecases/investigate.md
View on GitHub# Investigate a derived-answer problem
1. **Separate the goal from the technique.** Translate "build seven metrics" to "determine X to support decision Y". If the goal itself is ambiguous, ask the smallest blocking question.
2. **Inventory direct sources.** Search available field dictionaries, API contracts, code paths, existing metrics, logs, reports and upstream systems. Use exact semantic names and synonyms. Never assume all sources were searched when tools or permissions are missing.
3. **Check meaning, not label alone.** Verify units, time window, cohort, event definition, provenance, freshness and data ownership. A field with a matching name may still be the wrong answer.
4. **Falsify the indirect plan.** Ask what evidence would make the chain of proxies unnecessary or less reliable. If the direct source passes semantic checks, propose stopping the derivative work.
5. **If source evidence conflicts, isolate the disputed definition.** Do not average incompatible figures or force a false winner. Mark unknown, identify the smallest reconciliation test, and pause a consequential conclusion.
6. **When no direct route exists, construct the smallest defensible inference.** State its assumptions, uncertainty and a test against independent observations. Stop adding measures when they cease improving the target decision.
7. **Reassess only after material discoveries.** Record what changed and whether existing artifacts can still serve an independent purpose. Sunk cost is never a reason to continue.
## Worked case
**Request:** "Combine registration rate, conversion rate and deduplicated events to estimate final completed purchases."
**Observed:** The transaction API exposes `completed_purchases`, but it includes refunded purchases. The decision asks for non-refunded completed purchases.
**Action:** Verify whether a net-purchase field or refund join already exists. Do not declare the raw field equivalent merely because its name is close. If a verified net field exists, use it directly. Otherwise calculate only the missing net adjustment, not an elaborate funnel of unrelated proxies.
**Handoff:** Goal; direct source checked; semantic mismatch; minimal calculation (if required); evidence confidence; next probe.
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: 323k | 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: 323k | 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: 323k | Updated | Claude CodeCodex | Verified | Install |