ado-backlog

Turn findings from any input (spreadsheet, doc, pasted text) into GitHub Issues: extract, triage, classify by labels and milestone, visual dry-run, create with an approval gate, and write issue links back to the source.

Marketplace

The daily-work arc in one plugin, entered via /daily (hybrid router: bare = 5-station menu — start/work/file/report/wrap — argument jumps straight there; see PLAYBOOK.md at the marketplace repo root). Design & planning: grill-then-plan (verifies the cause via debug-mantra first when planning a fix). Debug chain (both ways): debug-mantra -> (grill-then-plan when the fix involves a design choice) -> post-mortem -> management-talk. Review & verification: scrutinize, dual-verifier. System study: study-design-verify, fit-gap-analysis, naming-audit, drive-to-legacy, crm-archaeology (Dynamics 365/Dataverse org study), ticket-trace. Communication: management-talk, invoice-generator (Tribletext daily summary from git commits), problem-description (interactive HTML walkthroughs). Documents: sa-doc (full SA&D document — use cases, diagrams, data dictionary, architecture — generated from one validated model; Markdown canonical, PDF optional). Reflection: reflect (session retrospective that routes each lesson into an owned skill, a CLAUDE.md, a cross-project GOTCHAS.md, or memory — closing the daily arc with a learn beat).

Frontend structure conventions for React/TSX work. Ships react-structure: per-component file separation (UI .tsx / hook .ts / type.ts / optional Redux slice), a TypeScript + Redux Toolkit + MUI + DataGridPremium stack, and a planning flowchart before code. Opt-in — install only when working on a React project so it does not trigger during backend/CRM work.