migration

Convert an existing codebase into a dryforge documentation harness with CLAUDE.md, AGENTS.md, and docs.

5|1|Updated May 8, 2026
One-click install
npx skills add https://github.com/baek-labs/hames --skill migration-baek-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: migration
Source: https://github.com/baek-labs/hames/tree/main/packages/claude/integrations/dryforge/upstream/migration
Command: npx skills add https://github.com/baek-labs/hames --skill migration-baek-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Existing projects often lack durable documentation that captures intent, constraints, and decisions that code alone cannot express, leaving future agents and developers without reliable project memory. ## Core Features & Use Cases - Codebase Scanning: Reads directory structure, code patterns, existing docs, external dependencies, and git history to build a technical manifest of the project. - Guided Elicitation: Asks the user targeted questions to extract domain knowledge, business invariants, and security policies that code cannot reveal. - Harness Generation: Produces CLAUDE.md / AGENTS.md entry files, a seven-document docs/ set with ADRs, and per-module AGENTS.md files, verified by an independent review subagent. - Use Case: Point the skill at a legacy repository with no documentation; it scans the code, interviews you about business rules, and generates a complete documentation harness ready to commit. ## Quick Start Invoke the migration skill on your existing git project and answer its questions to generate the full documentation harness.

Frequently Asked Questions about migration

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

FAQPage Schema
How do I generate documentation for an existing codebase?▼

Invoke the migration skill on your project with no arguments. It scans the directory structure, code patterns, and git history, asks you targeted questions about domain rules, then generates CLAUDE.md, AGENTS.md, a docs/ set, and per-module AGENTS.md files.

What files does the dryforge migration harness create?▼

It creates CLAUDE.md and AGENTS.md with identical content, seven core docs plus tracking files (status.md, decisions/index.md, findings.md), an ADR for each confirmed trade-off decision, and one AGENTS.md per identified module.

Does the migration skill require git?▼

Yes, git is required. If the project is not a git repository, the skill offers to run git init and make an initial commit, since later workflow steps need a HEAD for worktrees. If git is not installed, the skill stops.

Can I use migration on a new project with no code?▼

No, migration expects an existing codebase to convert. For greenfield projects with no code yet, use the ready skill instead, which designs the first cycle and lets go create the harness from scratch.

Does migration commit the generated documentation automatically?▼

No, migration writes files but performs no commits or branch operations. It backs up existing entry files to .dryforge/backup/, gitignores .dryforge/, and reminds you to commit the harness yourself before running ready and go.