happy-marketplace

Run a bounded change → verify → fix cycle until an objective check passes (tests green, lint clean, build/type-check ok) or a hard iteration cap is hit. Use for any task that needs repeated attempts against a verifiable signal instead of a single one-shot edit.

Review code for behavior-preserving simplification — collapse duplication, remove dead code and over-engineering, cut verbose patterns down to idiomatic ones. Use when code is longer or more complex than it needs to be, or the user asks to simplify, shorten, refactor, or clean up.

Implement a planned ticket on its own branch using test-first development, updating docs as part of the change, looping change→verify→fix until the suite is green. Use when a ticket has a plan and is ready to build, or the user says "implement X" / "build the ticket" / "make it pass".

Use to store durable context (decisions, facts, preferences, todos, summaries) and to recall or reply from it across sessions. Load when something worth remembering appears, or when the user asks what you were doing, what was decided, or to continue prior work.

Choose the right model and effort per task phase and apply it when dispatching subagents — strong model + high effort for planning and review, a cheaper model + lower effort for mechanical execution. Use when a task splits into plan / execute / review phases or you're spawning subagents.

Push a reviewed ticket branch and open a pull request with a structured title and body, after review-changes has passed. Use when a ticket is reviewed and ready to ship, or the user says "open a PR" / "create the pull request". Stops at opening the PR — never merges.

Turn a feature request into a concrete plan — scope, approach, affected files, a test plan mapped to acceptance criteria, and out-of-scope — before any code is written. Use when the user describes new work, asks to design or spec something, or says "plan this" / "how would you build X".

Review a ticket's branch diff freshly and independently — spec conformance, tests, correctness, quality, security, docs — producing blocking findings that must be fixed before a PR. Use after implement and before open-pr, or when the user asks to review changes / check the diff before shipping.

Umbrella skill that drives the full happy delivery pipeline end-to-end for one request or ticket — plan → track → implement → review → open-pr — stopping before merge. Use when the user wants a change shipped with one command, or to resume a ticket's pipeline from where it left off.

Break a plan into small, independently shippable tickets and track their status across the pipeline. Use when a feature is bigger than one change, when the user wants a task breakdown or a status view, or after plan-feature produces a plan that needs splitting.

Use when starting any conversation in a repo with the happy plugin — establishes how to find happy skills, when to route model/effort, when to loop, and how to keep and reply from memory.