migrate

Discovers implicit architectural decisions and specifications, converting them into ADRs and RFCs for govctl governance.

239|12|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/govctl-org/govctl --skill migrate-govctl-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate
Source: https://github.com/govctl-org/govctl/tree/main/.claude/skills/migrate
Command: npx skills add https://github.com/govctl-org/govctl --skill migrate-govctl-org

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps adopt a formal governance structure in existing projects that lack one, systematically discovering undocumented decisions and specifications to codify them.

Core Features & Use Cases

  • Project Onboarding: Integrates existing codebases into a governance framework.
  • Discovery & Backfilling: Identifies and documents implicit architectural decisions (ADRs) and existing specifications (RFCs).
  • Source Annotation: Links code to governance artifacts for traceability.
  • Use Case: You've inherited a legacy project with no documentation on key architectural choices. Use this Skill to scan the codebase, identify these decisions, and create ADRs to document them, making the project maintainable.

Quick Start

Use the migrate skill to start onboarding the current project into govctl governance.

Frequently Asked Questions about migrate

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

FAQPage Schema
How do I document undocumented architectural decisions in a legacy codebase?

To document undocumented architectural decisions, this Skill scans project files, code comments, and VCS history to identify implicit governance and backfills these findings into formal ADRs.

How do I onboard an existing project into a formal governance framework?

To onboard an existing project into a formal governance framework, the Skill systematically discovers existing specifications and architectural decisions, codifying them into RFCs and ADRs to establish a governance baseline.

Can I trace source code back to specific architectural decision records?

Yes, you can trace source code to architectural decision records because the Skill annotates source code files with cross-references that link implementation details directly to the generated governance artifacts.

What is the best way to backfill missing RFC specifications for an inherited project?

The best way to backfill missing RFC specifications is using an automated discovery process that scans VCS history and project files to extract implicit specifications and codify them into formal documents.

Does this governance migration process alter existing project files or just add documentation?

The governance migration process adds documentation and annotates source code with cross-references for traceability, establishing a baseline for ongoing governance without fundamentally changing the underlying implementation logic.