tdd-workflow

An error occurred: 'dict' object has no attribute 'render'

1|Updated Jan 10, 2026
One-click install
npx skills add https://github.com/vinothpandian/v-marketplace --skill tdd-workflow-vinothpandian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-workflow
Source: https://github.com/vinothpandian/v-marketplace/tree/main/plugins/claude-conductor/skills/tdd-workflow
Command: npx skills add https://github.com/vinothpandian/v-marketplace --skill tdd-workflow-vinothpandian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates discipline around software delivery by enforcing a Test-Driven Development workflow that ties planning, testing, and code commits together.

Core Features & Use Cases

  • Red-Green-Refactor cycle: drives feature implementation with failing tests, minimal code, and refactoring after tests pass.
  • Plan-driven workflow: requires plan.md to track tasks and CI-aware checks to ensure quality gates.
  • Quality assurance & visibility: establishes commit messaging standards and coverage verification as part of the workflow.
  • Use Case: When implementing a new feature, create a task in plan.md, write failing tests, implement code to pass, and commit with a descriptive message.

Quick Start

Create a new task in plan.md and follow the Red-Green-Refactor cycle to implement it.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce a Test-Driven Development workflow from planning to commit?

You can enforce a Test-Driven Development workflow by using a structured Red-Green-Refactor cycle that requires a plan.md for task tracking, failing tests before implementation, and descriptive commit messages to tie planning and testing together.

What is the Red-Green-Refactor cycle for software implementation?

The Red-Green-Refactor cycle drives feature implementation by first writing failing tests, adding minimal code to pass those tests, and then refactoring the code while ensuring tests remain green throughout the process.

How do I integrate CI-friendly test strategies into my feature delivery process?

You integrate CI-friendly test strategies by establishing coverage verification and quality gates during development, ensuring that code commits pass automated checks tied to your plan.md task tracking workflow.

Do I need a plan.md file to start a TDD workflow for bug fixes?

Yes, a plan.md file is required to track tasks and guide the TDD workflow for bug fixes, ensuring disciplined planning, visible status marks, and detailed commit messages throughout the delivery process.

Can I use this TDD workflow for refactoring existing code across different languages?

Yes, this TDD workflow is applicable to software implementation tasks across languages, guiding your refactoring efforts by ensuring tests pass before and after you modify the codebase.

What is the best way to maintain code quality during continuous integration?

The best way to maintain code quality during continuous integration is to enforce strict commit messaging standards and coverage verification as part of a plan-driven TDD workflow with visible status marks.