Planning Standard

This document specifies the standard for operational planning and execution within the OMP ecosystem. All complex, multi-file, or high-risk changes must follow the structured planning phase to eliminate execution ambiguity and coordinate state changes safely.

Plans are drafted as self-contained files under local://<slug>-plan.md. The planning phase is strictly read-only: no codebase changes, refactors, or state-altering commands are permitted until the plan is approved.

1. Protocol

1. Zero-Fluff & Decision-Completeness: A plan is an execution specification, not a general design discussion. Every decision, signature, path, and command must be resolved. The implementer must not make any design choices during execution.
2. Read-Only Plan Mode: During planning, do not modify or create repository files other than the plan itself. Avoid running state-changing commands (npm install, git commit, database migrations, etc.).
3. Verification First: Every step of the approach must have a corresponding verification command or assertion.
4. Dependencies: Clearly order tasks to ensure the codebase remains buildable and testable at each stage.
5. No Placeholders: Avoid stubs, mocks, and “TODO: implement” statements in both the plan and the eventual implementation.

2. Gotchas

• Nginx & Clean URLs: When changing paths or routing configurations, verify configuration syntax using nginx -t before reloading.
• State Preservation: Ensure configuration states and existing integrations remain functional unless explicitly deprecated by the plan.
• Emoji Rules: Emojis are permitted in user-facing documents and specifications to align with SSOT category tags. However, planning-standard.md itself must remain emoji-free.