What problem does it solve? Engineering teams on the PalFish GMV project lose time and cause incidents when handoff documents contain guessed table names, solutions skip root-cause evaluation, or schema changes silently break the shared Supabase database used by the pf-revenue repo. This Skill encodes the full change-control doctrine so every spec, handoff, commit, and schema change follows verified team rules. ## Core Features & Use Cases - Handoff document authoring: Enforces the canonical handoff structure (Origin, chốt decision, verified context, scope, acceptance criteria, test plan, anti-patterns) with a hard rule to grep-verify every table, column, and line number before writing. - Solution evaluation: Applies the three mandatory criteria (triệt để, không lỗi con, no infra/performance regression) to any proposed change before acceptance. - Spec workflow & task naming: Guides prototype-to-spec conversion using docs/SPEC_TEMPLATE.md and maintains TOP1/TOP2/TOP3/VAC-XX task-wave naming conventions. - Cross-repo safety: Requires impact checks on the shared bank_transactions table before any schema change that could affect pf-revenue's Lark sync. - Use Case: Before writing a handoff for a new bill softlock feature, run the grep verification commands to confirm actual column names in backend code, then produce a handoff with a verified context section and the mandatory tsc/test acceptance gate. ## Quick Start Ask the assistant to draft a handoff document for a new PalFish GMV task following the change-control rules, verifying all table and column names with grep first.
