skills.rest
Kohlex
KohlexOFFICIAL
Explore all skills by this author →
WebsiteGitHub

brownfield-onboard

Orchestrate brownfield onboarding by ingesting planning docs, mapping codebases, and emitting staged artifacts.

Updated Jun 4, 2026
Search Tags:#automation#planning#documentation#codebase#reconciliation#brownfield#onboard
One-click install
npx skills add https://github.com/Kohlex/autopilot-plugin --skill brownfield-onboard
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brownfield-onboard
Source: https://github.com/Kohlex/autopilot-plugin/tree/main/skills/brownfield-onboard
Command: npx skills add https://github.com/Kohlex/autopilot-plugin --skill brownfield-onboard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Onboard an existing-WIP product to AutoPilot conventions by orchestrating ingestion of pre-AutoPilot planning documents, mapping of the codebase, and reconciliation to AutoPilot requirements.

Core Features & Use Cases

  • Ingest pre-AutoPilot planning docs (e.g., ADRs, PRDs, SPECs) and map them into AutoPilot planning structures.
  • Inventory and analyze the existing codebase to produce architecture and codebase awareness artifacts.
  • Reconcile ingested docs and codebase against AutoPilot conventions, archiving conflicts when needed.
  • Emit capabilities.yaml with statuses that reflect retroactive MERGED for existing code and PLANNED for unfinished work.
  • Hand off to /autopilot to begin the composed loop.

Quick Start

Run /brownfield-onboard <product> to start onboarding the existing codebase into AutoPilot conventions.

Frequently Asked Questions about brownfield-onboard

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

FAQPage Schema
How do I onboard an existing codebase to AutoPilot conventions?▼

Onboard an existing codebase by orchestrating ingestion of pre-AutoPilot planning documents, mapping the codebase, and reconciling outputs to produce a retroactive MERGED state for existing code.

What planning documents are needed to map a brownfield project into AutoPilot?▼

Pre-AutoPilot planning documents such as ADRs, PRDs, and SPECs are ingested and mapped into AutoPilot planning structures during the brownfield onboarding workflow.

How does brownfield onboarding handle existing code that conflicts with new planning docs?▼

Brownfield onboarding reconciles ingested docs and codebase against AutoPilot conventions, archiving conflicting documents when needed to produce a clean merged state.

Can I preview codebase mapping results before promoting them to the live planning directory?▼

Yes, the workflow supports a read-only preview of staged artifacts before promoting them into the live .planning/ directory on a dedicated brownfield onboarding branch.

What artifacts are generated when reconciling an existing product to AutoPilot?▼

The workflow emits a .planning-staged/ artifact set including codebase maps, reconciliations, and a capabilities.yaml reflecting retroactive MERGED statuses for existing code.

Does brownfield onboarding validate outputs against a specific schema?▼

Yes, the workflow validates all emitted planning artifacts against AutoPilot's schema before they are ready for validation and promotion to the live environment.

Related Skills

Explore More Software Engineering Skills→
Elmanuel1Elmanuel1

prd-to-features

Convert Confluence PRDs into per-repo story specs and synchronized Jira tickets.

Community
Advanced
officechbusinessservices-creatorofficechbusinessservices-creator

autopilot

Automate end-to-end software delivery from product idea to working codebase.

Community
Advanced
KohlexKohlex

stakeholder-risks-generator

Aggregate risk signals from YAML, JSON logs, and architecture notes into a deduplicated RISKS.md register.

Official
Advanced
alexandersumeralexandersumer
1

reconcile-plan

Reconcile structured planning state with code reality using diffs and artifacts.

Community
Advanced