implement-milestone

Build a software milestone from done-conditions with branch isolation and committed tests.

1|Updated Jun 29, 2026
One-click install
npx skills add https://github.com/mckissinger/keel --skill implement-milestone-mckissinger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: implement-milestone
Source: https://github.com/mckissinger/keel/tree/main/skills/implement-milestone
Command: npx skills add https://github.com/mckissinger/keel --skill implement-milestone-mckissinger

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill prevents unverified milestone work by enforcing a structured build process that separates implementation from independent verification and protects the integrity of the delivery workflow.

Core Features & Use Cases

  • Milestone Implementation Workflow: Builds a single milestone from an existing specification, following branch-first development, done-conditions, required tests, and stack-specific verification requirements.
  • Quality and Safety Gates: Enforces branch isolation, stop-points, test authoring, and handoff rules so implementation does not self-verify or merge unverified changes.
  • Use Case: When a feature has approved milestone specifications, use this Skill to implement one milestone, commit the work on its branch, and prepare it for a separate verification pass.

Quick Start

Use the implement-milestone skill to build the specified milestone from its existing specification and prepare it for independent verification.

Frequently Asked Questions about implement-milestone

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

FAQPage Schema
How do I implement a software milestone while preventing unverified changes from entering the main branch?▼

To implement a milestone safely, use a structured build process that enforces branch isolation, commits tests alongside implementation, and separates independent verification to protect delivery workflow integrity.

What is branch isolation in autonomous development workflows?▼

Branch isolation is a delivery safety gate that builds milestones on separate branches, preventing unverified code from entering the main branch and ensuring implementation work does not self-verify before handoff.

How do I prepare milestone specifications for an autonomous development workflow?▼

You prepare milestones by defining done-conditions, feature plans, stack profiles, and verification handoffs so the implementation phase can execute tasks governed by the specification.

Can I merge milestone implementation and verification tasks together in a single step?▼

No, this workflow requires separating implementation from independent verification to maintain delivery integrity, enforcing stop-points and handoff rules so implementation does not self-verify or merge unverified changes.

What's the best way to enforce quality gates during milestone implementation?▼

The best way to enforce quality gates is by applying committed test authoring, branch isolation, and stack-aware execution rules governed by the milestone specification throughout the implementation process.

Do I need existing milestone specifications before starting branch-first development?▼

Yes, you need approved milestone specifications with defined done-conditions and stack profiles before implementation, as the build process executes tasks governed by these existing requirements.