Loading...
Loading...
Found 3 Skills
Use when you need to produce a test-case suite for a feature, change, PR, or fixed bug — manual or automated — for delivery to Excel/xlsx, Markdown, CSV, or a tracker. Triggers on "write test cases", "create a test plan", "QA cases", "turn this spec/diff/bug into tests", or after a feature is built / a bug is fixed and before filing or sign-off. Every case is grounded in real evidence (docs, code, git, or the LIVE system); the skill refuses to invent values. Do NOT use to verify one already-finished task (that is dual-verifier), or to file findings as work items (that is the backlog plugins — this hands off to them).
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.
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.