implement-feature

Coordinate multi-milestone feature implementation with dependency-ordered verification and pull request preparation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the challenge of coordinating complex feature implementation across multiple milestones while maintaining verification discipline, branch safety, and user-controlled merging.

Core Features & Use Cases

  • Milestone Orchestration: Sequences implementation and verification of feature milestones in dependency order using dedicated subagents.
  • Verification Governance: Enforces fresh-context verification, commit-pinned records, and independent validation before pull requests are handed off.
  • Use Case: Use this Skill when a fully specified feature needs multiple milestones built, verified, and prepared as correctly based pull requests without autonomous merging.

Quick Start

Use the implement-feature skill to build and verify all milestones for the specified feature after its milestone specifications are complete.

Frequently Asked Questions about implement-feature

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

FAQPage Schema
How do I coordinate feature implementation across multiple milestones without autonomous merging?

You can coordinate feature implementation across multiple milestones using milestone orchestration that sequences development in dependency order and prepares verified pull requests while enforcing user-controlled merge handoff. This prevents unauthorized autonomous merging and maintains branch safety.

What is fresh-context verification for pull request preparation?

Fresh-context verification for pull request preparation is an independent validation process using dedicated verifier agents to test features. It enforces commit-pinned validation records before pull requests are handed off, ensuring code verification discipline independently from the original implementation context.

How do I enforce dependency ordering when building software features?

Dependency ordering for building software features is enforced through milestone orchestration using dedicated subagents. This approach sequences implementation and verification steps, ensuring foundational milestones are completed and validated before dependent feature delivery workflows begin.

Does this feature delivery workflow support GitHub branch rule enforcement?

Yes, the feature delivery workflow supports GitHub branch rule enforcement as part of its verification governance. It maintains branch safety by applying rules during the implementation, independent verification, and pull request handoff phases of the milestone orchestration.

When do I need commit-pinned validation records for feature implementation?

Commit-pinned validation records for feature implementation are needed when a fully specified feature requires multiple milestones to be built and independently verified. They provide traceable proof that fresh-context verification passed before pull request handoff control is transferred to the user.