eve-verification-plans
Eve Verification Plans
Author agentic verification plans — markdown documents that fully specify the steps to verify an Eve-compatible app works correctly AND conforms to Eve platform conventions. Plans are actionable by humans or agents.
When to Use
- Building verification for a new Eve-compatible app
- Auditing an existing app for Eve platform conformance
- After significant feature work that needs structured validation
- Before handoff — proving the app works the Eve way, end to end
- Onboarding a new team to understand what "correctly built on Eve" looks like
Quick Start
# 1. Create the verification directory in your project
mkdir -p e2e-verification/00-smoke
More from incept5/eve-skillpacks
eve-web-ui-testing-agent-browser
Web UI testing and browser automation. Use Vercel agent-browser for general apps, or the repo-pinned Playwright wrapper inside Eve Horizon. Use when tasks require opening pages, interacting with forms, validating UI flows, taking screenshots, extracting page data, or running repeatable browser-based checks locally or in CI.
347eve-auth-and-secrets
Authenticate with Eve, manage project secrets, and add SSO login to Eve-deployed apps.
266eve-orchestration
Orchestrate jobs via depth propagation, parallel decomposition, relations, and control signals
266eve-skill-distillation
Distill repeated work into Eve skillpacks by creating or updating skills with concise instructions and references. Use when a workflow repeats or knowledge should be shared across agents.
265eve-job-lifecycle
Create, manage, and review Eve jobs, phases, and dependencies. Use when running knowledge work in Eve or structuring job hierarchies.
261eve-new-project-setup
Configure a new Eve Horizon project after running eve init (profile, auth, manifest, and repo linkage).
261