write-planlisted

# Write Plan - Plans are thin, vertical slices - Plans can have multiple `PLAN.md` and `CONTEXT.md` files that are thin vertical slices of full implementations ## Process 1. [Look for an existing plan](#looking-for-existing-docs) that matches the task 2. [Load relevant skills](#compose-with-other-skills) that will help you write a more aligned plan 3. Ask and confirm what should be thin vertically sliced with the user (give options) 4. Perform research/investigation/context gathering 5. Make or edit a new/existing artifact that walks through the plan ( see [artifacts](#context-gatheringartifactsopen-questions) for rules you must follow) 6. If the user has feedback from the presented plan, repeat the artifact step again until the user is satisfied and has no feedback 7. Perform research/investigation/context gathering based on gathered user context as a result of that artifact 8. Never start implementation after planning/within the current session, instruct the user to handover to another session, referencing the plan locations ## Compose with other skills - If the task is broad enough, orchestrate investigation with other agents to verify plan implementation and assumptions - If the plan is to implement code, use code writing/style/pattern related skills to understand how that should be implemented ## Looking for existing docs Before creating anything, check whether planning docs for this task already exists. Infer the repo's convention rather than assuming