write-and-validate-tests

Drafts test cases from design documents and confirms them with users before implementation.

1|9|Updated Jul 11, 2026
One-click install
npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill write-and-validate-tests-agenticgogol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-and-validate-tests
Source: https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul/tree/main/.claude/skills/write-and-validate-tests
Command: npx skills add https://github.com/agenticgogol/Edureka_Coding_Agent_Enabled_Demo_11Jul --skill write-and-validate-tests-agenticgogol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Tests written by the same agent that writes the implementation can silently encode the same misunderstanding twice. This Skill inserts a human checkpoint: test cases are drafted in plain language from the brief and design, then confirmed by the user before any test or implementation code is written. ## Core Features & Use Cases - Plain-language test drafting: Derives test scenarios from project_brief.md's Definition of Done and design.md's API contract, covering golden paths, edge cases, and safety-relevant cases. - User confirmation gate: Explicitly asks the user whether the drafted scenarios match their intent before writing any code, catching divergent interpretations early. - Framework-specific implementation: Implements confirmed cases as pytest tests for backend/agent code and vitest/jest tests for frontend code, run per-slice as builders progress. - Use Case: After approving a design.md for a new API project, use this Skill to draft test scenarios, confirm them with stakeholders, and seed per-slice tests that block progress when they fail. ## Quick Start Ask the agent to draft test cases from the approved design.md and project brief, then review and confirm the plain-language scenario list before implementation begins.

Frequently Asked Questions about write-and-validate-tests

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

FAQPage Schema
How do I write test cases before implementation in an AI coding workflow?▼

Draft test scenarios in plain language from the brief's Definition of Done and the design's API contract, then confirm them with the user before writing code. Only after confirmation are they implemented as runnable pytest or vitest/jest tests.

Why should test cases be confirmed by a human before coding?▼

An agent that writes both tests and implementation can encode the same misunderstanding twice. A human checkpoint on the plain-language scenario list catches cases where the agent's reading of the brief diverges from actual user intent.

Which test frameworks does this workflow use for backend and frontend?▼

Backend and agent tests are implemented with pytest under backend/tests/, while frontend tests use vitest or jest under frontend/tests/. Each builder runs its own new tests immediately after writing a slice.

Does this Skill run the final full test suite for a project?▼

No. This Skill only drafts, confirms, and seeds per-slice test runs. The final test gate is owned by the separate run-tests skill, invoked after all components are built, while run-and-verify handles end-to-end verification.

When should a lightweight concept project skip a separate test suite?▼

For single-notebook concepts, the notebook's own Exercise and Expected Output sections can serve as the test cases. A separate test suite is only warranted when the concept has real branching logic worth testing.