milestone-coverage

milestone-coverage is a skill for Claude Code from infraspecdev/tesseract. It costs 84 tokens per session (1,246 once invoked), scanned A, original, MIT.

A helper that proposes project milestones from product goals, user types, user stories, and success measures.

In plain words
What is it for?
Use it while creating a PRD or plan to generate a milestone proposal that can be edited and reviewed.
Why use it?
It gives a feature a staged delivery outline when the product requirements or plan does not already define milestones.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the shield plugin — 36 skills, 17 commands, 22 agents shipped together

Good fit Use it while creating a PRD or plan to generate a milestone proposal that can be edited and reviewed.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/infraspecdev/tesseract/milestone-coverage
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add infraspecdev/tesseract --skill milestone-coverage
Clone the repo
git clone --depth 1 https://github.com/infraspecdev/tesseract

Made for: Claude Code.

Or install shield, the plugin that ships this one along with the rest of its 36 skills, 17 commands, 22 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for milestone-coverage

README.md
[![agentmods](https://agentmods.dev/badge/skills/infraspecdev/tesseract/milestone-coverage/github.svg)](https://agentmods.dev/skills/infraspecdev/tesseract/milestone-coverage)
Your own site
<a href="https://agentmods.dev/skills/infraspecdev/tesseract/milestone-coverage"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/milestone-coverage/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for milestone-coverage

Your own site · 80×15
<a href="https://agentmods.dev/skills/infraspecdev/tesseract/milestone-coverage"><img src="https://agentmods.dev/badge/skills/infraspecdev/tesseract/milestone-coverage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,246 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.01246
Opus 5.5 $0.00034 $0.00498
Sonnet 5.5 $0.00017 $0.00249
Haiku 4.5 $0.00008 $0.00125

Measured 1mo ago against content hash 175bbf437d9b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

milestone-coverage scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

shield/skills/general/milestone-coverage/SKILL.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Milestone Coverage

Propose a milestone scaffold for a feature by dispatching a PM-lens general-purpose Agent and shield:agile-coach in parallel and merging their outputs into a single user-editable proposal. The PM-lens prompt lives inline in templates.md (post pm-restructure-v0; previously this dispatched the omnibus shield:product-manager agent which has been decomposed).

When to Use

  • /prd invokes this after Section 8 (User stories) is filled in the standard scaffold, or after Section 7 (Success metrics) in the lean scaffold, to scaffold the Milestones table.
  • /plan invokes this as a fallback when the linked PRD has no milestones (or no PRD exists), to populate the sidecar milestones[].

Input contract

The caller provides:

  • personas: list of {id, name, goals[]} (always required)
  • goals: list of {id, description} (always required)
  • stories: list of story objects from PRD §8 (required for standard; absent for lean — skill falls back to coarser proposals from goals+personas)
  • feature_domain: best-effort domain hint (same set as shield:story-coverage)
  • success_metrics: optional; used by PM agent to anchor outcomes to metrics

Output contract

Return a single merged milestone proposal:

{
  "milestones": [
    {
      "id": "M1",
      "name": "Login core",
      "outcome": "Users can log in with email + password",
      "exit_criteria": [
        "Login endpoint returns 200 + session token on valid credentials",
        "Rate limiting active on login endpoint"
      ],
      "depends_on": [],
      "source_agents": ["product-manager", "agile-coach"],
      "conflicts": []
    }
  ],
  "open_conflicts": [
    {
      "field": "depends_on",
      "milestone_id": "M2",
      "pm_proposal": [],
      "agile_coach_proposal": ["M1"],
      "explanation_pm": "PM sees recovery as independent of login UI changes",
      "explanation_agile_coach": "Recovery needs the session middleware shipped in M1"
    }
  ]
}

open_conflicts is what the caller surfaces to the user for resolution. conflicts per-milestone is set to [] when both agents agreed.

Read the full file on GitHub · 103 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 103 lines · 84 tokens per session scan A 175bbf437d9b

Subscribe to this mod's changes

milestone-coverage is a skill published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 84 tokens to every session and 1,246 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.