Well

Connect and verify the Well MCP — authenticate, confirm the tools work, and show what to ask. Use when the user runs /well:connect, just installed the Well plugin, or says the Well connection/MCP "isn't working" / "nothing happened".

Produce an accounts-receivable aging report and surface overdue invoices for a Well workspace. Use when the user asks who owes them money, an AR aging report, overdue invoices, days sales outstanding (DSO), or which customers to chase.

Forecast cash flow and runway for a Well workspace from booked invoices and collected bank transactions. Use when the user asks for a cash-flow forecast, runway, how long until they run out of cash, projected balance, or expected inflows/outflows.

Run a month-end (or period) close checklist against a Well workspace — verify everything is reconciled and posted before the books are closed. Use when the user asks to close the month/period, run a close checklist, check if the books are ready to close, or what's left before closing.

Produce a VAT / sales-tax summary for a period from a Well workspace's posted ledger. Use when the user asks for a VAT return, VAT summary, sales tax owed, output vs input VAT, or tax declaration figures for a period.

Build a balance sheet (bilan) from a Well workspace. Use when the user asks for a balance sheet, bilan, assets/liabilities/equity, or financial position at a point in time.

Build a profit & loss statement (compte de résultat / income statement) from a Well workspace. Use when the user asks for a P&L, income statement, compte de résultat, revenue vs expenses, or net result over a period.

How to query a Well workspace correctly — discover the schema first, then query the right root. Use whenever the user asks about their invoices, companies, contacts, bank transactions, accounts, or accounting ledger in Well, or before writing any well_query_records call.

Match bank transactions to invoices and surface unpaid / unmatched items in a Well workspace. Use when the user asks what's paid vs unpaid, to reconcile the bank, to find missing payments, or to match transactions to invoices.

Iterate until success or limit, composing existing skills with Jidoka integration

Generate and maintain BPMN 2.0 diagrams linked to Gherkin scenarios

Review code changes against hard rules and conventions

Research best-in-class products using Browser MCP and WebSearch

Audit Value Delivery compliance after PR push

Systematic debugging with MCP integration, auto-invoke from qa-commit, Phase 7 Harden

Capture patine (decision wisdom) at Gates when KO or challenge occurs

Map slice dependencies using DSM matrix and prioritize by risk

Refresh UI/UX context from design system, Storybook, and codebase

Align phases with GTM strategy, persona tiers, and KPI targets

Expedited workflow for urgent production issues

Guide for creating new MCP server integrations

Standardize Notion task updates across all modes

Group slices into risk-optimized phases with timeline generation

Automated code review using ReadLints and Shell for technical validation

Track commit accumulation and trigger PR when thresholds crossed

Frame problems using JTBD Job Stories, HMW questions, and persona validation

Verify implementation against QA Contract (G#N, AC#N), auto-invoke debug on RED

Generate QA Contract with numbered Gherkin scenarios (G#N) and acceptance criteria (AC#N)

Generate breadcrumb headers/footers with takt time tracking and muda metrics

One-time environment setup for new team members

Template and guide for creating new skills

Generate formatted Slack messages for team communication

Document UI component states (current vs expected) with transitions

Detect domain from context and find appropriate team member

Evaluate technical options with scoring matrix, trigger Gate 4 for significant decisions

Convert passed QA Contract criteria to automated tests

Test web app UI using Browser MCP and Storybook