Skip to content
TrustedSkillsbeta
Back to all skills

Tdd Planning

Checked
desplega-ai·vlatest·testing

Generates test-driven development plans, outlining steps and tests to build software features systematically.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add desplega-ai/ai-toolbox --skill tdd-planning -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

desplega-ai

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned desplega-ai/ai-toolbox at 9748aabf72.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
9748aabf72
Manifest
cc-plugin/base/skills/tdd-planning/SKILL.md
Scanned
2 files, 477 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill facilitates Test-Driven Development (TDD) planning for software projects. It helps break down a feature request into smaller, testable units and generates initial tests before any code is written. The agent can create a plan outlining the steps needed to implement a new feature based on TDD principles, including writing failing tests first.

When to use it

  • New Feature Development: When starting work on a new software feature, use this skill to generate an initial development plan and test suite.
  • Refactoring Existing Code: Before refactoring existing code, leverage the skill to create tests that verify current functionality.
  • Complex Problem Solving: When tackling a complex problem with unclear requirements, use TDD planning to structure your approach and ensure thorough testing.
  • Learning TDD: For developers new to Test-Driven Development, this skill can provide guidance and examples of the process.

Key capabilities

  • Generates initial test cases based on feature requests.
  • Creates a development plan following TDD principles.
  • Breaks down features into smaller, testable units.
  • Outlines steps for writing failing tests first.

Example prompts

  • "Create a TDD plan to implement user authentication."
  • "Generate initial tests for the 'calculate shipping cost' feature."
  • “Outline a TDD approach for implementing a REST API endpoint.”

Tips & gotchas

The quality of the generated plan and tests depends heavily on the clarity and detail provided in the initial prompt. Be as specific as possible when describing the desired functionality to get the best results.