project-planning

Plan software projects into epics, user stories, and sprint backlogs.

14|11|Updated Dec 1, 2025
One-click install
npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill project-planning-dauquangthanh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-planning
Source: https://github.com/DauQuangThanh/hanoi-rainbow/tree/main/skills/project-planning
Command: npx skills add https://github.com/DauQuangThanh/hanoi-rainbow --skill project-planning-dauquangthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Planning software projects across teams can be chaotic without a repeatable framework. This skill provides a structured approach to define scope, break down work into epics and user stories, estimate effort, organize backlogs into sprints, and track progress to improve delivery predictability.

Core Features & Use Cases

  • Workflow guidance: defines a repeatable planning workflow from scope definition to backlog refinement.
  • Story-based planning: converts requirements into epics, user stories, and technical tasks with acceptance criteria.
  • Backlog and sprint management: prioritization, velocity tracking, and milestone planning for predictable delivery.
  • Use Case: a small team uses this skill to plan a 4-sprint release by decomposing features into user stories and tasks with estimates.

Quick Start

Plan a new project by defining scope, creating epics and user stories, estimating effort, and generating a sprint backlog with milestones.

Frequently Asked Questions about project-planning

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

FAQPage Schema
How do I break down project scope into epics and user stories for sprint planning?

Sprint planning breaks down project scope by converting high-level requirements into epics, user stories, and technical tasks. This structured decomposition defines clear acceptance criteria and aligns deliverables with Definition of Ready and Definition of Done.

What is the best way to estimate effort and prioritize a project backlog?

Effort estimation and backlog prioritization organize work items by value and complexity to ensure predictable delivery. This process sequences user stories into actionable sprints while tracking team velocity for accurate milestone planning.

How does velocity tracking improve milestone planning across software teams?

Velocity tracking improves milestone planning by measuring completed work per sprint, creating a predictable delivery cadence. It aligns backlog prioritization with actual team capacity, ensuring realistic roadmap generation across multiple teams.

Can I use this sprint planning approach for a small team releasing over multiple sprints?

Yes, this sprint planning approach suits small teams managing multi-sprint releases. It decomposes features into estimated user stories and technical tasks, organizing them into a structured 4-sprint backlog with tracked milestones.

Do I need a specific project management tool to generate a roadmap with DoR and DoD alignment?

No specific project management tool is required to generate a roadmap with DoR and DoD alignment. The framework applies a repeatable workflow to define scope, refine backlogs, and track progress independently of proprietary platforms.

Why does chaotic cross-team project planning require a repeatable workflow framework?

Chaotic cross-team project planning requires a repeatable workflow framework to establish consistent scope definition and backlog refinement. This structured approach replaces ad-hoc methods with clear effort estimation and milestone tracking for delivery predictability.