Plugin

anticipating-shadow-points

Helps you ship complex engineering work without missing the obvious. Before any code is written, ASP runs an automated pre-mortem to surface failure modes that engineers (and LLMs) routinely miss on first pass — RLS policy gaps, replica lag during migrations, rate-limit issues in external APIs, deprecated callsites, monitoring blind spots, untested rollback paths. It then validates the plan with an independent agent, locks execution into a step-by-step contract with acceptance tests, and runs autonomously until done. Use before any non-trivial task: schema migrations, refactors across many files, deploys with external dependencies, RLS policy changes, or architecture decisions. Multilingual docs (English, Spanish, Portuguese, Italian, Hebrew). MIT licensed.

• Published source
• Repository

Analysed

11 October 2026

Last observed

12 October 2026

What the code does

Static analysis found none of the capabilities we track, such as shell commands, network requests or file writes, in the latest version.

Having a capability is not wrongdoing; many tools need these to do their job. It tells you what to check before you install.

This is public metadata, not a safety certification or complete assessment. Static analysis cannot establish what a tool does at runtime.