Add unit and end-to-end browser tests to a completed development phase using its acceptance criteria, planning documents, and implementation. Review the proposed coverage, verify tests fail and then pass, and commit the generated test files.
Generate tests for a completed phase based on UAT criteria and implementation
Review the instructions the agent will receive before you install.
Analyzes implementation files, classifies them into TDD (unit), E2E (browser), or Skip categories, presents a test plan for user approval, then generates tests following RED-GREEN conventions.
Output: Test files committed with message test(phase-{N}): add unit and E2E tests from add-tests command
</objective>
<execution_context> @${CLAUDE_PLUGIN_ROOT}/workflows/add-tests.md </execution_context>
<context> Phase: $ARGUMENTS@.planning/STATE.md @.planning/ROADMAP.md </context>
<process> Execute the add-tests workflow from @${CLAUDE_PLUGIN_ROOT}/workflows/add-tests.md end-to-end. Preserve all workflow gates (classification approval, test plan approval, RED-GREEN verification, gap reporting). </process>No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Handle ActiveCampaign contact and marketing tasks through Rube MCP, a connection for agent tools. Find or create contacts, manage tags and subscriptions, enroll contacts in existing automated workflows, and create follow-up tasks.
Research competitors’ live Meta and Google ads to identify opening hooks, offers, calls to action, and landing pages. Receive a sourced creative brief and up to three test ideas adapted to your product.
Analytics your AI agent can actually use. Track, analyze, run A/B experiments, and optimize across all your projects via CLI. Includes a growth playbook so your agent knows HOW to grow, not just what to track.
The English summary is being prepared. Showing the original description.
Teaches when to recall from long-term memory before acting and when to save durable decisions, corrections and failures afterwards. Use when a memory tool or MCP memory server is connected but the agent is not using it consistently, when the user complains that the assistant forgets preferences, conventions or past decisions between sessions, or when setting up persistent memory for a project. Works with any memory backend: a folder of Markdown files, a local MCP server, or a managed service.
The English summary is being prepared. Showing the original description.
Audit local AI coding-agent sessions with agenttrace for cost, tokens, tool failures, latency, anomalies, health, diffs, and CI gates.
The English summary is being prepared. Showing the original description.
Checks which private files (.env, keys, secrets) Claude Code and its subagents reached in this project, whether a value came into an agent's context, and which key to change, by running the open source agentwhy CLI over the session records Claude Code already keeps on disk. Use when the user asks whether the agent or a subagent read their .env or other secrets, which private files a session touched, whether a key leaked into the conversation, or which key to rotate. Runs locally and never prints a secret value.
The English summary is being prepared. Showing the original description.