skills.rest
erikhazzard
erikhazzardCOMMUNITY
Explore all skills by this author →
Website𝕏@erikhazzardGitHub

plan__creating-milestones

Plan production-ready milestones with user journeys and acceptance criteria.

1|1|Updated Mar 16, 2026
Search Tags:#planning#milestones#test-driven#acceptance-criteria#user-journey#feature-development#milestone-ladder
One-click install
npx skills add https://github.com/erikhazzard/vasir --skill plan-creating-milestones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plan__creating-milestones
Source: https://github.com/erikhazzard/vasir/tree/main/.agents/skills/plan__creating-milestones
Command: npx skills add https://github.com/erikhazzard/vasir --skill plan-creating-milestones

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creates test-driven milestones for complex features that anchor work to user journeys, invariants, and measurable acceptance criteria.

Core Features & Use Cases

  • Milestone ladder (M1..Mn) with production-ready endpoints
  • Documentation of user journeys, experience invariants, goals, and scope boundaries
  • Acceptance criteria, risk assessment, and rollback planning
  • Clear guidance for multi-step feature planning and test coverage

Quick Start

Describe the next milestone plan for a feature, including the user journey, invariants, goals, scope boundaries, acceptance criteria, and risks.

Frequently Asked Questions about plan__creating-milestones

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

FAQPage Schema
How do I plan production-ready milestones for complex multi-team feature development?▼

Production-ready milestones are planned by defining a milestone ladder from initial concept to shippable increments, documenting user journeys, scope boundaries, acceptance criteria, and rollback plans.

What are test-driven milestones and how do they anchor feature development to user journeys?▼

Test-driven milestones anchor feature development by enforcing documentation of user journeys, experience invariants, and measurable acceptance criteria across each shippable increment.

How do I document acceptance criteria and experience invariants for a feature milestone plan?▼

Acceptance criteria and experience invariants are documented within the milestone plan by defining goals, scope boundaries, performance budgets, and risks for each step of the user journey.

Can I use this milestone planning approach for multi-team product initiatives?▼

Yes, this milestone planning approach applies to multi-team product initiatives by guiding milestone definitions across scope, invariants, and risk considerations from concept to shippable increments.

What is the best way to structure a milestone ladder with shippable endpoints?▼

The best way to structure a milestone ladder is to define sequential production-ready endpoints (M1..Mn) that each include documented goals, risks, performance budgets, and rollback plans.

Why does feature planning need risk assessment and rollback plans for each milestone?▼

Feature planning needs risk assessment and rollback plans to ensure each milestone increment remains production-ready, maintaining scope boundaries and experience invariants throughout the user journey.

Related Skills

Explore More Product & Management Skills→
silaslopes100silaslopes100

reversa-researcher

Convert raw product ideation data into structured user personas and customer journey maps.

Community
Intermediate
PacificStudioPacificStudio
264

task-breakdown

Convert clarified specs into OpenASE tickets with dependency edges.

Official
Advanced
qa-amanqa-aman
19

qa-strategy

Generate a formal QA test strategy document with scope, risks, and coverage matrix.

Community
Advanced
ForgePlanForgePlan
3

sprint

Orchestrate multi-agent feature sprints with wave-based execution and evidence capture.

Official
Advanced