milestone-burndown

Automates GitHub milestone management, issue implementation, review, and merging.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/acmiyaguchi/fen --skill milestone-burndown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-burndown
Source: https://github.com/acmiyaguchi/fen/tree/main/.claude/skills/milestone-burndown
Command: npx skills add https://github.com/acmiyaguchi/fen --skill milestone-burndown

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the implementation, review, and merging of GitHub milestones, streamlining the process of driving milestones to zero open issues.

Core Features & Use Cases

  • Autonomous Milestone Management: Automates the picking, implementing, reviewing, and merging of issues within a GitHub milestone.
  • Adversarial Review: Implements an adversarial review process using different providers to ensure high-quality code.
  • Escalation and Retry Logic: Handles rate limits and outages by switching providers and provides a mechanism for escalating issues.
  • Compact and Release: Automates the compacting of orchestrator state and release process when milestones are completed.

Quick Start

To start using the milestone-burndown skill, simply provide the skill with the name of the milestone you wish to burndown.

Frequently Asked Questions about milestone-burndown

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

FAQPage Schema
How do I automate GitHub milestone management to drive open issues to zero?

GitHub milestone management can be automated by orchestrating the picking, implementing, reviewing, and merging of issues. This process continuously works through open issues until the milestone reaches zero remaining items.

What is adversarial code review and how does it work for issue resolution?

Adversarial code review uses a two-tiered model with different providers to implement and review issues independently. This mechanism ensures higher quality code by validating implementations against a separate evaluation layer.

How do I handle rate limits and outages during automated issue resolution?

Automated issue resolution handles rate limits and outages by automatically switching providers. It includes escalation and retry logic to ensure the milestone burndown process continues despite temporary API failures.

Can I automate the release process for completed GitHub milestones?

Yes, completed GitHub milestones can be automatically released. The automation compacts the orchestrator state and triggers a release mechanism once all issues within the milestone are successfully merged.

What do I need to provide to start automating issue resolution for a milestone?

To start automating issue resolution, you simply need to provide the name of the GitHub milestone you wish to burndown. The automation then autonomously manages the remaining implementation steps.

Are there limitations when using different providers for code review?

Using different providers for code review depends on provider availability and API stability. The system mitigates these limitations by switching providers during outages, but requires at least two accessible providers for the adversarial review process.