Writing Plans

Generate milestone-based plans with dependencies, risks, and validation criteria.

577|62|Updated May 15, 2026
One-click install
npx skills add https://github.com/agentic-in/elephant-agent --skill writing-plans-agentic-in
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Writing Plans
Source: https://github.com/agentic-in/elephant-agent/tree/main/packages/skills/builtin_packages/software-development/writing-plans
Command: npx skills add https://github.com/agentic-in/elephant-agent --skill writing-plans-agentic-in

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design teams and product teams struggle to create concrete, executable plans from vague objectives. This skill provides a structured way to translate goals into actionable milestones with clear dependencies and validation.

Core Features & Use Cases

  • Generate milestone-based plans from a goal.
  • Capture dependencies, risks, and validation criteria.
  • Use case: plan a feature rollout with a two-week sprint cadence and risk mitigations.

Quick Start

Outline a milestone-based plan from a given goal, including milestones, dependencies, risks, and validation criteria.

Frequently Asked Questions about Writing Plans

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

FAQPage Schema
How do I create an execution plan from a vague product goal?

To create an execution plan from a vague product goal, you translate the objective into structured milestones. This process captures dependencies, risks, and validation criteria to ensure the resulting roadmap is actionable and traceable.

What is milestone-based planning for feature rollouts?

Milestone-based planning for feature rollouts breaks down a target objective into discrete, executable phases. It structures the development roadmap by defining specific milestones alongside their dependencies and required validation criteria.

How do I plan a two-week sprint cadence with risk mitigations?

To plan a two-week sprint cadence with risk mitigations, you structure the timeline around clear milestones. The plan must explicitly capture identified risks, outline mitigation strategies, and define validation criteria for each sprint.

Does project roadmapping require capturing dependencies and constraints?

Project roadmapping requires capturing dependencies and constraints to ensure risk-aware execution. Structured plans preserve intent and scope by mapping these elements directly to milestones and defining clear success criteria.

What's the best way to structure traceability in a feature planning roadmap?

The best way to structure traceability in a feature planning roadmap is to link every milestone to explicit validation criteria and dependencies. This ensures the execution plan preserves the original intent and scope throughout development.