plan-big-featurelisted

# Plan Big Feature For an initiative too big and too tangled for a single `/plan` (which is scoped to one feature, one PR). This skill produces the *decomposition* — the set of decoupled epics and their draft tickets — not an implementation plan for any one of them. Once a resulting sub-ticket is picked up for real work, it goes through `/plan` on its own. The whole point of this skill is the hard gate at the end: a big initiative must not start getting built piecemeal just because someone had a good idea about part of it. Everything gets decomposed, proposed, and explicitly walked through with the user first. ## When to use this The user describes something that is really several independent efforts wearing one name — a "mega issue," a platform migration, a feature with 4+ genuinely separable workstreams, a restructure of existing tracked work. If it fits in one PR or one epic without contortion, this skill is overkill — use `/plan` instead. ## Process ### Step 1: Research, in parallel Fan out parallel subagents (never sequential — this is exactly the kind of work that benefits from it) across the distinct areas the initiative touches. Each research subagent should: - Read the actual code/config/docs, not assume from memory — an initiative like this usually spans work done over many sessions, and stale assumptions (a file that got deleted, a store that got migrated, a feature that already shipped) are the single biggest way this kind of plan goes wrong. - Come back wi