What problem does it solve? Vague development requests often lead to uncontrolled refactoring, scope creep, and broken builds. This Skill turns a natural-language WellMate development request into a controlled, step-by-step engineering execution plan with explicit safety gates. ## Core Features & Use Cases - Request Classification: Categorizes incoming requests as investigation, bug fix, feature, UX change, architecture change, refactor, documentation, or tooling before any code is touched. - Safety Gates: Enforces pre-implementation rules such as never modifying locked systems, never introducing network-first behavior, and never silently expanding scope. - Validation & Failure Handling: Requires TypeScript/build checks, clean imports, intact offline behavior, and a defined recovery procedure when validation fails. - Use Case: A user asks to "fix the sync issue in WellMate." The Skill classifies it as a bug fix, checks CLAUDE.md for locked-system constraints, maps affected files, produces a minimal-change plan, validates the build, and creates a focused commit. ## Quick Start Ask the assistant to plan and implement a small WellMate bug fix using the orchestration workflow, starting from your natural-language description of the problem.