DMTools agents

Writes acceptance criteria for a story from its description, design context, and answered question sub-tickets.

Writes acceptance criteria for a story from its description, design context, and answered question sub-tickets.

Gate check: verifies that all BA sub-tasks of a story are done before the story moves forward.

Writes a full story description from the ticket context and its answered question sub-tickets.

Implements a story end to end: checks out the repository, writes the code and tests, and opens a pull request linked to the story.

Story development variant that resolves the target repository dynamically from the ticket instead of using a fixed project repository.

Test variant of storydevelopmentdynamicrepo used to exercise the dynamic-repo flow safely.

Routes a story to the repository-specific development agent based on the ticket context.

Test variant of storydevelopmentredirect used to exercise the redirect flow safely.

Verifies that a story can move to Done: checks that tests passed and PRs merged, then transitions the ticket or reports what is missing.

Collects open business questions for a story and creates them as question sub-tickets assigned for review.

Designs the technical solution for a story: reads the story context, the answered questions, and the BA/SA/VD parent context, then produces the solution write-up and architecture diagrams.

End-to-end variant of storysolution that also labels the ticket according to the solution outcome.

Multi-task variant of storysolutione2e that splits a large solution into several implementation tasks.

Writes automated tests for a story: generates test code from the acceptance criteria, runs it, and opens a PR with the new tests.

Merges an approved story-test-automation PR and updates the story ticket with the result.

Reworks a story-test-automation PR after review: fixes the test code per review comments and pushes the updates.

Turns a ready QA finding into a well-formed bug ticket: drafts summary, description, severity and steps to reproduce, creates the bug and links it to the source ticket.

Implements a bug fix end to end: checks out the repository, analyzes the root cause, writes the fix with tests, and opens a pull request.

Verifies that a bug can move to Done: checks that linked tests passed and the fix PR merged, then transitions the ticket or reports what is missing.

Collects several related bugs into one batch epic so they can be fixed together in a single development pass.

Fixes a whole batch of related bugs in one branch: reads the batch epic context, implements all fixes with tests, and opens a single pull request.

Finalizes a merged batch-fix PR: updates the batch epic, links results back to each bug, and moves the batch tickets forward.

Notifies the team when a bug fix PR is merged and moves the bug ticket to its post-merge status.

Writes automated tests for a bug: generates test code from the bug context, runs it locally, and opens a PR with the new tests.

Merges an approved bug-test-automation PR and updates the bug ticket with the result.

Reworks a bug-test-automation PR after review: reads the review comments, fixes the test code, and pushes the updates.

Generates manual test cases for a bug (TestCasesGenerator job) and moves the ticket through the testing statuses.

Gate check: decides whether a bug has everything needed (reproduction details, environment, approval) to be taken into development.

Reviews a bug-test-automation pull request: checks test quality and coverage, then posts review comments on the PR.

Distills the outcome of a merged PR into the self-curated review-knowledge base and pushes the update.

Reviews a pull request like a senior reviewer: analyzes the diff, checks conventions and risks, and posts inline review comments plus a verdict.

Routes a review request to the correct PR review configuration for the repository.

Reworks a pull request after review: reads review comments, implements the requested fixes, and pushes updates to the PR branch.

Routes a rework request to the correct PR rework configuration for the repository.

Reviews a story-test-automation pull request: checks test quality against the story acceptance criteria and posts review comments.

Reviews a test-automation pull request and posts structured review comments on it.

Reworks a test-automation PR after review: applies review feedback to the test code and pushes the fixes.

Automates a single manual test case: converts it into executable test code and opens a PR with the result.

Generates manual test cases for stories (TestCasesGenerator job) and moves the tickets through the testing statuses.

Recovery job: cleans up a test case left in a dirty in-review state (unfinished review bookkeeping) and restores a consistent status.

Recovery job: repairs the status of bugs whose test-case workflow failed mid-transition.

Recovery job: repairs tickets whose pull request merged but the ticket status was never updated.

Recovery job: unsticks a test case left in an intermediate status after a failed or interrupted run.

Retries a pull request merge that previously failed (for example due to temporary CI flakiness) and reports the outcome.

Test variant of retrymerge used to exercise the retry-merge flow safely.

Aggregates AI token usage written by agent runs and posts a summary report comment.

Creates many bug tickets at once from a single test failure analysis: drafts each bug and creates them in bulk with links back to the source.

Creates repository housekeeping tasks (setup, CI, docs) as tracker tickets for a new or onboarding repository.

Same as createRepoTasks but fans out across multiple repositories in one run.

Coordinates dark-factory manager routines (scheduling and housekeeping) as a pure JSRunner job without an AI CLI step.

Runs continuous product discovery for a ticket and publishes the result as a Confluence page tree; on later runs it iterates on the existing pages and answers reviewer inline comments.

Product intake: analyzes a raw request against existing epics and stories, then creates the missing epics/stories and posts an analysis comment.

Answers a Product Owner refinement question using the parent ticket context ([BA]/[SA]/[VD] sibling tickets), writes the answer to the Answer field, and closes the question.

Routes a proof-of-concept development request to the appropriate development agent configuration.

Restores a ticket description from its history when the description was accidentally overwritten or cleared.

Enhances the solution design description of a ticket with architecture detail and posts an assessment of the result.

Gate check: verifies that all stories of a task are done before the task itself moves to Done.

Finds tickets blocked by dependencies that are already resolved and moves them back to an actionable status.

Reports failed agent workflow runs (with links and error summaries) so failures are visible instead of silent.