plan

<!-- rig-generated --> # plan+ — Disciplined Planning Wraps `superpowers:writing-plans`. Requires superpowers to be installed. ## Before You Begin This skill runs after `brain+` has produced a validated design. It creates the implementation plan with testing discipline baked into every task. ## Procedure ### Phase A: Load Context 1. Read the design output from `brain+` (from the current session or saved spec). 2. When you need to explore the codebase (verify file paths, check dependencies, find related modules), use the scout agent: ``` Agent(subagent_type="scout", prompt="Map the codebase structure for [area]. Focus on: dependencies, test files, and related modules.") ``` 3. Load active enforcement rules from session context (see session-start output). If active enforcement rules are configured, add a **Constitutional Compliance** section to the plan: ``` ## Constitutional Rules for This Plan [List active enforcement rules from session-start output — these are configurable via .harness.yaml] - Use real [database/payment/logger] connections in stack/E2E tests — mocks are appropriate in unit tests - Show command output before claiming done - Every source file change requires corresponding test changes - Full-loop assertions: verify primary + second-order + third-order effects ``` 4. Identify the mock policy for this plan based on active enforcement rules: ``` ## Mock Policy Stack/E2E (real deps): [list from active enforcem...