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/architect.md
View on GitHub# Defend an architecture choice
1. **Freeze requirements, not brands.** Capture public/private routes, execution shape, jobs, data growth, team skill, reliability/recovery target, compliance, budget and ownership. Mark absent inputs unknown, not guessed.
2. **List hard constraints and current assets.** Include signed requirements, already-operating infrastructure, existing integrations and migration costs. Exclude options that violate a binding constraint.
3. **Decompose independently.** Consider rendering mode, frontend framework, API and background runtime, hosting, database, storage, auth and operations only to the extent each affects this product. A full-stack framework, host and DB are not inseparable.
4. **Search for the smaller third option.** If a logged-in dashboard already has an API and no server-rendering need, test whether a client-side application is sufficient before comparing two full-stack frameworks.
5. **Compare serious candidates.** For each: what it makes easy now, what it burdens the team with, failure mode, operational owner, irreversibility, exit path and evidence. Use current official docs/benchmarks where claims are time-sensitive; otherwise mark unverified.
6. **Stress the decision.** Evaluate today plus at least one plausible future state: growth, 3am incident, loss of provider feature, backup restore, compliance change, deployment topology or price sensitivity. Future states are conditional scenarios, not predictions.
7. **Recommend conditionally.** Distinguish verified facts from assumptions and articulate a concrete revisit trigger. If critical owner/requirement/price is unresolved, choose a reversible experiment or pause hard commitments. Do not block harmless discovery.
8. **Handoff execution.** Obtain user approval for material platform, spending, migration or data-placement decisions. Once authorized, resume the parent implementation workflow and test actual deployment characteristics.
## Worked case: authenticated SaaS
**Evidence:** Public content comprises landing and legal pages. The private app has heavy background jobs. No confirmed ops owner or restore target.
**Consider:** Separate the rendering layer from background compute. Compare a Vite SPA, TanStack Start and Next.js against actual server-rendering needs. Compare VPS and managed runtime on deploy effort, incident response, queue support and fixed/usage cost. Compare colocated and managed PostgreSQL on restore testing, backups, isolation and team capability.
**Do not conclude:** "Next.js always requires Vercel", "Supabase is required for PostgreSQL", or "VPS is inherently superior over two years". All three are unsupported shortcuts.
**Conditional output:** A VPS with local PostgreSQL can be a strong initial option if an owner can patch it, monitor it and prove an offsite restore. Managed hosting may be preferable when no one can operate that stack. Framework choice remains independent of hosting, and no option is selected purely by popularity.
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 |