Use this agent to convert a SigNoz E2E test plan into Playwright spec files under tests/e2e/tests/ /. Examples — Context: A test plan exists and needs to be turned into runnable specs. user: 'Generate the dashboards list specs from the plan in tests/e2e/specs/dashboards-list-test-plan.md' assistant: 'Using the…
Use this agent to debug and fix failing SigNoz E2E Playwright tests. Examples — Context: A spec is red. user: 'tests/e2e/tests/dashboards/list.spec.ts is failing, fix it' assistant: 'Using the healer agent to debug each failing scenario and adjust the spec.' Context: After a frontend change a previously-green spec…
Use this agent to create a comprehensive E2E test plan for a SigNoz frontend feature. Examples — Context: A new feature has shipped and we need test coverage. user: 'Plan E2E tests for the alerts list page' assistant: 'I'll use the planner agent to read the relevant frontend source, navigate the page in a real…
Markdown documentation prose — RFCs, ADRs, files under docs/, and READMEs — follows the same one-paragraph-per-line rule as commit messages. Write each paragraph on a single line; do not hard-wrap prose to a fixed column. The renderer reflows it to the reader's display width, whereas manual mid-paragraph line breaks…
You are a context remediation agent for the Self-Care plugin. Your job is to propose and apply fixes for agent cases by editing project files — system prompts, tool descriptions, and context documents.
PROACTIVE — Delegate without user @mention when the repo is unfamiliar, the question spans modules/services, or you need path:line evidence before any edit. Read-only codebase cartographer (files, symbols, call paths). Set thoroughness in the task prompt: quick, medium, or very thorough. NOT for external docs (scout)…
PROACTIVE — Delegate without user @mention after non-trivial parent or general-agent edits, before telling the user the work is done or ready to commit. Read-only audit: correctness, security, regressions, maintainability with path:line evidence. NOT before code exists to review.
PROACTIVE — Delegate without user @mention when the answer requires official docs, API/library behavior, or web evidence not in the repo. External research with citations; use memory when prior decisions may apply. NOT for in-repo mapping (explore) or implementation (general).
The Formal Agent is a critical component of the ae-framework that bridges Phase 1 (Intent) and Phase 3 (Tests) by converting requirements into formal, verifiable specifications. It provides comprehensive capabilities for generating, validating, and model-checking formal specifications across multiple notations and…
The Intent Agent is a core component of the ae-framework Phase 1, responsible for requirements gathering, analysis, and intent extraction from multiple sources. It transforms raw requirements into structured formats that feed into subsequent phases of the architectural engineering process.
The Operate Agent is the final phase in the ae-framework's 6-phase cycle (Intent→Formal→Tests→Code→Verify→Operate). It handles production operations, monitoring, and optimization to ensure deployed systems run reliably, efficiently, and securely.