modernize-assess

Mode. If $ARGUMENTS starts with --portfolio, run Portfolio mode on the directory that follows. Otherwise run Single-system mode on $system, the first token. Flags go after it (<system> --show-secrets): a flag in first place would be read as the system name.

The code is legacy/$system, often a symlink to where it really lives: say where it points (readlink legacy/$system) in one line before you start. If legacy/$system does not exist, stop and say so: nothing can run without the code, so the fix is /code-modernization:modernize $system --source <path to the code>. Run every subagent in the foreground and wait for its result: never end your turn while one is still running.

---

Portfolio mode (--portfolio <parent-dir>)

Sweep every immediate subdirectory and produce a heat-map a steering committee can use to sequence a multi-year program.

If the Workflow tool is available (this command is your authorization), list the subdirectories first (ls -d <parent-dir>/*/ | xargs -n1 basename; the script has no filesystem access), tell the user the count (30 systems means 30 agents), then run one survey agent per system:

Call it by name (the plugin registers it). If the tool does not know the name, pass scriptPath: "${CLAUDE_PLUGIN_ROOT}/workflows/portfolio-assess.js" instead:

Workflow({
  name: "code-modernization:modernize-portfolio-assess",
  args: { parentDir: "<parent-dir>", systems: ["<sub1>", "<sub2>", ...] }
})

Each agent returns a metrics row and the workflow computes the COCOMO index in code, so every row uses the same formula. If the session dies mid-sweep, relaunch with resumeFromRunId and finished systems return from cache. Without the Workflow tool, gather the same row per system yourself.

Per system: SLOC and dominant language (cloc --csv, else scc, else find + wc -l), file count, complexity measured one way for every system (scc's per-file complexity summed, divided by KSLOC, and the most complex single file; without scc, count decision keywords the same way everywhere), dependency freshness (age or pinned-version count of the manifest), documentation coverage (source files whose opening comment describes the file, not just a license, and architecture docs present), and the COCOMO index 2.94 × KSLOC^1.10. The index is a relative size measure for ranking systems, never a timeline or a cost (it assumes human-team productivity): label the column "index", never print person-months, a date or a duration.

Write analysis/portfolio.html (dark #1e1e1e background, #d4d4d4 text, #cc785c accent, system-ui, CSS inline): one row per system, columns System · Lang · KSLOC · Files · Complexity per KSLOC · Most complex file · Dep Freshness · Doc Coverage % · Complexity index · Risk, index and Risk cells graded green to red, and a 2–3 sentence recommendation of which system goes first and why. Tell the user to open it, then stop.

---