task-planning

Plan software development tasks into INVEST-compliant user stories and MoSCoW-prioritized sprint backlogs.

8|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/JEO-tech-ai/oh-my-unity3d --skill task-planning-jeo-tech-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: task-planning
Source: https://github.com/JEO-tech-ai/oh-my-unity3d/tree/main/.unity-skills/task-planning
Command: npx skills add https://github.com/JEO-tech-ai/oh-my-unity3d --skill task-planning-jeo-tech-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and organizing software development tasks is essential to streamline sprint planning, improve alignment across teams, and keep a clear backlog.

Core Features & Use Cases

  • Break features into lightweight user stories using the INVEST framework to ensure clarity and testability
  • Prioritize work with MoSCoW, maintain acceptance criteria, and estimate effort for reliable planning
  • Provide reusable sprint planning templates and execution guidance to accelerate delivery across projects

Quick Start

Describe features as user stories, apply INVEST criteria, and assemble a sprint backlog with MoSCoW priorities.

Frequently Asked Questions about task-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write user stories that meet INVEST criteria for sprint planning?

INVEST-compliant user stories break features into Independent, Negotiable, Valuable, Estimable, Small, and Testable tasks. This approach ensures clarity, testability, and reliable sprint planning across multiple teams and project sizes.

What is the best way to prioritize a backlog using MoSCoW?

Prioritizing a backlog using MoSCoW categorizes tasks into Must have, Should have, Could have, and Won't have. This method streamlines sprint planning by aligning work with acceptance criteria and effort estimates for delivery.

Can I use this task-planning approach for feature breakdown across multiple teams?

Yes, you can use this task-planning approach for feature breakdown across multiple teams. It applies to backlog grooming and sprint planning regardless of project size, providing reusable templates and execution guidance to accelerate delivery.

How do I assemble a sprint backlog with acceptance criteria and estimates?

To assemble a sprint backlog with acceptance criteria and estimates, describe features as user stories, apply INVEST criteria, and organize them using MoSCoW priorities. This creates a reliable, reusable sprint planning template.

Does this sprint planning method work for different project sizes?

Yes, this sprint planning method works for different project sizes. It applies to feature breakdown, user story creation, and backlog grooming across multiple teams, providing reusable templates to streamline execution and accelerate delivery.