tdd-setup

Create docs/vision.md capturing project purpose, users, principles, and success signals.

4|1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-setup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-setup
Source: https://github.com/CurtisThe/three-pillars-plugin/tree/main/skills/tdd-setup
Command: npx skills add https://github.com/CurtisThe/three-pillars-plugin --skill tdd-setup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Aligns project work by surfacing the project's why into docs/vision.md, ensuring a shared foundation before architecture or testing decisions.

Core Features & Use Cases

  • Aligns stakeholders by eliciting the project purpose and creating a living vision doc at docs/vision.md.
  • Defines a sequenced flow for TDD setup: /tdd-setup, /tdd-docs-init, and /tdd-test-setup to emit architecture, roadmap, and issues from the vision.
  • Keeps the scope focused on guiding early-stage planning, architecture decisions, and test strategy without dictating technical choices.

Quick Start

Start by running /tdd-setup to draft the vision and create docs/vision.md, then continue with /tdd-docs-init.

Frequently Asked Questions about tdd-setup

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

FAQPage Schema
How do I start a new software project with a vision document?

You start a new project with a vision document by running a conversational flow that captures your problem, users, principles, and non-goals, then records them into a living vision doc at docs/vision.md to align stakeholders.

What is vision-led TDD setup and why do I need it for project planning?

Vision-led TDD setup is a planning approach that surfaces your project's purpose into docs/vision.md before making architecture or testing decisions, ensuring every future step aligns with a shared foundation and prevents scope drift.

Can I use this project setup flow for an existing codebase?

This project setup flow applies specifically to fresh projects to produce a vision-driven foundation. It is designed to guide subsequent steps for architecture and testing setup from scratch rather than retrofitting existing codebases.

What's the best way to structure project planning before writing tests?

The best way to structure project planning before testing is a sequenced flow: draft the vision, then run docs initialization to emit architecture, roadmap, and issues, and finally configure the test setup based on that shared foundation.

Does the TDD setup process dictate specific testing frameworks or technical choices?

The TDD setup process does not dictate technical choices. It focuses on guiding early-stage planning, architecture decisions, and test strategy scope, ensuring the vision drives the framework selection rather than the tool forcing a stack.