tdd-feedback

Collect user feedback and evaluate TDD solutions after tdd-run sessions.

2|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/amashigeseiji/tdd-skills --skill tdd-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-feedback
Source: https://github.com/amashigeseiji/tdd-skills/tree/main/tdd-feedback
Command: npx skills add https://github.com/amashigeseiji/tdd-skills --skill tdd-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The tdd-feedback Skill addresses the challenge of collecting and documenting user feedback on implemented TDD solutions, enabling continuous improvement and quality assurance.

Core Features & Use Cases

  • User Feedback Collection: Gather insights on the effectiveness of TDD implementations through user interviews.
  • Solution Evaluation: Assess the performance of vocabulary and solution structures based on real-world usage.
  • Plan Closure Decision: Determine whether to close a plan, return to it, or create a new one based on findings.

Quick Start

Execute the tdd-feedback skill to initiate the feedback collection process after completing a tdd-run session.

Frequently Asked Questions about tdd-feedback

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

FAQPage Schema
How do I collect user feedback on implemented TDD solutions?

Gather user feedback on implemented TDD solutions by executing the tdd-feedback process, which facilitates user interviews and evaluates solution performance to document findings for continuous improvement.

What is the best way to evaluate TDD solution performance after a run?

The best way to evaluate TDD solution performance is to assess the effectiveness of vocabulary and solution structures based on real-world usage. This evaluation ensures continuous improvement and quality assurance for the implemented solutions.

When do I need to start the feedback collection phase in a TDD workflow?

You need to start the feedback collection phase immediately after completing a tdd-run session. Initiating this process requires interaction with the tdd-run phase to properly evaluate the implemented TDD solutions and document findings.

How do I decide whether to close a TDD plan or create a new one?

Decide whether to close a TDD plan, return to it, or create a new one by analyzing the documented findings from user interviews and solution evaluations. This plan closure decision is based on real-world usage insights.

Can I use this feedback collection process without completing a prior run phase?

No, you cannot use this feedback collection process without a prior run phase because it requires interaction with the tdd-run phase. You must complete a tdd-run session first to provide the implemented solutions for evaluation.