maturity-analysislisted

# Skill: maturity-analysis Performs a deep end-to-end analysis of the current repository and delivers a structured report across four sections. ## Phase 1 — Project Overview Launch a single Explore subagent (or a general-purpose subagent if the Explore type is unavailable) to sweep the repository. Instruct it to read the README, entry points, main modules, and core types, then report back on: - What problem the project solves (2–3 sentences, plain language) - Who uses it and how (consumers, dependents, runtime context) - What the main packages / modules are and how they relate - The primary data flow from entry point to output, step by step, with actual function and type names - Core abstractions explained with simple analogies (not "this is a registry" but "this is like a phonebook that...") ## Phase 2 — Most Important Files Based on the Phase 1 sweep, identify the 8–10 most important files. For each file: - What it does (plain language — explain the logic, not just the name) - Why it matters (what breaks or becomes impossible without it) Then close with a short narrative — a compact story about how these files play together. ## Phase 3 — Maturity Assessment Launch all six subagents **in parallel** (single message, multiple Agent tool calls). Each subagent adopts a specific expert persona, reads the relevant source files, searches the web for reference projects using the same stack or idea, and returns a structured assessment. ### Subagent 1 — Documentation **Pers