MCPInstall

milestone

Completes every open issue in a GitHub milestone. Takes one issue at a time to a tested and reviewed pull request. Use when the user asks to finish or deliver a milestone.

Installs
61
Last 24h
—
Trending rank
—
Security
Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/owainlewis/blueprint --skill milestone
  1. 01

    Install

    Run the command in your project. The CLI asks which agents to install for.

  2. 02

    Describe the task

    Ask your agent for something this skill covers. It loads milestone automatically when relevant.

  3. 03

    Review the result

    The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Milestone

Finish every open issue in a GitHub milestone.

Workflow

  1. Resolve the milestone and repository. Inspect its open issues, dependencies, linked pull requests, checks, and current project state.
  2. Order the remaining issues by dependency, risk, and how easy each change will be to review. Put blockers, bugs, and shared foundations before features that depend on them.
  3. Take one issue at a time to a ready pull request. Create the branch and worktree, implement the smallest complete change, test it, review it with a fresh agent, then open the PR. Resume a matching pull request instead of creating duplicate work.
  4. After each pull request is ready, stop for human merge unless the user explicitly allowed merging for this run.
  5. When merging is allowed, merge only when:
    • Required checks pass or are confirmed unconfigured.
    • The pull request is mergeable.
    • Every current comment has a clear outcome.
    • No required change remains unresolved.
    • The description and checklist match the final commit.
  6. Sync the latest remote default branch before starting the next issue.
  7. Refresh the milestone before each issue. Record pull request links, proof, blockers, and final state in the tracker when access permits.
  8. Report completed issues, merged and open pull requests, blockers, checks, and anything not verified.

Boundaries

  • Work only on issues in the milestone.
  • Use one branch and pull request per issue unless combining issues is required for a working result. Explain any combination before starting it.
  • Do not batch unrelated issues.
  • Never merge without explicit permission.
  • Do not merge with failing required checks, missing acceptance criteria, a current comment without a clear outcome, or a required change still open.
  • Do not merge when an acceptance criterion or affected failure path is unverified unless the user accepts that exception.
  • Stop when an issue has unresolved product or technical decisions, requires missing secrets or permissions, already has conflicting work, or grows beyond its acceptance criteria.

FAQ

What does the milestone skill do?

Completes every open issue in a GitHub milestone. Takes one issue at a time to a tested and reviewed pull request. Use when the user asks to finish or deliver a milestone.

How do I install milestone?

Run npx skills add https://github.com/owainlewis/blueprint --skill milestone in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/milestone/ (personal) or .claude/skills/milestone/ (project).

Which AI agents can use milestone?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is milestone safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains milestone?

It is published by owainlewis in owainlewis/blueprint. It has 61 recorded installs.

More from owainlewis/blueprint

View all →

review

owainlewis/blueprint

Uses a fresh agent to review an implementation change without editing it. Checks behavior, security, regressions, complexity, tests, docs, and missing proof. Use for code, PR, diff, security, second-opinion, or pre-merge reviews.

plan

owainlewis/blueprint

Turns a reviewed spec or decided brief into ordered tasks for separate agent runs. Use for implementation tasks, tracker tickets, or useful milestones. Do not use for one coding task or its short execution outline.

task-to-pr

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

spec

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

tdd

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

Testing & QA371 installs

refactor

owainlewis/blueprint

Open the skill to read its SKILL.md instructions.

Popular code quality & workflow skills

View category →

grill-me

mattpocock/skills

A relentless interview to sharpen a plan or design.

Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.

handoff

mattpocock/skills

Compact the current conversation into a handoff document for another agent to pick up.

domain-modeling

mattpocock/skills

Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.

codebase-design

mattpocock/skills

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

diagnosing-bugs

mattpocock/skills

Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.