write-tests

Generate failing test scaffolds from todos or requirements for TDD workflows.

2.5k|421|Updated Oct 1, 2025

Search Tags:#pytest #test-driven #todo #acceptance-criteria #software-testing #write-tests

Ready to run

npx skills add https://github.com/meta-pytorch/OpenEnv --skill write-tests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: write-tests
Source: https://github.com/meta-pytorch/OpenEnv/tree/main/.claude/skills/write-tests
Command: npx skills add https://github.com/meta-pytorch/OpenEnv --skill write-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps software teams automatically convert a well-defined todo or requirement into a set of failing tests, enabling fast validation of acceptance criteria before any code is written.

Core Features & Use Cases

Test-Driven Guidance: Generate focused test scaffolds from a todo or requirement to verify expected behavior.
Pre-Implementation Validation: Ensure every todo has corresponding tests to guard against scope creep and regressions.
Use Case: Given a todo like Add logout button to header, produce a test outline and example assertions that fail until the feature is implemented.

Quick Start

Use the write-tests command to generate a failing test scaffold from a provided todo or requirement, then run your test suite to confirm it initially fails and guides implementation.

Frequently Asked Questions about write-tests

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

FAQPage Schema

How do I write tests before implementing features?▼

Test-driven development writes failing tests first to define expected behavior before coding. This Skill generates test scaffolds from your todo or requirement, ensuring tests fail initially and guide implementation toward acceptance criteria.

Can I generate pytest tests from acceptance criteria?▼

Yes. Provide a well-defined todo or requirement, and this Skill generates failing pytest test scaffolds with example assertions that validate your acceptance criteria, ready to run before any code is written.

What's the best way to ensure todos have test coverage?▼

Convert each todo into failing tests before implementation to prevent scope creep and regressions. This Skill reads existing tests, creates focused scaffolds from your requirement, and returns file paths for the /implement step.

How do I validate acceptance criteria before coding?▼

Write failing tests that encode your acceptance criteria upfront. This Skill generates test outlines and assertions from your todo—like testing an 'Add logout button' feature—so implementation must satisfy the tests to pass.

Do I need existing tests to use test-driven development?▼

No. This Skill reads your existing test suite if present to match patterns, then generates new test scaffolds from scratch based on your todo or requirement, even in new test files.

Why should I write failing tests first?▼

Failing tests clarify requirements, prevent incomplete implementations, and create regression guards. They transform vague todos into concrete acceptance criteria your code must satisfy before merging.