wellmate-orchestration

Convert natural-language development requests into bounded engineering execution plans.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-orchestration-sarkarshivaditya-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wellmate-orchestration
Source: https://github.com/sarkarshivaditya-lab/WellMate/tree/main/.engineering-skills/wellmate/orchestration
Command: npx skills add https://github.com/sarkarshivaditya-lab/WellMate --skill wellmate-orchestration-sarkarshivaditya-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about wellmate-orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a vague feature request into an implementation plan?▼

Submit the request in natural language and the orchestration workflow classifies it, identifies affected files and systems, checks architectural constraints, and produces a step-by-step implementation plan before any code changes are made.

How does the orchestration workflow prevent scope creep?▼

It enforces explicit safety gates: never perform unrelated cleanup, never silently expand scope, and make only the smallest necessary change. If scope expands materially during implementation, the workflow stops and reports instead of continuing.

What happens when build validation fails after a change?▼

The workflow identifies the failure, determines whether the change caused it, fixes the root cause when in scope, and re-runs validation. Failing validation steps are never hidden from the user.

Can the workflow modify locked systems or core architecture?▼

No. Locked systems require explicit permission before modification, and existing architecture is never replaced for convenience. Local-first data ownership and offline behavior must remain intact after every change.

When should I not use a structured orchestration workflow?▼

For trivial one-line edits or exploratory prototyping where planning overhead exceeds the value of the change, a direct edit may be faster. The workflow is designed for changes that touch real systems and require validation.