What problem does it solve? Planning a GitHub issue before building it often produces vague plans that hand unresolved design decisions to the builder, or plans grounded in assumptions rather than the actual repository state. This Skill produces a complete, buildable implementation plan for one MellowMaker issue and posts it as an issue comment so a fresh build context can execute it without inheriting this conversation. ## Core Features & Use Cases - Repository-grounded planning: Loads the issue body, comments, labels, vision docs, configs, and source from the canonical ciaran-slow/MellowMaker repository before prescribing anything, and refuses to invent files, commands, or conventions that do not exist. - Decision resolution: Resolves data shapes, migrations, error states, and platform differences up front, with dedicated methods for un-reproducible device bugs (arithmetic over committed constants), schema changes (executed SQLite probes), and event-ordering mechanisms (emitter-source citation). - Falsifiable verification specs: Requires every planned contract to name a test that would fail under a plausible bug, including negative-branch fixtures traced to the exact code branch they exercise. - Use Case: A maintainer says "plan issue 43" and receives a posted issue comment containing the outcome, ordered implementation steps with exact paths, persistence and offline behavior, accessibility requirements, concrete test cases, and recorded decisions, ready for a separate build stage. ## Quick Start Use the plan skill to write the implementation plan for MellowMaker issue 43 and post it on the issue.