pm-plan

Turn vague project ideas into a structured sprint plan with scope and ownership.

3|Updated May 28, 2026
One-click install
npx skills add https://github.com/mahg-es/araya --skill pm-plan-mahg-es
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-plan
Source: https://github.com/mahg-es/araya/tree/main/skills/pm-plan
Command: npx skills add https://github.com/mahg-es/araya --skill pm-plan-mahg-es

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plans for sprints or project phases are often ambiguous, leading to misaligned expectations and delivery delays. This skill provides a structured sprint plan with clear scope, prioritization, effort estimates, and assigned owners to accelerate alignment and execution.

Core Features & Use Cases

  • Sprint planning: create a prioritized backlog, scope, goals, and a plan for the upcoming iteration.
  • Task estimation & ownership: assign effort estimates and designate a single owner per task, with clear dependencies.
  • Dependency mapping & timeline: identify blocking relationships and draft a delivery timeline.

Quick Start

Create a sprint plan for the upcoming release and write it to .araya/plan/spec/sprint-plan.md.

Frequently Asked Questions about pm-plan

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

FAQPage Schema
How do I create a sprint plan with clear scope and ownership from vague project ideas?

A sprint plan defines a prioritized backlog, iteration goals, task estimates, designated owners, and dependency mapping to prevent ambiguous project phases from causing misaligned expectations and delivery delays.

What's the best way to map task dependencies and ownership for an upcoming release backlog?

Mapping task dependencies for a backlog involves identifying blocking relationships, assigning a single owner per task, and drafting a delivery timeline to produce a structured sprint plan document.

When do I need to formalize Definition of Done and effort estimates for sprint planning?

You need to formalize Definition of Done and effort estimates at sprint starts or phase transitions across product, engineering, and design teams to ensure clear scope definition and shared delivery expectations.

Does sprint planning work for phase transitions across product, engineering, and design teams?

Yes, sprint planning applies at sprint starts or phase transitions across product, engineering, and design teams to structure vague ideas into shared priorities, estimates, and assigned task ownership.

How do I structure a deliverable sprint plan document for engineering teams?

You structure a deliverable sprint plan document by defining scope, prioritizing the backlog, mapping dependencies, assigning single owners per task, and establishing a Definition of Done for engineering execution.