← ClaudeAtlas

charterlisted

Work out whether a body of work is worth doing and what order it happens in, ending with the bet written down and a sequenced set of features under it: why this should exist, what we are actually betting on, and what gets built first. Use it when the question is bigger than one feature and nothing above it is written down — "should we build a plugin system at all?", "we have five things we could do next quarter, which ones and in what order?", "what's our story for the next year on X", "I need to pitch this to the team", or a request for a rollout order where nobody has said why the work matters, which otherwise produces a sequence with no bet behind it. Do NOT use it for one feature whose requirements need working out; that is `/scope`. `/vision`, `/strategy`, and `/roadmap` each run alone when you want only the thesis, only the bet, or only the sequence — but reaching for one of them because a conversation "sounds strategic" usually lands you here instead.
tsukumogami/shirabe · ★ 0 · AI & Automation · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh charter 2>&1 || true` # 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 durable terminal artifact. A full run also produces a ROADMAP, which `/roadmap` writes on every chain unless the author declines it (R7). STRATEGY is still the *durable* terminal artifact even though `/roadmap` runs after `/strategy`: the ROADMAP is a working artifact that drives work rather than recording it, while the STRATEGY stays in `docs/strategies/` as the audit trail. Both appear in `exit_artifacts:`. A working artifact is not a self-disposing one. `/roadmap`'s own `## Artifact Lifecycle` section owns the completion condition, and the cascade only retires a ROADMAP through a finished downstream PLAN — a ROADMAP nobody plans against persists until someone removes it. 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 spawne