
1 result

Plans and breaks down work before implementation. Use this skill whenever the user wants to plan a feature, break down a task into subtasks, create a project plan, estimate effort, or organize work into trackable issues — then optionally create GitHub or Jira issues from the plan. MUST trigger when the user describes a feature or task and asks to "break it down", "plan", "figure out tasks", "estimate effort", "where to start", "what steps", "create issues for this work", or wants to think through implementation before coding. Also triggers for migration planning, refactoring strategy, CI/CD pipeline design, or any multi-step engineering work that benefits from upfront task decomposition. Trigger even if the user doesn't say "plan" explicitly — if they describe something complex and seem unsure how to approach it, this skill structures their thinking.