Creating Development Plans

This is the skill you want when you need to document a structured development plan before diving into implementation. It creates a phased task breakdown in a DEVELOPMENT_PLAN.md file, complete with checkboxes, QA criteria, and explicit stop points for human review. The approach is methodical: it reads your existing codebase first, analyzes requirements, breaks work into discrete phases, and uses deep thinking to catch over-engineering before it happens. What I appreciate here is the emphasis on simplicity and the "planning occurs before code" mentality. It's built for teams who want an AI to plan thoroughly, then execute against that plan later, rather than rushing straight into implementation.