planning

Creates structured plans with goals, scope, milestones, owners, timelines, and dependencies for projects.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/retz8/iris --skill planning-retz8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/retz8/iris/tree/main/.claude/skills/planning
Command: npx skills add https://github.com/retz8/iris --skill planning-retz8

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams overcome unclear planning and scope creep by providing a universal, repeatable planning framework for both technical and non-technical projects.

Core Features & Use Cases

  • Feature planning: Define scope, objectives, and success criteria for features.
  • System architecture planning: Outline high-level architecture and interfaces before implementation.
  • Goal setting & milestones: Establish SMART goals and phased milestones to track progress.
  • Requirement breakdown & trade-offs: Decompose needs and evaluate trade-offs between options.
  • Resource allocation & risk assessment: Plan people, time, and risks to ensure delivery.
  • Use Cases: Software features, product roadmaps, process improvements, event planning.

Quick Start

Create a high-level plan for your next project by outlining the goal, deliverables, milestones, owners, and a timeline.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I create a project plan that prevents scope creep?

To prevent scope creep, create a project plan that explicitly defines goals, scope, deliverables, owners, timelines, dependencies, and success criteria before execution begins. This structured framework ensures all stakeholders agree on boundaries and expected outcomes upfront.

What is the best way to break down requirements for feature planning?

The best way to break down requirements for feature planning is to decompose high-level needs into structured phases with clear deliverables, assigned owners, and SMART goals. This allows you to evaluate trade-offs between options and track milestones effectively.

Can I use this planning framework for non-technical projects like event planning?

Yes, you can use this planning framework for non-technical projects like event planning, process improvements, and academic projects. It provides a universal structure for setting milestones, allocating resources, and assessing risks across both software and business contexts.

How do I structure milestones and resource allocation for software architecture design?

Structure milestones and resource allocation for software architecture design by outlining high-level interfaces and phased goals, then assigning people and time to each deliverable while assessing potential risks to ensure technical delivery stays on track.

What should be included in a project roadmap to ensure successful delivery?

A project roadmap for successful delivery should include clear goals, defined scope, specific deliverables, assigned owners, realistic timelines, identified dependencies, risk assessments, and measurable success criteria to guide the team from idea to final handoff.