nexus-planninglisted

# Nexus Planning Protocol Produce a complete, decision-ready technical plan before any implementation begins. --- ## Compatibility - Output: Scoping table + Mermaid diagram + trade-off matrix + ordered execution steps - Requires: Read access to source code, infra-as-code, CI/CD config, and recent git history --- ## Workflow ### Step 1 — Context & Discovery Build a complete technical map before proposing anything: 1. Read source code patterns, infra-as-code (CDK/TF), CI/CD flows, and `git log --oneline -20` 2. Identify tech debt, bottlenecks, security boundaries, and breaking change risks 3. Confirm alignment with existing naming conventions, directory structures, and linting config If information is missing: ask a direct, specific technical question ("What auth middleware is in use?" not "Tell me about your auth"). ### Step 2 — Research & Trade-offs For each approach being considered, evaluate: | Category | What to assess | |----------|---------------| | Standard tech | Performance benchmarks, operational cost, maintenance complexity | | AI/LLM stack | Token cost per call, latency p95, tool-calling reliability, RAG retrieval quality | | Cloud/Infra | IAM scoping, VPC/SG boundaries, disaster recovery RTO, blast radius | ### Step 3 — Scoping Table (Stop & Wait for Approval) Present the scoping table and **do not proceed** until the user explicitly approves: | Task | System Impact | Risk Level | Dependencies | Status | |------|---------------|------------|------------