tdd-init

Detect project stacks and generate TDD configuration files.

3|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/ForgePlan/marketplace --skill tdd-init-forgeplan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-init
Source: https://github.com/ForgePlan/marketplace/tree/main/plugins/agents-tdd/skills/tdd-init
Command: npx skills add https://github.com/ForgePlan/marketplace --skill tdd-init-forgeplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

The tdd-init Skill resolves the challenge of manually setting up TDD (Test-Driven Development) methodology for a project, automating the creation of necessary configuration files and stack definitions.

Core Features & Use Cases

  • Automated TDD Setup: Generates and manages the .forgeplan/tdd/stack.json configuration file for TDD gate operations.
  • Stack Detection: Automatically detects the project stack based on repository metadata.
  • User Reconciliation: Allows manual input or reconciliation with existing stack-ADR (Architecture Decision Record).
  • Re-run Capability: Allows re-run to update configuration after stack changes.
  • Use Case: For projects adopting TDD, this Skill can be used to quickly set up the TDD environment and ensure consistent TDD gate operations.

Quick Start

Run /tdd-init to configure the TDD stack for your project.

Frequently Asked Questions about tdd-init

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

FAQPage Schema
How do I automate test-driven development setup for a new project?

You can automate test-driven development setup by running a command to detect your project stack and generate the `.forgeplan/tdd/stack.json` configuration file for TDD gate operations.

Can I manually adjust the test stack configuration if auto-detection is wrong?

Yes, you can provide manual input or reconcile the automatically detected test stack configuration with your existing stack Architecture Decision Record to ensure accuracy.

What is the best way to update TDD stack configuration after changing project dependencies?

The best way to update TDD stack configuration after dependency changes is to re-run the initialization command, which allows you to refresh and update the stack definitions.

Do I need an existing Architecture Decision Record to configure a TDD environment?

No, an existing Architecture Decision Record is not required to configure a TDD environment, but you can use it for user reconciliation to align the generated stack configuration with your architectural decisions.

How does automated stack detection work for test-driven development workflows?

Automated stack detection works by interpreting your repository metadata to identify the project stack, then using that information to generate the necessary configuration files for consistent testing environments.