AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

doc-and-modernize

Two related workflows for a locally-cloned codebase, in one skill. Documentation mode produces a single, comprehensive, verifiable architecture document primarily by reading files on disk (local-first) — use it whenever the user wants to understand, map, document, research, or onboard onto a codebase ("research this repo", "write up the architecture", "do an architecture deep dive", "document how this codebase works", "map the system design", "create an onboarding doc"). Modernization mode generates a phased plan to modernize, migrate, upgrade, or rewrite a legacy system ("modernize this", "plan the migration", "how would we rewrite this", "how do we get off this legacy stack"); if no architecture document exists yet it first runs Documentation mode, then continues straight through to the plan. It assumes the legacy stack may be dead, runs a time-boxed feasibility spike, and picks the highest achievable rung on a safety ladder instead of demanding a fully-green legacy CI gate up front.

Original source
github
License
MIT
Pinned revision
5269f7ea2d6c3a9bfda5ed878b6726cf509121fd

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

Ask your assistant

Use Agentic Memory skills to read github--doc-and-modernize at revision 5269f7ea2d6c3a9bfda5ed878b6726cf509121fd, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 3

SKILL.md · 48000

Testability Milestone per component and never require a component's automated test gate before that component crosses its own testability line.

  • Name the CI Milestone, hand enforcement to a human. State which phase stands up CI (the first lit phase), and make explicit that turning CI into an enforced required check / branch-protection rule is a manual platform step the agent cannot do — surface it as a user action item, not a done task.
  • Net the seams, not the corpse. Anchor safety at externally observable contracts (protocols, schemas, wire/file formats, endpoints) with a ranked oracle (running instance → recorded I/O → code-as-spec → self-frozen golden master when no external reference exists or is permitted). Don't sink sprints resurrecting a dead toolchain just to run a test that gets deleted at rewrite.
  • Keep it generic. Express commands and gates in terms of the project's package manager / test runner / CI — never assume a specific stack.
  • Red-team every phase before implementing (H1–H8). Walk each phase plan against references/migration-hazards.md and fold the fixes into tasks/exit criteria first — a hazard caught in planning is a task; in review, rework; in prod, an incident. These tactical hazards (incomplete quarantine, framework codemods, runtime/base-image lockstep, route-class enumeration, data-store upgrade paths, transitional-insecure-state noise, stacked-PR/trunk drift, living-doc drift) are what strategic scaffolding alone keeps missing.