Skip to content

imMamdouhaboammar/anti-slop-engineering / skills/decision-guard

decision-guard

Verified

Use 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.

examples/architecture-record.json

View on GitHub
{
  "kind": "architecture",
  "goal": "Run an authenticated analytics app with long background calculations",
  "proposal": "Use Next.js, Vercel and Supabase",
  "evidence": [
    {"source": "Illustrative product brief", "finding": "Most routes are behind login; long background jobs are required", "level": "observed"}
  ],
  "direct_check": {
    "status": "not_found",
    "source": "Illustrative service inventory",
    "finding": "No existing app directly meets these product requirements"
  },
  "assumptions": [
    {"claim": "A maintainer can manage production PostgreSQL", "state": "unverified", "basis": "Operational ownership not yet assigned"}
  ],
  "decision_axes": [
    {"name": "frontend", "considered": ["Vite SPA", "TanStack Start", "Next.js"], "selected": "Vite SPA"},
    {"name": "hosting", "considered": ["VPS", "Managed runtime"], "selected": "VPS"},
    {"name": "database", "considered": ["Self-managed PostgreSQL", "Managed PostgreSQL"], "selected": "Self-managed PostgreSQL"}
  ],
  "alternatives": [
    {"name": "VPS and local PostgreSQL", "benefit": "Predictable fixed infrastructure", "risk": "Shared failure domain and operational burden", "reversal": "Export and restore to external DB"},
    {"name": "Managed runtime and managed PostgreSQL", "benefit": "Lower direct administration", "risk": "Usage-dependent costs and provider integration", "reversal": "Portable application with database export"}
  ],
  "horizons": [
    {"stage": "now", "scenario": "Low initial concurrency", "consequence": "Simple single-node deployment possible"},
    {"stage": "later", "scenario": "Database grows and server fails", "consequence": "Offsite recovery and isolation become critical"}
  ],
  "decision": {
    "action": "pause",
    "choice": "VPS and local PostgreSQL, conditional",
    "reason": "Needs named operator and tested backup recovery before approval",
    "invalidated_by": "No operations ownership or inadequate recovery time"
  }
}
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: 472kUpdated Claude CodeCodexVerifiedInstall
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: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
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 availableStars: 322kUpdated Claude CodeCodexVerifiedInstall