llipe

Perform bounded, delegated codebase investigation and emit a structured research artifact. Use when downstream agents need grounded, file-level evidence without pulling the search transcript into their own context.

Validate API contracts against implementation using dt verify (contract-diff, impact, drift). Detects breaking changes, consumer impact, and spec-to-code staleness. Use when checking API boundary integrity.

Author Playwright end-to-end tests from verifier scenario tables. Covers auth, state reset, CI config, and scenario-to-spec traceability. Use when writing or backfilling E2E tests.

Author integration tests (Layer 2.5) against real databases — local via testcontainers/docker-compose/Supabase CLI, remote via testing environments. Covers migrations, RLS, pgTAP, fixtures, and fallback paths. Use when writing or backfilling integration tests.

Establish and maintain a project's /TESTING.md contract, detect test-harness defects, and verify that every test package is reachable from the aggregate test command and the CI and deploy gates. Use when bootstrapping or refreshing the testing standard.

Template-aware mockup project creation with DESIGN.md-derived tokens. Supports html-lite (zero-install, navigable) and react-full (shadcn + Vite + Radix). Use when generating mockups from a PRD or spec.

Generate platform-specific theme artifacts from DESIGN.md. Use when mockups or production code need consumable tokens derived from the canonical design contract.

Clarify scope: produce a lightweight issue refinement or a full PRD. Use in product-engineer Feature or Issue Mode.

Design consumer/provider contract and schema-compatibility tests from a spec or story. Use when deriving contract test strategy during verifier design mode.

Routes verifier drift findings into task-list/GitHub-checklist expansion, new-issue creation, or PRD/spec changelog write-back with a human-confirmation gate. Use when a verifier fidelity report (Design or Audit Mode) surfaces drift that needs to be acted on.

Generate end-to-end black-box test scenarios from a spec or user stories. Use when deriving E2E compliance scenarios.

Systematically discover edge cases by category with concrete examples. Use when expanding coverage for input domains, state transitions, timing, and failure modes.

Transform an approved PRD into a technical specification. Use in product-engineer Feature Mode after refine.

Break a technical specification into user stories with coverage validation. Use after generate-spec.

Establish product-context.md and technical-guidelines.md foundation docs. Use in product-engineer Init Mode.

Publish user stories as GitHub Issues following github-ops conventions. Use after generate-stories.