Stats
Actions
Available In
Tags
Plugin
Dev Workflows
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. Debug chain: debug-mantra -> (grill-then-plan when the fix involves a design choice) -> post-mortem -> generating-test-cases (regression case) -> management-talk. Review & verification: scrutinize, review-pr (GitHub PR review — safe workspace, scrutinize as the judge, then send-back / fix-it / chat-only), dual-verifier. Testing & QA: generating-test-cases (evidence-grounded test-case suites for a feature/change/fixed bug, rendered to Excel/Markdown/CSV or delegated to a tracker). Documents: sa-doc (full SA&D document — use cases, diagrams, data dictionary, architecture — generated from one validated model; Markdown canonical, PDF optional). 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). 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).
What's Inside
Slash Commands2
Daily
/daily
The one daily-work command — routes you to the right skill for your moment in the day. Bare = 5-station menu (start / work / file / report / wrap); with a station word it jumps straight there. The entry point into the whole daily arc mapped in PLAYBOOK.md.
Sa Doc
/sa-doc
Generate a complete SA&D document (use cases, diagrams, data dictionary, architecture) from one validated model — Markdown canonical, PDF optional. Academic or professional profile.
Skills19
crm-archaeology
/crm-archaeology
Study a live Dynamics 365 / Dataverse environment end-to-end and produce one ARCHITECTURE.md — pull every customization to disk (solutions, entities, forms, JS and React web resources, PCF controls, classic workflows, plugins, cloud flows, classic RibbonDiffXml AND modern commands, security roles, embedded Power BI), map every business entity (standard AND custom), then trace the business processes layer by layer. Use whenever the user wants to learn, study, understand, reverse-engineer, audit, or document an existing Dynamics 365 / CRM / Dataverse org or model-driven app — "how does this CRM work", "document my D365 org", "learn the business logic of this environment", "what does this solution actually do", onboarding to a customer's CRM, or scoping a migration/rebuild. Read-only by design — it never writes to the org. NOT for building or changing CRM components (use the dataverse plugin skills) or for studying a plain source-code repo (use drive-to-legacy).
daily
/daily
The single entry point into the daily-work arc — a hybrid menu/argument router. Trigger whenever the user invokes /dev-workflows:daily, types /daily, asks "what should I do now", "where was I", "start my day", "what's next today", "wrap up my day", "end my day", or seems unsure which skill fits their current daily-work moment. Bare invocation shows a 5-station menu (starting / working / filing findings / reporting / wrapping up); with an argument (start | work | file | report | wrap, synonyms accepted) it jumps straight to the station and hands off to the right skill: ado-backlog:my-work, the situational toolbox (grill-then-plan, debug-mantra, study-design-verify, naming-audit, fit-gap-analysis, problem-description, ticket-trace, scrutinize, review-pr, dual-verifier, drive-to-legacy, crm-archaeology, generating-test-cases), findings-to-ado-backlog or ado-create-work-items (github-backlog twins on request), management-talk, or invoice-generator.
debug-mantra
/debug-mantra
Four-mantra debugging discipline — reproduce, trace the fail path, falsify the hypothesis, cross-reference every breadcrumb. Recite the mantra block verbatim at the start of any debugging session, then apply the four steps in order before proposing any fix. Trigger on /debug-mantra and proactively whenever debugging starts — user reports a bug, says something is broken/throwing/failing, asks to debug/diagnose/investigate an issue, or pastes a stack trace or error log.
drive-to-legacy
/drive-to-legacy
Use when exploring, studying, or porting an unfamiliar legacy codebase. Triggers when the user says "explore this project", "understand this code", "I need to port this", "how does this app work", "document this codebase", "study this code", or any request to deeply understand an existing project they did not write. Also triggers when onboarding to a new repo or preparing migration/rewrite plans.
dual-verifier
/dual-verifier
Use when an implementation task has just been completed and the user wants independent verification that the work is actually correct. Dispatches two subagents that perform the SAME verification checks independently, then merges their findings into one deduplicated report with severity and confidence. Triggers when the user says "verify this", "double-check the implementation", "cross-check what was done", "did this actually work", "verify the task", or invokes a slash command for verification. Especially valuable right before commits, PRs, or hand-offs, where over-claiming is most costly.
Stats
Version0.25.2
LanguagePython
Stars0
MaintenanceExcellent
LicenseMIT
Last Commit
Added
Available In
Safety Signals
Caution
Executes bash commands
Tags
Categories
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
