doc-engine
Doc Engine
Purpose
Create and improve technical documentation, README files, AGENTS.md files, architecture notes, diagrams, and usage docs that help people act correctly.
Use When
- Writing or improving a README.
- Writing or refining AGENTS.md guidance.
- Documenting architecture or developer workflows.
- Creating usage docs or technical notes.
- Explaining how a system should be used or maintained.
Avoid When
- The user wants implementation only.
- Documentation would duplicate obvious code.
More from moeller-projects/agent-skillz
ado-gateway
Use when fetching Azure DevOps work items or pull request comments, parsing Azure DevOps pull request URLs, or normalizing read-only Azure DevOps data for downstream skills. Do not use when editing Azure DevOps state, reviewing GitHub pull requests, or authoring OpenSpec files.
4caveman
Trigger when user wants terse, low-token, high-signal technical replies for coding work. Avoid for documentation, onboarding, polished copy, or high-risk instructions requiring explicit detail.
3ops-engine
Use when designing CI/CD, reviewing infrastructure, working with containers or Kubernetes, or analyzing deployment and security risk. Avoid for pure application refactoring or documentation.
3repo-engine
Use when onboarding into a repository, mapping architecture, finding entry points, or extracting conventions and hotspots. Avoid when exact files are provided and only a small patch is needed.
3test-engine
Use when writing tests, improving coverage, designing E2E flows, or reducing flaky behavior in automation. Avoid when the task is pure refactoring with no testing component.
3thinking-engine
Use when a problem is vague, a plan needs critique, or options must be compared before execution. Avoid when implementation is already decided or direct execution is requested.
3