dmtools-agents

Setup, configuration, and customization of dmtools GraalJS agents (smAgent, configLoader, unit tests). Use this when asked to configure agents for a project, add a new project config, write agent rules, customize branch/commit/PR formats, set up per-project SM schedules, or run/write agent unit tests.

Guidance for keeping dmtools-agents prompt/config architecture generic and project-safe. Use when refactoring agent prompts, composing cliPrompt/cliPrompts, moving project rules into target repos, adding .dmtools config fields, or changing GraalJS agent code.

Dark Factory manager runbook for monitoring Jira labels, GitHub Actions, open PRs, review/rework/merge loops, and recovering stuck automation. Use when tickets or PRs appear stuck, SM labels remain without active runs, CI fails after merge, or review/rework chains do not auto-start.

Documentation for the SCM (Source Control Management) abstraction layer in dmtools-agents. Use when configuring GitHub vs Azure DevOps (ADO) as the SCM provider for agents, creating or modifying scm.js providers, setting global or per-agent SCM config, or understanding the provider interface (listPrs, addComment, resolveThread, mergePr, etc.).

Runbook for setting up a Dark Factory: an automated development repository where tracker intake (Jira is the common example), dmtools agents, GitHub workflows, branch protections, required quality gates, labels, and merge automation work together to deliver changes through PRs. Use when bootstrapping a new repo for autonomous development agents or troubleshooting why SM/intake/development agents did not start.