milestone

Name: milestone
Author: owainlewis

238stars46forks

How to install milestone?

owainlewis/blueprint/milestone

$npx -y skills add owainlewis/blueprint --skill milestone

Installs into the current project.

Summary

Completes all open GitHub issues in a milestone by running the task-to-pr skill one issue at a time. Use when the user asks to complete, deliver, work through, or finish a GitHub milestone.

Files · 1

View on GitHub

SKILL.md

1	# Milestone
2
3	Finish every open issue in a GitHub milestone.
4
5	## Workflow
6
7	1. Resolve the milestone and repository. Inspect its open issues, dependencies, linked pull requests, checks, and current project state.
8	2. Order the remaining issues by dependency, risk, and reviewability. Put blockers, bugs, and shared seams before dependent feature work.
9	3. Take one issue at a time through `/task-to-pr`. Resume a matching pull request instead of creating duplicate work.
10	4. After each pull request is ready, stop for human merge unless the user explicitly allowed merging for this run.
11	5. When merging is allowed, merge only after required checks and review are clean. Sync the latest remote default branch before starting the next issue.
12	6. Refresh the milestone before each issue. Record pull request links, proof, blockers, and final state in the tracker when access permits.
13	7. Report completed issues, merged and open pull requests, blockers, checks, and anything not verified.
14
15	## Boundaries
16
17	- Work only on issues in the milestone.
18	- Use one branch and pull request per issue unless combining issues is required for a working result. Explain any combination before starting it.
19	- Do not batch unrelated issues or reimplement the inner delivery workflow.
20	- Never merge without explicit permission.
21	- Do not merge with failing checks, important unresolved feedback, missing acceptance criteria, or unexplained test gaps.
22	- 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.

People who liked this also viewed

6 picks

Type

milestone

238stars46forks

View on GitHub

How to install milestone?

owainlewis/blueprint/milestone

$npx -y skills add owainlewis/blueprint --skill milestone

Installs into the current project.

Summary

Completes all open GitHub issues in a milestone by running the task-to-pr skill one issue at a time. Use when the user asks to complete, deliver, work through, or finish a GitHub milestone.

Files · 1

View on GitHub

SKILL.md

1	# Milestone
2
3	Finish every open issue in a GitHub milestone.
4
5	## Workflow
6
7	1. Resolve the milestone and repository. Inspect its open issues, dependencies, linked pull requests, checks, and current project state.
8	2. Order the remaining issues by dependency, risk, and reviewability. Put blockers, bugs, and shared seams before dependent feature work.
9	3. Take one issue at a time through `/task-to-pr`. Resume a matching pull request instead of creating duplicate work.
10	4. After each pull request is ready, stop for human merge unless the user explicitly allowed merging for this run.
11	5. When merging is allowed, merge only after required checks and review are clean. Sync the latest remote default branch before starting the next issue.
12	6. Refresh the milestone before each issue. Record pull request links, proof, blockers, and final state in the tracker when access permits.
13	7. Report completed issues, merged and open pull requests, blockers, checks, and anything not verified.
14
15	## Boundaries
16
17	- Work only on issues in the milestone.
18	- Use one branch and pull request per issue unless combining issues is required for a working result. Explain any combination before starting it.
19	- Do not batch unrelated issues or reimplement the inner delivery workflow.
20	- Never merge without explicit permission.
21	- Do not merge with failing checks, important unresolved feedback, missing acceptance criteria, or unexplained test gaps.
22	- 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.

People who liked this also viewed

6 picks

Type