verid
Self-contained verid BA, onboard, design, planning, TDD, debugging and review skills with architect, planner, tester, coder, QA, reviewer and security agents
Plugin verid from marketplace verid in anhtranhai835/aeriq. Commands read from the repo's manifest — 5 days ago.
What it installs
Skills (32)
verid-baUse when a verid project needs requirements research, scope clarification, EARS specification (.verid/spec.md), or modular BA dossiers.
verid-buildUse when an approved verid module is ready for TDD implementation (RAW -> COOKING -> PLATED) and verification with verid taste.
verid-debuggingUse when a test fails unexpectedly, a bug is reported, or an implementation is stuck during a verid cycle.
verid-designUse when a verid project has agreed research and spec and needs architecture decisions, reuse inventory, and .verid/design.md.
verid-onboardUse when onboarding to a verid workspace, checking setup health, or reporting current module status and next step without modifying files.
verid-planUse when a verid design is agreed and needs delivery modules and testable acceptance criteria in .verid/plan.md (classic, modular, or kanban).
verid-reviewUse when all ACs of an ordered verid module pass and need an independent subagent review before verid serve.
verid-routerUse when a verid task touches a specific domain (UI/UX, React, Frontend, Backend, Databases, DevOps, Mobile, Web-Testing, Edge-Cases, Security-Scan, Docs-Seeker) to load only the needed reference file.
baUse when verid requirements or scope need research, clarification or a spec.
backend-developmentUse for API, authentication, service, and backend architecture work.
context-engineeringUse for selective document reading, focused agent handoffs, context loss or token waste in verid workflows.
databasesUse for schema design, queries, indexes, migrations, and data integrity.
debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
designUse when a verid project needs an agreed design before planning modules.
devopsUse for CI, containers, cloud infrastructure, and deployment design.
docs-seekerUse to find current library or framework documentation for an implementation decision.
edge-casesUse when an AC has input, state, permission or timing boundaries.
frontend-developmentUse for React or TypeScript UI implementation and component structure.
mcp-builderUse when building a Model Context Protocol server or tool integration.
mobile-developmentUse for iOS, Android, React Native, or Flutter development.
modulesUse when workflow is modular to prepare module dossiers from repo templates and carry their contracts through verid order, TDD, review and release.
onboardUse when a developer is new to a verid project or asks whether their workspace is set up and where the project stands.
planUse when a verid design is agreed and needs modules with testable acceptance criteria.
predictUse before a major or risky verid design change to examine architecture, security, performance, user experience, and hidden assumptions.
problem-solvingUse when a verid task is stuck because of growing complexity, repeated failed approaches, hidden assumptions, or uncertain scale.
react-best-practicesUse for React and Next.js performance reviews and implementation.
reviewUse when a verid module is ready for review, a signed auto plan needs review, or the product is ready for handoff.
security-scanUse for an authorized codebase scan for secrets, vulnerable dependencies, and risky code paths.
securityUse when a verid module needs a security review before closure, alone or as the security part of a combined review.
tddUse when writing or changing verid tests and production code.
ui-ux-pro-maxUse for UI layout, design systems, accessibility, and interaction design.
web-testingUse for browser, accessibility, visual, load, and integration test design.
Subagents (14)
architectUse when agreed verid research needs an architecture proposal or an approved design draft.
brainstormerUse when a verid feature needs a focused comparison of possible approaches before design approval.
code-simplifierUse after a passing verid cycle when recently changed code may be simpler without changing behavior.
coderUse when a verid AC has a recorded failing test or an open stub step.
debuggerUse when a verid test, build, or runtime failure needs a second read-only root-cause investigation.
docs-managerUse when documentation needs an accuracy and consistency review against verid's code and decisions.
plannerUse when a verid design needs proposed module boundaries or an approved plan draft.
project-managerUse when the developer needs a factual progress report across verid modules.
qaUse when a verid (e2e) acceptance criterion needs a failing test of the real product.
reviewerUse when a verid module, whole product or signed auto plan needs an independent review.
securityUse when a verid module has passed correctness review and needs its security review.
technical-researcherUse when a verid design or implementation needs current technical evidence outside the repository.
testerUse when one verid acceptance criterion needs its failing test before implementation.
ui-ux-designerUse when a verid module changes a screen and needs a focused UI and accessibility critique.
Maintain verid?
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.