happier-plan

# Happier Plan Create a repository plan only on an explicit current-user request. Planning is a human-controlled product/design decision, not an agent-selected prerequisite. Do not invoke this skill to implement an existing plan, update ordinary execution status, review completed work, or create an internal ephemeral checklist. ## 1. Establish authorization and mode Classify the explicit request as one of: - `CREATE`: author a new repository plan; - `REFINE`: materially change a draft or approved plan as the user requested; - `REPLACE`: supersede an existing plan with a user-requested successor; - `AMEND`: record a user-approved change to an approved execution contract. If the user did not explicitly request one of these, do not create or materially edit a plan file. A reviewer or implementation agent may recommend a plan/amendment, but only the user can authorize creating it or changing its approved contract. A successor references its predecessor and explicitly preserves, changes, or retires still-applicable material decisions; do not mechanically transcribe historical tasks, findings, or markers. Plan authoring does not authorize implementation. If the user asked only for a plan, stop after presenting the draft. If the user requested both planning and implementation, present the plan for approval before treating it as the execution contract unless the user explicitly waived that checkpoint. ## 2. Recover the real intent before designing State the outcome beneath th...