my-festival-campaign

What problem does it solve?

This Skill eliminates the high risk and coordination overhead of implementing the "My Festival" personal diary feature in a production Flutter beer festival app by providing a structured, decision-gated campaign runbook that guides developers through local UI work, analytics, and cloud sync backend provisioning while preventing common failure modes like schema drift, route breaking, and big-bang UI rewrites.

Core Features & Use Cases

• Two-track phased execution: Separates UI work (local diary with want-to-try/tasted states, multi-tasting timestamps, notes) from cloud sync backend (D1 provisioning, worker deployment, Flutter sync client) to manage risk and unblock work early.
• Decision gates and verification: Each phase includes exact file targets, baseline commands, verification steps, and expected outcomes, with explicit branching logic for unexpected observations and wrong-path fencing.
• Safety guardrails: Enforces accessibility semantics, golden-file testing, single-PR-per-phase discipline, and change-control routing while explicitly forbidding dangerous operations like schema migrations or route renames.

Quick Start

Use the my-festival-campaign skill to implement the My Festival feature by following its phased runbook, starting with Phase 0 baseline verification and then executing Track A UI phases before provisioning the cloud sync backend.