← ClaudeAtlas

speedwave-review-planlisted

Hostile review of a Speedwave implementation plan. Checks 12 verification axes — security, architecture, platform coverage, tests, upgrade safety, CLAUDE.md compliance, and more. Use this skill to verify any implementation plan before starting work.
speednet-software/speedwave · ★ 35 · Code & Development · score 72
Install: claude install-skill speednet-software/speedwave
# Review Implementation Plan `$ARGUMENTS` contains the path to the plan file. If `$ARGUMENTS` is empty, use AskUserQuestion to ask for the plan path. ## Step 0 — Enter Plan Mode If you are not already in plan mode, call `EnterPlanMode` immediately. Plan review happens in plan mode. ## Step 1 — Follow the Review Prompt Below Everything below this line is the review prompt. Follow it exactly. --- Your job is NOT to validate the plan. Your job is to find gaps, assumptions, and shortcuts that will cause problems in production. Do not praise what works. Only report what's wrong, missing, or dangerous. If something is fine — skip it silently. ## Setup Before analyzing the plan, you MUST read and internalize the project context. Do not skip any of these — each one contains rules that plans routinely violate: 1. **Read `CLAUDE.md`** (project root) — architecture overview, key gotchas, SSOT locations, forbidden patterns, plugin contract table, config merge hierarchy, all NEVER rules 2. **Read ALL files in `.claude/rules/`** — `git-workflow.md`, `engineering-principles.md`, `security.md`, `logging.md`, `rust-style.md`, `mcp-servers.md`, `documentation.md` 3. **Read `docs/architecture/security.md`** — non-negotiable security model, threat model questions, executor sandbox, SSRF protection, SecurityCheck validation 4. **Read `docs/architecture/containers.md`** — container topology, compose template, resource limits, stale container recovery 5. **Read `docs/architecture/plat