plan

Writes implementation plans for MellowMaker GitHub issues and posts them as issue comments.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/ciaran-slow/MellowMaker --skill plan-ciaran-slow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan
Source: https://github.com/ciaran-slow/MellowMaker/tree/main/.claude/skills/plan
Command: npx skills add https://github.com/ciaran-slow/MellowMaker --skill plan-ciaran-slow

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a GitHub issue before building it?

Invoke the plan skill with an issue number, and it reads the issue body, comments, labels, vision docs, and repository configuration from ciaran-slow/MellowMaker, then posts a structured implementation plan as an issue comment covering scope, implementation steps, persistence, tests, and decisions.

How do I diagnose a mobile bug I cannot reproduce locally?

For layout and viewport defects, the plan derives the mechanism by arithmetic over committed constants: fix a frame from an existing test fixture, tabulate every height contributor with its source file, sum against the frame, and compare with a control screen that shares the structure but not the symptom.

How do I plan a SQLite migration safely?

Run an executed probe during planning: migrate a test harness connection to the previous version, populate it with baseline data, run the candidate statements with foreign keys both on and off, and record before and after row counts for every referencing table in the plan.

What happens when an issue has an owner gate blocking the build?

The plan stops and posts a comment on the issue quoting the gate wording, stating no plan was written, and describing what evidence opens the gate. It does not write a partial plan or argue for opening the gate, since that escalation belongs to the owner.

When should planning escalate a decision to the user instead of resolving it?

Escalate only for genuine product or destructive-data choices, or when acceptance criteria conflict with each other, the vision doc, or repository constraints. When criteria merely outrank the issue's own proposed mechanism, the plan picks the mechanism satisfying every criterion and records the divergence.