adopt

Discover repository foundations and configure verification gates for autonomous development workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams bring existing codebases under a structured autonomous development workflow by discovering the real project foundation instead of rebuilding assumptions from scratch.

Core Features & Use Cases

  • Brownfield Foundation Discovery: Inspects an existing repository to identify stack conventions, data models, integration seams, design language, and project invariants.
  • Keel Workflow Setup: Creates missing foundation artifacts, configures verification gates, and prepares the project for ongoing feature-by-feature development.
  • Use Case: A team adopting an autonomous coding workflow for a mature application can use this Skill to retrofit the project with the necessary specifications and verification process before adding new features.

Quick Start

Use the adopt skill to prepare this existing codebase for keel-managed autonomous development.

Frequently Asked Questions about adopt

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

FAQPage Schema
How do I retrofit an existing codebase for autonomous software development workflows?

Retrofitting existing codebases for autonomous software development requires discovering the real project foundation by inspecting repository architecture, stack conventions, and verification setup. This prepares mature applications for structured feature work without imposing framework-specific assumptions.

What is brownfield foundation discovery and when do I need it?

Brownfield foundation discovery inspects an established repository to identify stack conventions, data models, integration seams, and project invariants. You need it when adopting a structured autonomous coding workflow for a mature application before adding new features.

How do I set up verification gates for an established repository?

Setting up verification gates for an established repository involves configuring workflow gates during the codebase adoption process. This creates missing foundation artifacts and prepares the project for ongoing feature-by-feature autonomous development.

Can I use autonomous development workflows on mature applications without rebuilding from scratch?

Yes, you can apply autonomous development workflows to mature applications by discovering the existing architecture and stack profiles rather than rebuilding assumptions. This codebase adoption approach retrofits the project with necessary specifications and verification processes directly.

Does codebase adoption impose specific framework assumptions on my project?

No, codebase adoption does not impose framework-specific assumptions on your project. It focuses on repository analysis and foundation specification creation based on the actual discovered architecture and stack conventions already present in your existing codebase.