milestone-seal

Create milestone seals listing shipped skills and their interfaces.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill milestone-seal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: milestone-seal
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/milestone-seal
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill milestone-seal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Milestone-driven development requires a verifiable record of what shipped and the interfaces bound to by future milestones. The milestone-seal provides a formal, relocatable artifact that captures each shipped skill with its interface, so next milestones can bind to a known contract without accessing the previous plan.

Core Features & Use Cases

  • Creates a self-contained seal that lists shipped skills and their inline interfaces.
  • Relocates the seal into in-fence planning paths, ensuring isolation from global reports.
  • Enables forward-feed validation by allowing a cold reader to recover the shipped skill and its interface from the seal alone.

Quick Start

Render a milestone seal for a mock milestone by listing shipped skills and their signatures, then render the seal to an in-fence path.

Frequently Asked Questions about milestone-seal

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

FAQPage Schema
How do I document shipped skill interfaces for future milestone binding?

A milestone seal provides a verifiable, self-contained record that lists shipped skills alongside their interface signatures, ensuring future milestones can recover contracts without relying on external reports or previous plans.

How to create a relocatable milestone record for forward-feed validation?

To create a relocatable milestone seal, list your shipped skills and their interface signatures, then render the seal directly into an in-fence planning path to isolate it from global reports and enable forward-feed validation.

Why does milestone-driven development require interface signature enforcement?

Milestone-driven development enforces interface signature presence to guarantee every shipped item has a formal contract, allowing a cold reader to successfully recover the shipped skill and its interface from the seal alone.

Can I isolate milestone documentation from global reports using an in-fence path?

Yes, you can isolate milestone documentation by relocating the generated seal into in-fence planning paths, ensuring the record of shipped skills and their interfaces remains self-contained and segregated from global reports.

What's the best way to validate forward-feed contracts without consulting external references?

The best way to validate forward-feed contracts without external references is to use a milestone seal equipped with a recoverInterface function, providing a self-contained artifact that allows a cold reader to verify shipped skills and interfaces directly.