Loading...
Loading...
Found 90 Skills
Use when ready to implement designed features - breaks design into TDD tasks (Red-Green-Refactor), tracks progress with checkboxes in tasks.md, enforces strict testing discipline. Activates when user says "implement this", "let's code", "start execution", mentions "tasks", "TDD", or uses /dev-workflow:spec commands (tasks, execute).
Only when explicitly invoked by the user or precisely delegated by the Planner, implement a single DevFlow Task that has already passed planning and test review, or a Defect that has been attributed as an implementation issue; follow the original repository style, source branch, allowed paths, and change budget, add necessary tests and submit verification evidence, and do not take responsibility for review or merge.
Independently review DevFlow's repository baseline, Spec, test plan, code commits, or release readiness only when the user explicitly invokes it or Planner precisely delegates; output structured conclusions based on file and version evidence, without modifying reviewed artifacts or implementing functionality.
Design and execute tests for an approved DevFlow Spec only when explicitly invoked by the user or precisely delegated by the Planner; maintain an acceptance traceability matrix; complete feature, contract, integration, E2E, regression, and real-scenario verification; output a test report and defect evidence bound to the Commit SHA; do not modify production code.
Show status of all features in .dev/. Scans feature folders using parallel agents, generates a status report, and offers to archive completed features.
Acts as the sole DevFlow Planner only when explicitly invoked by the user or precisely routed after entry preparation is complete; responsible for requirements, repository takeover, Spec, Task DAG, global state, coordination, and merging; does not write production code, and is not used for explanation, general advice, or mere documentation editing.
Actively use when the user requests software development, bug fixing, project continuation, refactoring, migration, or infrastructure changes; first confirm the host, installation scope, and same-source integrity, supplement the DevFlow Skill and the current platform's native roles as needed, and then continuously route four-role delivery. Explanations, general advice, standalone review or testing, documentation-only changes, and minimal risk-free edits do not start the full process.
Critical Standard Bottom-Up Self-Check (check-standards, Convergence Gate) after Java backend code generation/modification. **This skill must be loaded after any Java code is written or modified—including scattered coding that does not follow the complete development process (e.g., "write an XX interface"/"write a Controller"/"help me write this code"): this skill must be loaded and verified before delivering code products to users**. It uses grep/ast-grep to actually scan and verify each standard—comments (class/field/method Javadoc/step comments, including private and extracted methods), logs (full class @Slf4j, each business method has logs, ERROR exceptions with stack traces), transaction rollbackFor, constructor injection, layered boundaries, SQL in XML, unified return body, pagination limit, password encryption, SQL comments/injection/WHERE, and all other verification items, with "File:Line Number" evidence attached to each item; **No level distinction—any item that is not implemented properly (regardless of importance) will be listed in the pending confirmation list to confirm with the user whether to complete it**. **Correct intermediate product naming and paths before verification** (Technical Solution 3.x.1 / Interface List 3.x.2 / Standard Verification Report 5.2.x / Acceptance Report 5.3.x, remove the task ID prefix T0xx from file names and move to the module version directory). Trigger scenarios: after writing code, after code generation, after modifying code, **before delivering code**, pre-submission check, code standard verification/review, comment and log verification, code review, standard self-check, bottom-up check, acceptance review, product file naming correction, file renaming and relocation, **perform standard scanning on specified directories/modules/packages (e.g., "run check-standards on xx directory"/"verify order module standards"/"only scan the code modified this time")**. It can be used with ai-dev-workflow 5.2 standard verification node / 5.3 acceptance, or triggered independently (output the report in the dialogue and prompt the user for confirmation when there are no docs/no process).
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.
Start working on a Marshroom cart issue — creates branch, injects context, updates status to running
Route a task to the right skill in prathamdby/skills and run multi-step workflow chains. Verifies the leaf skill is installed before invoking it.
Universal task dispatcher. Start, route, and execute any task through the development workflow (Steps 0-9). Invoke on every task — /task <description>, /task