Run any Skill in Manus with one click

Get Started

plan-tdd

Stars0

Forks0

UpdatedApril 10, 2026 at 10:44

Create a test-driven development plan for the project

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

stevengonsalvez

stevengonsalvez/nanoclaw-standalone

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

SKILL.md

readonly

name	plan-tdd
description	Create a test-driven development plan for the project
user-invocable	true

Create a test-driven development plan for the project: $ARGUMENTS

Follow these steps:

Read the specification:
- Look for the spec file specified in $ARGUMENTS
- If no file specified, look for spec.md or ask for the specification file path
- Understand the project requirements, acceptance criteria, and expected behavior
Draft a TDD-focused development blueprint:
- Break down the project into testable components and features
- Identify the testing strategy: unit, integration, and end-to-end tests
- Plan for incremental development with early and continuous testing
- Ensure each step includes comprehensive test coverage
- Design for testability from the beginning
Create test-first development chunks:
- Review the breakdown and organize into TDD cycles
- Ensure steps are small enough to implement safely with strong testing
- Make sure steps provide meaningful progress while maintaining test coverage
- Iterate until steps are appropriately sized for TDD methodology
Generate TDD implementation prompts:
- Create detailed prompts that follow the TDD red-green-refactor cycle
- For each step: write failing tests first, then implementation, then refactor
- Prioritize best practices, incremental progress, and comprehensive testing
- Ensure no big jumps in complexity between TDD cycles
- Make sure each prompt builds on previous work with maintained test coverage
- End with integration steps that wire everything together under test
Structure the TDD workflow:
- Define the testing framework and tools to be used
- Establish test file organization and naming conventions
- Plan for test data management and mock strategies
- Include performance and integration testing milestones
Generate comprehensive documentation:
- Save the TDD plan as tdd-development-plan.md
- Create tdd-implementation-prompts.md with step-by-step TDD prompts
- Generate testing-strategy.md outlining the overall test approach
- Include examples of expected test structure and patterns

Remember: Every feature should be developed test-first, with failing tests written before any implementation code.

More from this repository

same repository

argus

stevengonsalvez/nanoclaw-standalone

Argus — all-in-one information gathering & reconnaissance toolkit. 135 modules covering network infrastructure, web app analysis, and security/threat intelligence. Use for domain recon, subdomain enum, SSL analysis, tech stack detection, vulnerability scanning, and OSINT.

2026-04-100

bitwarden

stevengonsalvez/nanoclaw-standalone

Manage secrets via Bitwarden CLI (bw). Use when pulling secrets into a shell session, creating/updating Secure Notes from .env files, listing vault items, or setting up Bitwarden on a new machine. Secrets live in Bitwarden, get loaded into memory on demand, and die with the shell session — no files on disk.

2026-04-100

brainstorm

stevengonsalvez/nanoclaw-standalone

Develop a thorough, step-by-step specification for a given idea

2026-04-100

build-tracker

stevengonsalvez/nanoclaw-standalone

Set up a recurring build tracker cron job for any GitHub repo. Runs a zero-LLM shell script to detect stale PRs, stale assigned issues, and phase progress, then posts to a Discord channel only when there's something actionable. Use when asked to "track this build every N hours", "prod agents on a project", "set up a build monitor", "watch this repo for stale work", or similar. The tracker is cheap to run — script does all the work, the agent only speaks when findings exist.

2026-04-100

cloud-coding-agent

stevengonsalvez/nanoclaw-standalone

Run long-running coding tasks in cloud environments (Claude Code or Codex), with session teleporting and automatic PR creation.

2026-04-100

coding-agent

stevengonsalvez/nanoclaw-standalone

Delegate coding tasks to subagents or run Claude Code/Codex in tmux sessions. Use the Task tool for focused multi-step coding work. Use tmux for long-running interactive sessions, parallel worktree-based fixes, and PR reviews. NOT for simple single-file edits — do those directly.

2026-04-100

name	plan-tdd
description	Create a test-driven development plan for the project
user-invocable	true

Create a test-driven development plan for the project: $ARGUMENTS

Follow these steps:

Read the specification:
- Look for the spec file specified in $ARGUMENTS
- If no file specified, look for spec.md or ask for the specification file path
- Understand the project requirements, acceptance criteria, and expected behavior
Draft a TDD-focused development blueprint:
- Break down the project into testable components and features
- Identify the testing strategy: unit, integration, and end-to-end tests
- Plan for incremental development with early and continuous testing
- Ensure each step includes comprehensive test coverage
- Design for testability from the beginning
Create test-first development chunks:
- Review the breakdown and organize into TDD cycles
- Ensure steps are small enough to implement safely with strong testing
- Make sure steps provide meaningful progress while maintaining test coverage
- Iterate until steps are appropriately sized for TDD methodology
Generate TDD implementation prompts:
- Create detailed prompts that follow the TDD red-green-refactor cycle
- For each step: write failing tests first, then implementation, then refactor
- Prioritize best practices, incremental progress, and comprehensive testing
- Ensure no big jumps in complexity between TDD cycles
- Make sure each prompt builds on previous work with maintained test coverage
- End with integration steps that wire everything together under test
Structure the TDD workflow:
- Define the testing framework and tools to be used
- Establish test file organization and naming conventions
- Plan for test data management and mock strategies
- Include performance and integration testing milestones
Generate comprehensive documentation:
- Save the TDD plan as tdd-development-plan.md
- Create tdd-implementation-prompts.md with step-by-step TDD prompts
- Generate testing-strategy.md outlining the overall test approach
- Include examples of expected test structure and patterns

Remember: Every feature should be developed test-first, with failing tests written before any implementation code.