Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Junior Test Drive Developer (TDD)

    1

    Strict TDD implementation agent that executes single tasks without scope creep or architecture drift.

    $5

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    Junior Test Drive Developer (TDD)

    Junior Test Drive Developer (TDD)

    Example session with this skill installed

    Implement T-001 for the "Vault" project. Goal: add basic encryption to the storage module. Tasks are at plans/tasks.md. Follow TDD. Only touch files listed in T-001.

    • Read your context and instructions
    • Compiled the junior test drive

    I have implemented task T-001 (Encryption Implementation) for the Vault project. The implementation followed the strict RED-GREEN-REFACTOR cycle, and no files outside the authorized list were modified.

    TDD Implementation Report: T-001

    SectionDetails
    Task IDT-001
    Statusready
    StoryAs a user, I want my stored notes encrypted so they are not readable in plain text on disk.
    Files Modifiedtests/test_crypto.py (created), vault/crypto.py (created)
    RED StepRan pytest tests/test_crypto.py. Failed with ImportError (Module not found).
    GREEN StepRan pytest tests/test_crypto.py. Passed after implementing minimal AES logic.
    Existing TestsAll 12 existing suite tests passed.
    RefusedRefused request to add cryptography library; used stdlib hashlib and secrets to avoid stack drift.

    Next steps

    • Review the handoff at plans/tdd-T-001.md.
    • Run the QA Engineer skill to verify the implementation against the full product spec.
    • Proceed to task T-002 (Key Rotation) once T-001 is merged.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    The problem

    LLM developers often over-implement, skipping test-driven protocols and introducing architecture drift or "scope creep" into single tasks. This leads to messy diffs where production code is written before a failing test exists, or dependencies are added without architectural approval.

    What it does

    • Enforces a strict RED-GREEN-REFACTOR cycle by requiring a verified failing test before any production code is written.
    • Constrains file modifications exclusively to the paths defined in the task handoff.
    • Identifies and blocks implementation if the task requires unauthorized architecture changes like new databases or SDKs.
    • Generates a standardized TDD handoff report documenting the specific commands used for test failure and success.

    Why this beats prompting it yourself

    Generic prompts often result in the agent "helping" by starting the next task or refactoring files it wasn't assigned to touch. This skill provides a rigid procedural framework that treats the task list as a binding contract, ensuring your codebase remains clean and your PRs remain focused.

    Use cases

    • Implementing individual features from a pre-defined senior planner backlog.
    • Fixing specific bugs that require a reproduction test case before a patch.
    • Adding atomic functions to an existing module while strictly adhering to a provided architecture spec.
    • Running a "junior" agent in a multi-agent workflow to handle isolated implementation tickets.

    Known limitations

    This skill requires a pre-existing task list and architecture document to function. It will not create project plans, choose your tech stack, or perform final QA sign-off.

    Requires pre-defined project_path and tasks_path. Only handles one task_id per run. Blocks if files needed for the task aren't explicitly listed in the task plan.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    Permissions

    Read Files
    Write Files
    Listed2 months ago
    Updated1 month ago

    What's inside

    Frequently Asked Questions

    This skill forces the agent to follow a strict Red-Green-Refactor workflow, requiring a verified failing test before any production code can be written. This prevents 'hallucinated features' and ensures that every change is backed by a specific requirement.

    The Junior TDD agent is designed to be framework-agnostic and works with any environment where you can execute shell commands for testing, such as Python (pytest), JavaScript (Jest), or Go.

    No, this skill is designed for execution, not planning. It requires a pre-defined task list and architecture document provided at runtime to ensure it stays within the boundaries of your project.

    You will receive the complete skill definition, including the rigid procedural framework and the standardized TDD handoff report template, ready to be integrated into your existing agent workflow.

    This skill is optimized for agents with tool-calling capabilities and file-system access, making it an ideal 'worker' agent in multi-agent systems or a standalone implementation tool.

    New in Agents & Orchestration