happier-implement-plan

# Happier Implement Plan Execute an approved plan as its orchestrator and integrator. Read and apply `skills/happier-implement` for the common implementation workflow; this skill adds plan authority, execution-state, amendment, boundary-review, and completeness rules. It does not create, materially refine, approve on the user's behalf, or redesign a plan. ## 1. Resolve authorization and the execution contract - Identify the exact plan path, approved contract revision, intent, exclusions, material requirement/invariant IDs, execution units, acceptance criteria, and designated tracking area. - The current user's explicit direction to implement a named plan is execution authorization and may serve as approval when that same plan was awaiting approval. Record approval only in the plan's designated identity area; do not alter requirements while doing so. - If several plans could match, the named plan is unavailable, or approval would select among materially different contracts, resolve that ambiguity before production edits. - Do not create a replacement plan, add unapproved requirements, or turn ordinary implementation decisions into amendments. Route plan authoring and user-approved amendments to `skills/happier-plan`; route deep review, QA, finding triage, and authorized review-fix loops to `skills/happier-review`. ## 2. Recover current state without reopening design Read the complete approved plan when it is not already active in context. Recover: - approved intent, tar...