lock-tests

Generate a failing test inventory from frozen spec and acceptance criteria.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/AndreJorgeLopes/devflow --skill lock-tests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lock-tests
Source: https://github.com/AndreJorgeLopes/devflow/tree/main/skills/lock-tests
Command: npx skills add https://github.com/AndreJorgeLopes/devflow --skill lock-tests

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents AI agent sessions from writing production code without first locking in a complete, behavior-focused set of failing tests derived from the frozen spec, plan, and acceptance criteria.

Core Features & Use Cases

  • Batch-failing test generation: Converts each acceptance criterion into one public-interface, behavior-only failing test placed in the project’s canonical test structure.
  • Test Inventory emission: Writes a traceable Test Inventory document mapping ACs to new tests, including considered-but-skipped edge cases and framework details.
  • Mandatory user approval gate: Blocks progression to implementation until the user explicitly approves the generated inventory (except for a trivial-change escape hatch).

Quick Start

Ask your agent to run lock-tests for the current feature branch so it generates the full failing test inventory from the frozen plan/spec artifacts and requests your approval before any implementation begins.

Frequently Asked Questions about lock-tests

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

FAQPage Schema
How do I prevent an AI coding agent from writing implementation code before tests are ready?

To prevent an AI coding agent from writing implementation code prematurely, use a mandatory user approval gate that blocks progression until a complete, behavior-focused failing test inventory is explicitly approved. This isolates testing phases from feature implementation.

How do I generate a failing test inventory from acceptance criteria for TDD?

Generate a failing test inventory for TDD by converting each frozen acceptance criterion into one public-interface, behavior-only failing test placed in the project's canonical test structure, ensuring all tests fail correctly before any production code is written.

What is a test inventory document in a git workflow?

A test inventory document in a git workflow is a traceable record mapping acceptance criteria to newly generated failing tests, including considered-but-skipped edge cases and detected test framework details, providing traceability before implementation begins.

Can I skip the test approval gate for trivial code changes?

Yes, you can skip the test approval gate for trivial changes using a specific escape hatch, bypassing the mandatory user approval block to allow immediate implementation without generating a full failing test inventory.

Does test generation work with any test framework?

Test generation works with various test frameworks by automatically detecting the framework used in the project's canonical test structure, ensuring the generated failing behavior tests are written and verified correctly within the existing environment.