planning

Structure backlog, sprint plans, and architecture decisions with dependency mapping.

94|49|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/josipjelic/orchestrated-project-template --skill planning-josipjelic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/josipjelic/orchestrated-project-template/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/josipjelic/orchestrated-project-template --skill planning-josipjelic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides structured guidance to plan and organize work, aligning backlog, sprint scope, and architecture decisions to deliver predictable outcomes.

Core Features & Use Cases

  • ICE scoring framework to prioritise backlog items with transparent rationale.
  • Dependency graph thinking to sequence tasks, identify blockers, and map the critical path.
  • Risk identification and spike task planning to de-risk uncertainty before committing to work.
  • Definition of Done and sprint health signals to maintain quality and momentum.

Quick Start

Create your first backlog item, score it with ICE, map its dependencies, and propose the next sprint plan.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I prioritize my product backlog with ICE scoring?

ICE scoring prioritizes backlog items by evaluating Impact, Confidence, and Ease, providing a transparent rationale for sequencing tasks. This framework helps product teams objectively rank features and align sprint scope with highest-value work.

What is the best way to map dependencies and identify blockers for sprint planning?

Dependency graph thinking maps task relationships to sequence work, identify blockers, and establish the critical path. This approach ensures teams coordinate tasks across multiple domains and anticipate blockers before committing to sprint scope.

How do I plan spike tasks to de-risk project uncertainty?

Risk identification and spike task planning de-risk uncertainty by allocating focused research time before committing to full implementation work. This allows teams to validate assumptions, resolve unknowns, and satisfy governance requirements for task review.

Can I use this for architecture decision records and cross-domain task governance?

Yes, this maps and optimizes project work by structuring architecture decisions and governance of task creation and review across multiple domains. It aligns sprint plans with ADRs to deliver predictable outcomes for product teams.

When should I not use ICE scoring for backlog prioritization?

ICE scoring may not suit contexts requiring purely qualitative prioritization or where Impact, Confidence, and Ease metrics cannot be meaningfully estimated. In such cases, alternative prioritization frameworks offering different evaluation criteria should be considered.