task-planning

Break down features into INVEST-based user stories and backlog tasks.

Updated Mar 30, 2026

Search Tags:#agile #estimation #backlog #sprint #user-stories #task-planning

Ready to run

npx skills add https://github.com/nashirabbash/autorepychatbot --skill task-planning-nashirabbash

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: task-planning
Source: https://github.com/nashirabbash/autorepychatbot/tree/main/.agents/skills/task-planning
Command: npx skills add https://github.com/nashirabbash/autorepychatbot --skill task-planning-nashirabbash

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Task planning for software projects is often inconsistent and manual, leading to vague requirements and missed deadlines.

Core Features & Use Cases

Break down features into granular tasks and user stories that follow INVEST principles.
Define acceptance criteria, effort estimations, and dependencies to enable reliable planning.
Align sprint planning with backlog grooming to drive predictable delivery and clear prioritization.

Quick Start

Create an Epic, split it into a User Story, define concrete tasks with acceptance criteria, and prepare a prioritized backlog for the next sprint.

Frequently Asked Questions about task-planning

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

FAQPage Schema

How do I break down an epic into user stories for a sprint backlog?▼

To break down an epic for a sprint backlog, split features into granular tasks and user stories that follow INVEST principles, then define acceptance criteria and dependencies. This structures work from epic to sprint, enabling reliable planning and clear prioritization for predictable delivery.

What is the best way to write user stories using INVEST principles for agile estimation?▼

INVEST-based user stories for agile estimation are structured by breaking features into independent, negotiable, valuable, estimable, small, and testable tasks. This process defines acceptance criteria and effort estimations, aligning sprint planning with backlog grooming to drive predictable software delivery.

How do I prioritize a backlog and define acceptance criteria for feature development?▼

Prioritize a backlog and define acceptance criteria by organizing feature development tasks with clear estimations and dependencies. Applying backlog grooming guidelines structures the work, enabling reliable sprint planning and clear prioritization to drive predictable software delivery.

Can I use this approach for sprint planning without prior backlog grooming?▼

Sprint planning without prior backlog grooming is difficult because the approach aligns both processes to drive predictable delivery. Backlog grooming defines acceptance criteria, effort estimations, and dependencies, which are required to structure work and prioritize tasks effectively for the next sprint.

Why does task planning fail when requirements are vague and lack dependencies?▼

Task planning fails with vague requirements because it leads to missed deadlines and inconsistent project execution. Defining concrete tasks with acceptance criteria, estimations, and dependencies solves this by structuring work and enabling reliable sprint planning and clear prioritization.

Does task planning work for both sprint planning and backlog grooming?▼

Task planning works for both sprint planning and backlog grooming by aligning them to structure work and drive predictable delivery. It supports breaking down features into tasks, defining INVEST-based user stories, and applying prioritization guidelines across both activities.