initiativelisted

# Initiative Plan work in a shared memory, then complete one task per conversation. Use the user's request to select planning or execution. Creating a plan does not start its implementation. Follow the active session's permissions and mode; in a read-only planning session, present the plan without writing memory or code. ## Create a plan 1. Read the project instructions, relevant code, and existing plans. Establish the intended result, scope, constraints, and measurable completion criteria. State assumptions and ask about choices that affect the work. 2. Divide the work into tasks small enough to complete and verify in one conversation. Give each task its dependencies, affected files or modules, implementation steps, and acceptance checks with expected results. Follow the project's test-first requirements for code changes. 3. Use [assets/initiative.md](assets/initiative.md) to create the memory. Replace all placeholders, omit unused optional fields, and repeat the task section as needed. Retain shared context once: background, key files, design choices, and links to applicable instructions. 4. Follow `.serena/memories/memory_maintenance.md`. Unless the user supplies a location, use `plans/<initiative-name>/initiative` as the memory name. Link it from the relevant parent memory, or `plans/core` for a top-level plan, using a `mem:` reference with a short description. Preserve existing records; do not overwrite another initiative with the s