em-planning

Define scope, decompose work into tasks, and estimate effort for engineering initiatives.

Updated Feb 21, 2026
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill em-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: em-planning
Source: https://github.com/hilaryosborne/skills/tree/main/engineering-manager/em-planning
Command: npx skills add https://github.com/hilaryosborne/skills --skill em-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering managers plan projects and initiatives by breaking them down into actionable steps and estimating effort.

Core Features & Use Cases

  • Project Scoping: Define project goals, deliverables, and key milestones.
  • Task Decomposition: Break down large initiatives into smaller, manageable tasks.
  • Effort Estimation: Provide initial estimates for task completion.
  • Use Case: An Engineering Manager needs to plan the rollout of a new feature. They can use this skill to define the scope, break down the work into epics and stories, and get initial time estimates for each.

Quick Start

Use the em-planning skill to plan the rollout of the new user authentication feature.

Frequently Asked Questions about em-planning

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

FAQPage Schema
How do I break down an engineering project into manageable tasks?

Task decomposition breaks large engineering initiatives into smaller, manageable tasks. By defining project scope and desired outcomes, you can structure work into actionable epics and stories for sprint preparation.

What is the best way to estimate effort for a software project rollout?

Effort estimation provides initial time estimates for engineering task completion. It works by taking decomposed project tasks and evaluating required work to generate actionable effort projections for roadmap planning.

How do I define project scope for a new engineering feature?

Project scoping defines engineering goals, deliverables, and key milestones for new initiatives. It requires structured input on desired outcomes to establish clear boundaries and generate actionable team plans.

Can I use this approach for sprint preparation and roadmap planning?

Yes, this planning approach is applicable to sprint preparation and roadmap planning within software development teams. It facilitates project kick-offs by decomposing work and providing effort estimations for upcoming iterations.

What input do I need to plan an engineering team initiative?

Planning engineering initiatives requires structured input on project goals and desired outcomes. Providing clear deliverables and key milestones allows the process to generate actionable plans with task decomposition.