test-first-development

Generate BDD/Gherkin feature files and TDD test scaffolding before coding.

12|41|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/pingwu/solo-unicorn --skill test-first-development
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-first-development
Source: https://github.com/pingwu/solo-unicorn/tree/main/skills/test-first-development
Command: npx skills add https://github.com/pingwu/solo-unicorn --skill test-first-development

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Helps teams define and lock in expected software behavior before coding by adopting BDD (Gherkin) for cross-functional alignment or TDD for fast, solo development.

Core Features & Use Cases

  • Choose BDD for collaborative scenarios that engage product, QA, and developers.
  • Choose TDD for fast iteration with well-defined requirements and edge-case coverage.
  • Guides acceptance criteria to tests and provides step definitions for outside-in development.
  • Use case: PM defines a feature, a developer writes tests first, and QA validates behavior.

Quick Start

Provide a feature description and let the skill generate Gherkin scenarios and test scaffolding.

Frequently Asked Questions about test-first-development

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

FAQPage Schema
How do I generate Gherkin feature files from acceptance criteria for BDD?

To generate Gherkin feature files, provide a feature description to define expected software behavior before coding. This creates BDD scaffolding with acceptance criteria and step definitions for cross-functional alignment among product, QA, and developers.

What is the difference between using BDD and TDD for test-first development?

Test-first development uses BDD with Gherkin for collaborative cross-functional alignment, while TDD supports fast solo iteration with well-defined requirements and edge-case coverage. BDD engages product and QA, whereas TDD focuses on outside-in development and refactoring safety nets.

How to write test stubs and step definitions for outside-in development?

Writing test stubs for outside-in development requires defining expected behavior upfront. Provide a feature description to generate test scaffolding and step definitions, locking in requirements before implementation to guide development and ensure edge-case coverage.

Can I use test-first development for solo projects without cross-functional teams?

Yes, test-first development supports solo projects by applying TDD for fast iteration. It guides acceptance criteria into tests, providing step definitions and refactoring safety nets without needing the cross-functional collaboration required by BDD.

When do I need Gherkin scenarios for feature development workflows?

You need Gherkin scenarios when cross-functional alignment matters in feature development. Generating BDD scaffolding engages product, QA, and developers by locking in expected software behavior through structured acceptance criteria before coding begins.