writing-planslisted

# Writing Plans Use this skill to turn requirements or an approved design into an implementation plan. ## Relationship To Context Skills When the work is tracked in `.my-context/tasks/`, use `context-task` alongside this skill. - read the task goal from `task.md` - use `notes.md` for task-specific research and constraints - write the resulting plan to `plan.md` When prior project decisions or non-obvious history may matter, use `context-memory` before finalizing the plan. ## When to Use This Skill Use this skill when: - The work has multiple steps or checkpoints - The user wants a plan before implementation - The task spans several files or responsibilities - The requirements are clear enough to sequence into execution tasks Do not use this skill for tiny, direct edits that can be implemented safely without separate planning. ## Core Principles - Plan against the real codebase, not an imagined structure - Make tasks small enough to verify independently - Keep the plan concrete: exact files, responsibilities, and validation steps - Prefer the smallest correct implementation - Follow existing project patterns unless there is a strong reason not to ## Workflow ### 1. Confirm Inputs Before writing the plan, make sure you have: - The approved goal or requirements - Enough codebase context to know where the change belongs - A reasonable task boundary If a `.my-context` task exists for the work, read `task.md` first. If research notes already exist, read `notes.md` t