e2e-architect

Plan, audit, and debug end-to-end test coverage for software projects.

1|2|Updated Apr 6, 2026
One-click install
npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-architect
Source: https://github.com/parisgroup-ai/imersao-ia-setup/tree/main/skills/e2e-architect
Command: npx skills add https://github.com/parisgroup-ai/imersao-ia-setup --skill e2e-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning, auditing, and debugging end-to-end test coverage across projects to improve reliability and traceability.

Core Features & Use Cases

  • Provides memory persistence for cross-session decisions and knowledge retention.
  • Generates structured test plans, audits, and debugging guides for e2e flows.
  • Integrates with commands /e2e-architect plan, audit, debug, and fixtures to streamline QA workflows.

Quick Start

Run /e2e-architect plan <feature> to begin designing end-to-end tests.

Frequently Asked Questions about e2e-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan end-to-end test coverage for a new software feature?

To plan end-to-end test coverage, you outline structured test plans and fixtures for software features. This process generates a testing guide that maps e2e flows and defines memory tracking requirements for the project's auto-memory directory.

What is e2e test auditing and how does it improve software reliability?

E2e test auditing reviews existing test suites and fixtures to improve reliability and traceability. It evaluates current testing flows, identifies coverage gaps in the end-to-end design, and produces an audit report for software projects.

How do I debug failing end-to-end tests in my project?

To debug failing end-to-end tests, you analyze test execution flows and generate a debugging guide. This isolates failures within e2e test suites and fixtures, leveraging memory persistence to retain cross-session debugging decisions.

Can I retain QA decisions and test knowledge across different sessions?

Yes, you can retain QA decisions across sessions by utilizing memory persistence. The system reads and writes to the project's auto-memory directory, ensuring test plans, audits, and debugging knowledge are retained between different workflows.

Do I need any specific testing frameworks to audit my e2e test suites?

No specific testing frameworks are required as dependencies to audit your e2e test suites. The auditing process applies across design and debugging phases to analyze existing test flows and fixtures without external framework integrations.