wellmate-workflow

Executes WellMate code changes through a structured inspect-plan-implement-verify-review workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Unstructured code changes often skip inspection, break stable systems, or ship without validation. This Skill enforces a disciplined, repeatable workflow for making changes to the WellMate codebase so every modification is inspected, planned, verified, reviewed, and committed cleanly. ## Core Features & Use Cases - Structured Change Pipeline: Guides changes through eight phases: intake, inspection, planning, implementation, verification, diff review, recording, and commit. - Natural Language to Command Translation: Converts user requests into explicit, minimal, reversible, and ordered command chains with defined scope and constraints. - Architecture Protection: Prevents rewrites of stable systems, speculative abstractions, unauthorized dependency additions, and changes to persistence or backend authority. - Use Case: A user asks to fix a sync bug in WellMate. The Skill inspects the implementation, callers, and state ownership first, plans the smallest viable change, implements it, runs targeted validation, reviews the diff for accidental changes, and commits one logical change. ## Quick Start Use the wellmate-workflow skill to implement this change request following the full inspect-plan-verify-commit process.

Frequently Asked Questions about wellmate-workflow

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

FAQPage Schema
How do I make a code change in WellMate safely?▼

Follow the eight-phase workflow: convert the request into intent and constraints, inspect the implementation and its callers, plan the smallest viable change, implement following existing architecture, run targeted validation, review the diff, and commit one logical change.

How to convert a natural language request into engineering commands?▼

Translate the request through intent, scope, constraints, research, inspection, and an execution plan. Produce explicit, minimal, reversible, ordered commands, and end every chain with concrete validation and a report of changed files and risks.

What changes does the WellMate workflow prohibit?▼

It prohibits rewriting stable systems, adding speculative abstractions, renaming unrelated files, changing persistence ownership or backend authority, and adding dependencies without justification. Ambiguous requests are never converted into destructive commands without confirmation.

What validation should run after implementing a change?▼

Run the narrowest relevant checks first, then TypeScript build, lint, tests, production build, and platform-specific validation where applicable. Every implementation chain must end with concrete verification before commit.

When should I not use this structured workflow?▼

The workflow is designed for changes to the WellMate codebase with its specific constraints and memory system. For unrelated projects or trivial one-line edits, the full eight-phase process may add unnecessary overhead.