What problem does it solve? When you inherit an existing codebase with no documentation, or have outdated keel docs that no longer match the current specification, you lack a trustworthy project baseline. This Skill investigates the project, verifies claims against actual code, and produces a source-annotated baseline document—or migrates legacy keel documentation to the current numbered spec. ## Core Features & Use Cases - Project Baseline Creation: Investigates README, CHANGELOG, git history, issues, and real build/test runs, then writes docs/devdocs/00-baseline.md with four-tier source annotations (user-confirmed, documented, inferred-pending, unknown). - Legacy Version Migration: Detects non-compliant keel docs, generates a diff checklist, and migrates numbering (F/US/AC/UT/IT/E2E), file renames via git mv, and traceability matrices after user confirmation. - Evidence Verification: Cross-checks every verifiable documentation claim against the code, recording conflicts instead of silently trusting stale docs. - Use Case: You take over a half-finished project with a two-year-old README. Run the Skill to get an honest baseline that marks what is confirmed, what conflicts with the code, and what remains unknown—so the next session knows exactly what not to trust. ## Quick Start Ask the AI to retrofit this existing project into the keel workflow by scanning the repo and establishing a documented baseline.
