doc-and-modernize

Topics in the source

• Documentation & Modernization
• Mode selection
• Documentation mode
• Why local-first
• Workflow
• Output structure
• Part 1 — Whole-repo technical deep-dive
• Part 2 — Context & ecosystem

Two complementary workflows for a repository the user already has checked out locally, bundled as one skill: Documentation mode — produce one definitive, cited architecture document from the code on disk. Ideal for onboarding, system-design maps, or as the evidence base for a modernization effort. Modernization mode — turn that architecture into a phased, safety-laddered plan to upgrade, migrate, or rewrite a legacy system. If the user wants to understand, document, map, research, or onboard onto a codebase, run Documentation mode. If the user wants to modernize, migrate, upgrade, or rewrite a system, run Modernization mode. Modernization mode is self-sufficient: if no architecture document exists yet, it runs the Documentation mode workflow first (in the same pass), then continues straight through to the plan. When in doubt, produce the architecture document first — it is the audited evidence base both modes rely on. Generate one definitive, cited architecture document for a repository the user already has checked out locally. The goal is a writeup someone could hand to a new engineer as their onboarding reference — broad enough to cover the whole system, deep enough on the hard p

This is an excerpt. Refer to the complete source and its current requirements.