Automação

Verificação proativa do ambiente — destacar qualquer coisa que mereça atenção

Coordinate test writing and execution across the project. Launches the Test Coordinator to orchestrate language-specific test writers and verification agents.

Execute implementation work - plans, sprints, tasks, or ad-hoc work.

Integrate with Notion — database queries, page creation, property updates, and content sync.

Comprehensive test suite review across five phases. Surveys unit coverage, integration coverage, E2E (browser) coverage for webapps, fuzz coverage, and test quality — in that order. Advisory only — produces findings and proposes tickets; does not implement test changes.

Update subtask with fixes or new steps. Two trigger modes: (A) Auto-called by autoworker:gate-check on FAIL — reads FAIL info, adds supplementary steps. (B) User calls with a finding/bug during testing — diagnoses, fixes, updates subtask. Both modes end by invoking autoworker:dispatch to re-enter the loop.

Auto-generate documentation from code — docstrings, API references, README files, and changelog entries.

Create technical documentation — API docs, user guides, runbooks, architecture decision records, and onboarding guides.

Initialize, manage, and search the per-project .briefing/ vault. Obsidian-compatible persistent knowledge base.

Scaffold production-ready REST APIs with authentication, rate limiting, validation, and OpenAPI docs.

Good-faith adversarial scrutiny of an idea or plan. Spawns critical skeptics across relevant lenses, pairs them with an advocate defending the idea, and synthesizes the exchange into a report. Produces feedback only — no code, no tickets, no artifacts.

Design Zapier automations — triggers, actions, filters, formatters, and multi-step Zap architectures.