Testing
Unit tests, integration tests, test automation
ring:dev-property-testing
by LerianStudio
Gate 5 of development cycle - ensures property-based tests exist to verify domain invariants hold for all randomly generated inputs.
ring:dev-frontend-visual
by LerianStudio
Gate 4 of frontend development cycle - ensures all components have snapshot tests covering all states, viewports, and edge cases.
ring:condition-based-waiting
by LerianStudio
Flaky test fix pattern - replaces arbitrary timeouts with condition polling that waits for actual state changes.
ring:testing-anti-patterns
by LerianStudio
Test quality guard - prevents testing mock behavior, production pollution with test-only methods, and mocking without understanding dependencies.
ring:dispatching-parallel-agents
by LerianStudio
Concurrent investigation pattern - dispatches multiple AI agents to investigate and fix independent problems simultaneously.
ring:testing-agents-with-subagents
by LerianStudio
Agent testing methodology - run agents with test inputs, observe outputs, iterate until outputs are accurate and well-structured.
ring:testing-skills-with-subagents
by LerianStudio
Skill testing methodology - run scenarios without skill (RED), observe failures, write skill (GREEN), close loopholes (REFACTOR).
ring:dev-unit-testing
by LerianStudio
Gate 3 of development cycle - ensures unit test coverage meets threshold (85%+) for all acceptance criteria using TDD methodology.
ring:dev-fuzz-testing
by LerianStudio
Gate 4 of development cycle - ensures fuzz tests exist with proper seed corpus to discover edge cases, crashes, and unexpected input handling.
ring:dev-cycle-frontend
by LerianStudio
Frontend development cycle orchestrator with 9 gates. Loads tasks from PM team output or backend handoff and executes through implementation → devops → accessibility → unit testing → visual testing → E2E testing → performance testing → review → validation.
ring:dev-cycle
by LerianStudio
Main orchestrator for the 10-gate development cycle system. Loads tasks/subtasks from PM team output and executes through implementation → devops → SRE → unit testing → fuzz testing → property testing → integration testing (write) → chaos testing (write) → review → validation gates (Gates 0-9), with state persistence and metrics collection. Gates 6-7 (integration/chaos) write and update test code per unit but only execute tests at end of cycle (deferred execution).
drive-new-project
by p-wegner
Drive a freshly-created project hands-off to a finished multi-ticket epic — the playbook for "use the board to build a new app / implement a 10+ ticket epic" tickets. Encodes the completion CONTRACT (keep the meta-ticket In Progress until the epic is N/N Done, then drive the meta itself to Done — not parked in Review), a preflight prerequisites check, fan-out epic seeding, autodrive enablement, and a REQUIRED resident watch that recovers stalls instead of abandoning them. Use when a ticket asks you to register/scaffold a new project and take it to completion via the board.
test-coverage
by Montimage
Expand unit test coverage by targeting untested branches and edge cases. Use when users ask to "increase test coverage", "add more tests", "expand unit tests", "cover edge cases", "improve test coverage", or want to identify and fill gaps in existing test suites. Adapts to project's testing framework.
coverage-intelligence
by p-wegner
Build a multidimensional functional-coverage model for a software system and rank the highest-ROI verification gaps. Binds the observable-behaviour model (from behavior-discovery) against requirements (PRD/ADRs/user stories/acceptance criteria), the existing test suites (unit/integration/e2e), and historical signals (git churn, bug history) to compute — per behaviour — whether it is covered / partial / uncovered / undocumented-implemented / documented-missing, across many orthogonal coverage dimensions (capability, requirement, workflow, permission, navigation, API, error, boundary, state-transition, config, accessibility, regression, risk). Produces a coverage matrix, gap report, and an ROI-ranked test backlog. NOT line coverage. Use when the user asks "what's our real test coverage", "what behaviour is unverified", "where are the coverage gaps", "what tests give the most value", "map requirements to tests", "build a coverage model", or as phase 2 of an end-to-end verification effort.
cleanup
by p-wegner
"Clean up stale agentic-kanban resources including git worktrees, Claude Code sessions, and E2E test artifacts."
java-backend-planner
by p-wegner
Explore codebase in parallel with subagents, interview user on requirements and constraints, then synthesize a phased Java backend implementation plan with tech stack decisions, module structure, risks, and DevOps strategy
building-router
by Bbeierle12
Router for 3D building game mechanics in Three.js. Use when creating survival games, sandbox builders, base builders, or any game with player-constructed structures. Routes to 9 specialized skills for performance, physics, multiplayer, terrain, decay, UX, platform support, and design reference. Start here for building mechanics projects.
behavior-discovery
by p-wegner
Build a high-confidence model of a software system's EXTERNALLY OBSERVABLE behaviour — capabilities, actors, permissions, entry points, workflows, state transitions and error states — by combining many evidence sources (domain docs, OpenAPI/GraphQL schemas, source, routing, running-UI exploration, existing tests, git history) and degrading gracefully when some are absent. Infers business semantics; never paraphrases code. Marks unknowns explicitly instead of guessing. Output is the shared _behavior-model.json that the coverage-intelligence and e2e-test-author skills consume. Use when the user asks to "model what the app does", "discover observable behaviour", "build a verification/behaviour model", "explore the running app and map its capabilities", or as phase 1 of an end-to-end verification effort.
quality-metrics-collector
by p-wegner
Collect repository code-health metrics and POST them to the board Quality Metrics API
count-code-lines
by p-wegner
Count productive code lines per package using scc, scoped to actual source directories
architecture-review
by p-wegner
Exhaustive architecture review — spawns parallel analysis agents, synthesizes findings, and creates kanban tickets for the top weaknesses
flaky-test-triage
by p-wegner
Classify a failing test as known-flaky vs real regression, then re-run with the right strategy instead of debugging flakes or wrongly dismissing real failures
robotframework-testcase-builder
by manykarim
Generate Robot Framework test cases from structured requirements or scenarios. Use when asked to create test cases, apply tags/setup/teardown/templates, or produce keyword-driven tests.
e2e-test-author
by p-wegner
Generate the highest-ROI end-to-end tests from a prioritized coverage-gap backlog, then subject them to an adversarial review that tries to REFUTE them before they land. Consumes the verification model (_priorities.md / _coverage.json from coverage-intelligence), authors complete user-workflow tests (not isolated clicks) using the target project's own anti-flake conventions, makes each test DECLARE the coverage dimensions it contributes, runs independent adversarial reviewer subagents (overfitted assertions, flaky interactions, false positives, missed edge cases), fixes what they find, and writes the new coverage back into the model so re-running the pipeline improves. Use when the user asks to "write the missing tests", "generate high-value e2e tests", "author tests for the coverage gaps", "close the top coverage gaps", or as phase 3 of an end-to-end verification effort. For a single ad-hoc test in agentic-kanban use the project e2e-author skill instead; this skill is the gap-driven, reviewed, batch author.