What problem does it solve? Scoping a release usually means ad-hoc notes, duplicated tracker issues, and a plan that drifts from what actually ships. This Skill runs a structured planning conversation and writes each confirmed component directly into the shared Marshall store, so the plan is live and consistent across machines, people, and agents. ## Core Features & Use Cases - Structured planning conversation: Walks theme, per-category component sweep (driven by the release's project_type), deploy-safety and breaking-change questions, and an out-of-scope sweep — one cluster at a time. - Store-native component filing: Files each confirmed component via component_create with a strict shape (title, branch type, slug, deploy safety, breaking flag, structured notes), one per confirmation, never batched. - Add and amend modes: Append a single component to an existing release with add, or patch an already-filed component's fields via component_update without duplicating it. - Use Case: A team lead says "plan v0.5.0" — the Skill confirms the seeded release, sweeps categories like API changes and migrations, drafts each component for approval, and files them so they appear immediately on the release-detail screen. ## Quick Start Ask the AI to plan release v0.5.0 with a one-line theme and confirm each drafted component as it is filed into the Marshall store.
