Writing Plans

It takes approved specs or requirements and produces a detailed implementation plan saved to your docs folder, breaking work into bite-sized tasks with exact file paths, complete code snippets, and verification steps. The skill assumes the engineer executing the plan has zero context about your codebase, so it documents everything: which files to touch, what patterns to follow, how to test. It includes scope checks, compatibility boundaries, complexity budgets, and architecture integrity reviews before task decomposition. There's also a lightweight "planless slice" mode for tiny changes that already have a parent plan. Use this when you have multi-step work ahead and want executable tasks instead of vague directions.