milestone-coverage

Merge product outcome proposals with technical sequencing into milestone plans.

3|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/infraspecdev/tesseract --skill milestone-coverage
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-coverage
Source: https://github.com/infraspecdev/tesseract/tree/main/shield/skills/general/milestone-coverage
Command: npx skills add https://github.com/infraspecdev/tesseract --skill milestone-coverage

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams turn a feature into a clear milestone scaffold when a PRD has no milestones yet or when a plan needs a fallback structure. It combines product outcome thinking with technical sequencing so teams can move from vague goals to an editable, testable roadmap.

Core Features & Use Cases

  • Parallel Perspective Merging: Runs a product-manager lens and an agile-coach lens in parallel, then merges the two proposals into one milestone plan.
  • Conflict Surfacing: Detects disagreements in dependencies or sizing and returns them as explicit open conflicts for user resolution.
  • PRD and Plan Support: Works for standard PRDs, lean PRDs, and plan workflows that need milestone scaffolding from goals and personas alone.
  • Testable Outputs: Produces milestones with outcomes, exit criteria, dependencies, and source attribution so the result is ready for review and approval.

Quick Start

Use the milestone coverage skill to propose a merged milestone scaffold for this feature based on the provided personas, goals, stories, and success metrics.

Frequently Asked Questions about milestone-coverage

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

FAQPage Schema
How do I create milestone plans from a lean PRD that has no milestones yet?

Conflict surfacing detects disagreements in dependencies or sizing between the product-manager and agile-coach perspectives, returning them as explicit open conflicts for user resolution before finalizing the milestone plan.

How do I merge product outcome proposals with technical sequencing for sprint planning?

Merging product outcomes with technical sequencing is done by running a product-manager lens and an agile-coach lens in parallel, then combining both proposals into a single milestone scaffold with source attribution and dependencies.

What do I need to generate a testable milestone scaffold for a new feature?

Generating a testable milestone scaffold requires validated personas, goals, optional stories, and success metrics as inputs, which the system uses to produce outcomes, exit criteria, and dependencies ready for review and approval.

How do I surface dependency conflicts when scaffolding product milestones?

Conflict surfacing detects disagreements in dependencies or sizing between the product-manager and agile-coach perspectives, returning them as explicit open conflicts for user resolution before finalizing the milestone plan.

Can I build a milestone fallback structure using only personas and goals?

Building a milestone fallback structure from personas and goals alone is supported when milestone structure is missing, applying dependency analysis and technical sequencing to produce testable outcomes and exit criteria.