mapping-suite
Mapping Suite
Overview
You have a small library of skills that map, audit, and document a system from different angles — architectural-analysis, release-analysis, wiring-audit, doc-claim-validator, doc-completeness-audit, etc. They share conventions (docs/<skill>/<date>/, mermaid + cited reports, cross-skill callout reuse, --style corporate HTML output) and they share a common prior: a recent architectural-analysis run is the foundational artifact most of the others can build on.
Coordinating them by hand means resolving the same scope four times, threading the same prior through four different Phase 0 lookups, and ending up with four standalone HTMLs to share. This skill owns the coordination so you don't.
The skill is a coach, not an autorunner. At each step it presents:
- The next sibling skill in the recipe.
- The scope it should inherit (resolved once at suite start).
- The recommended invocation.
- An approval gate.
You invoke the sibling. The orchestrator records what landed and proposes the next step.