charterlisted

# Charter `/charter` is the first parent skill in the shirabe parent-skill pattern. It walks an author through the strategic chain (VISION → STRATEGY → ROADMAP), holding state across child boundaries, enforcing pattern-level invariants (state schema, resume ladder, exit paths, child inspection), and producing a STRATEGY as the terminal artifact. The pattern-level contract surface is documented in `${CLAUDE_PLUGIN_ROOT}/references/parent-skill-pattern.md` and its three companion references. `/charter` is the first concrete consumer; the seven SKILL.md structural elements below align section-by-section with the pattern's required structural elements. ## Team Shape `/charter` runs as a single-agent skill in the v1 core layer — no team is spawned. The parent-of-the-parent (the agent invoking the skill) calls `/charter` directly; there are no peer roles to materialize at team-creation time. The team-shape declarator is prose per Decision 8's v1 form (see `${CLAUDE_PLUGIN_ROOT}/references/parent-skill-pattern.md` — Team- Shape Declarator section). When the amplifier-layer substrate ships, team-emitting parents declare their roster as structured metadata; single-agent parents like `/charter` keep the prose form. See [`${CLAUDE_PLUGIN_ROOT}/references/parent-skill-pattern.md`](${CLAUDE_PLUGIN_ROOT}/references/parent-skill-pattern.md) Dispatch Contract section for the mechanism that carries each child invocation. ## Input Modes From `$ARGUMENTS`: 1. **Empty** — surface a cold