planning

Plan software development with RICE, MoSCoW, and Value vs. Effort prioritization.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/iannil/code-coder --skill planning-iannil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/iannil/code-coder/tree/main/packages/ccode/src/skill/builtin/planning
Command: npx skills add https://github.com/iannil/code-coder --skill planning-iannil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of organizing and prioritizing development work, ensuring efficient project execution from strategic goals to daily tasks.

Core Features & Use Cases

  • Structured Planning: Supports strategic, tactical, and operational planning levels.
  • Prioritization Frameworks: Implements RICE, MoSCoW, and Value vs. Effort matrices.
  • Feature Breakdown: Guides breaking down Epics into Stories and Tasks with templates.
  • Dependency Management: Visualizes dependencies and identifies critical paths.
  • Estimation Techniques: Offers relative estimation methods like story points.
  • Risk Management: Utilizes a risk matrix and mitigation strategies.
  • Meeting Agendas: Provides structures for Sprint Planning and Retrospectives.
  • Use Case: A development team can use this Skill to plan their next sprint by breaking down a large feature into smaller tasks, estimating effort, identifying dependencies, and prioritizing them using the RICE score.

Quick Start

Use the planning skill to break down the 'User Authentication' epic into stories and tasks.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I break down a large epic into manageable user stories and tasks?

Feature breakdown involves guiding the decomposition of large Epics into smaller Stories and Tasks using structured templates. This ensures development work is organized into actionable units for efficient project execution.

What is the best way to prioritize software features for a sprint?

Feature prioritization uses frameworks like RICE, MoSCoW, and Value vs. Effort matrices. These methodologies score and rank features to ensure efficient project execution from strategic goals to daily tasks.

How does dependency mapping work for agile project management?

Dependency mapping visualizes relationships between tasks to identify the critical path. This process mitigates delays by highlighting blocking issues before they impact the operational planning of a sprint.

Can I use story points for relative estimation during sprint planning?

Yes, relative estimation techniques like story points offer a structured method to gauge effort. This supports sprint planning by providing a consistent measurement for task complexity across the development team.

What is included in a structured sprint retrospective agenda?

A structured sprint retrospective agenda provides specific meeting formats to review past iterations. It facilitates risk management evaluation and process improvements based on the tactical and operational planning levels.

When should I use a risk matrix for software development planning?

A risk matrix should be utilized during strategic planning to identify and assess potential project vulnerabilities. It enables the formulation of mitigation strategies to ensure efficient project execution.