verify-implementation

Coordinate five-phase verification of implementations against requirements.

Updated Aug 29, 2025
One-click install
npx skills add https://github.com/teocrafters/public-talk-planner --skill verify-implementation-teocrafters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verify-implementation
Source: https://github.com/teocrafters/public-talk-planner/tree/main/.claude/skills/verify-implementation
Command: npx skills add https://github.com/teocrafters/public-talk-planner --skill verify-implementation-teocrafters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This verification workflow helps teams ensure that completed implementations meet all requirements by validating code changes, i18n key coverage, API contracts, and end-to-end flows before marking work as done.

Core Features & Use Cases

  • Code Implementation Verification: Validate new or changed files against the active requirements, including structure and quality gates.
  • i18n Keys Verification: Check translation keys exist in both Polish and English locales to prevent missing localization.
  • API Interface Verification: Compare frontend API usage with backend endpoints to detect mismatches in request bodies and responses.
  • Flow Testing with ChromeDevTools MCP: Execute browser-based end-to-end flows to verify user journeys and error handling.
  • Final Report Generation: Compile findings into a comprehensive report with actionable fixes.

Quick Start

Start the verification process with a running dev server and seeded test data, then follow prompts to complete all five phases.

Frequently Asked Questions about verify-implementation

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

FAQPage Schema
How do I verify completed software features against requirements before marking work as done?

You can verify completed software features by running a coordinated end-to-end verification workflow that checks code changes, i18n key coverage, API contracts, and browser-based user flows against an active requirement specification.

What is the best way to check for missing i18n translation keys across Polish and English locales?

Checking for missing i18n translation keys involves validating that all required localization strings exist in both Polish and English locales, preventing missing translations during the implementation verification phase.

How do I detect frontend and backend API contract mismatches during implementation?

Detecting API contract mismatches requires comparing frontend API usage with backend endpoints to identify discrepancies in request bodies and response structures before finalizing the implementation.

Can I run end-to-end flow testing with ChromeDevTools for user journey verification?

Yes, you can execute browser-based end-to-end flow testing using ChromeDevTools MCP to verify user journeys and error handling against a running development server with seeded test data.

Do I need a running development server and test accounts to start end-to-end verification?

Yes, starting end-to-end verification requires an active requirement specification, a running development server, and seeded test accounts to execute the five sequential verification phases successfully.