agentsclimarketplace
Sign in

Testing tdd

Skill planifest/planifest-framework/planifest-framework/external-skills/testing-tdd

Red-green-refactor workflow for test-first implementation feedback loops. Use when behavior and design must evolve safely through small increments backed by failing-then-passing tests; do not use for post-hoc test backfilling only.From its SKILL.md

Install
npx -y skills add planifest/planifest-framework --skill testing-tdd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 326 tokens by cl100k_base, as published. Nobody here has run it

Testing TDD

Overview

Use this skill to drive implementation through fast red-green-refactor cycles with explicit design feedback.

Scope Boundaries

  • Use when implementation should be guided by failing tests first.
  • Typical requests:
    • Develop a new feature with strict red-green-refactor discipline.
    • Reduce refactor risk with micro-cycle verification.
    • Use tests to shape API and domain design incrementally.
  • Do not use when:
    • Tests are added only after full implementation.
    • The primary goal is performance/load experimentation.

Inputs

  • Target behavior and constraints
  • Existing test harness and coding standards
  • Cycle-time and commit-granularity expectations

Outputs

  • Red-green-refactor evidence at incremental steps
  • Decision record for cycle design and test scope
  • Verification checklist for regression safety

Workflow

  1. Write a failing test for the smallest next behavior.
  2. Implement the minimal change to pass.
  3. Refactor while keeping tests green.
  4. Repeat in small increments with explicit intent.
  5. Publish residual risks and uncovered behaviors.

Quality Gates

  • Every implementation step is preceded by a failing test.
  • Steps remain small enough for quick diagnosis and rollback.
  • Refactoring preserves behavior with green evidence.
  • Assumptions and unresolved risks are explicit.

Failure Handling

  • Stop when implementation proceeds without prior failing tests.
  • Escalate when cycle size becomes too large for reliable feedback.

Bundled Resources

  • references/trigger-and-examples.md: trigger patterns, anti-patterns, and deliverable expectations.

What ships with it: 1 file

11.3 KB alongside SKILL.md

Keep looking

Skills are one crate of 326,750. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.