adopt

Audit project artifacts for template compliance and generate a prioritized migration plan.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/emcconnell/nova-scout --skill adopt-emcconnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: adopt
Source: https://github.com/emcconnell/nova-scout/tree/main/.claude/skills/adopt
Command: npx skills add https://github.com/emcconnell/nova-scout --skill adopt-emcconnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audits brownfield project artifacts for template format compliance and detects whether existing GDDs, ADRs, stories, systems index, and infrastructure files will actually work with the template's skills, preventing silent failures and wasted effort when running downstream automation.

Core Features & Use Cases

  • Comprehensive Format Validation: Verifies not only presence but required internal sections and header fields for GDDs, ADRs, systems-index, and stories.
  • Impact Classification: Organises gaps into BLOCKING, HIGH, MEDIUM, and LOW tiers so teams can prioritise fixes that prevent pipeline failures.
  • Actionable Migration Plan: Produces a numbered, ordered adoption plan (docs/adoption-plan-[date].md) with fix commands, manual steps, and time estimates, and offers guided in-place fixes for the most urgent items.
  • Use Case: Run when joining an in-progress game or software project to assess readiness for template-driven skills, or when upgrading from an older template version to avoid silent automation breakage.

Quick Start

Run adopt to silently scan the repository, summarise blocking/high/medium/low gaps, and then write an adoption plan when prompted.

Frequently Asked Questions about adopt

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

FAQPage Schema
How do I audit existing project artifacts for template compliance?

To audit project artifacts for template compliance, run a scan that reads repository files silently and validates required internal sections and header fields for GDDs, ADRs, systems-index, and stories. It classifies gaps into BLOCKING, HIGH, MEDIUM, and LOW tiers.

What is a migration plan for brownfield software onboarding?

A migration plan for brownfield onboarding is a prioritized, ordered remediation document that identifies template format gaps in existing artifacts and provides fix commands with time estimates to prevent silent automation failures.

Can I check if my GDDs and ADRs will work with template-driven skills?

Yes, you can check if GDDs and ADRs will work with template-driven skills by verifying not only their presence but also their required internal sections and header fields, ensuring downstream automation does not silently break.

How do I generate an adoption plan for technical-debt remediation?

To generate an adoption plan for technical-debt remediation, scan the repository to classify artifact format gaps by impact, then write a numbered migration plan with fix commands and manual steps to docs/adoption-plan-[date].md with user confirmation.

What is the best way to upgrade an older template version without breaking automation?

The best way to upgrade an older template version without breaking automation is to audit existing infrastructure and project artifacts for format compliance first, then follow an ordered migration plan to fix BLOCKING and HIGH gaps before running downstream skills.

Why does downstream automation silently fail on brownfield projects?

Downstream automation silently fails on brownfield projects when existing artifacts like GDDs, ADRs, and systems-index files lack required internal sections or header fields, causing template-driven skills to misread or skip critical configuration data.