baek-labs

You can elicit and validate project intent into a 3-doc handoff/spec/plan (ready), execute that plan with wave-based parallel implementation and integration gates (go), migrate existing projects into the dryforge documentation system (migration), diagnose and configure Hames installations (doctor, setup), and audit workspace file indexing and organization rules (index).

They target software engineers and technical leads who want structured, spec-first development: turning loose goals or notes into validated plans, executing them with test-first verification, and keeping existing codebases documented with CLAUDE.md, AGENTS.md, and per-module documentation harnesses.

Invoke ready first with any input — a goal, existing docs, or notes — to interactively produce an execution-ready handoff, spec, and plan. Then invoke go, which reads that 3-doc and runs wave-based parallel implementation with right-sized verification, spec-first review, and integration gates.

The ready, go, and migration skills explicitly require git to be available in the environment. The migration skill additionally operates on an existing project codebase, while doctor, setup, and index run within the current project or workspace when invoked via their slash commands.

Yes. The migration skill reads the existing codebase, interactively elicits knowledge the code cannot reveal, and generates a full project harness: CLAUDE.md or AGENTS.md at the root, a docs/ directory, and per-module AGENTS.md files following the dryforge documentation system.