Define and document TDD problems in a structured markdown file.
npx skills add https://github.com/amashigeseiji/tdd-skills --skill tdd-problem
Please help me install this Agent Skill. Skill: tdd-problem Source: https://github.com/amashigeseiji/tdd-skills/tree/main/tdd-problem Command: npx skills add https://github.com/amashigeseiji/tdd-skills --skill tdd-problem
This Skill helps in clearly defining problems for Test-Driven Development (TDD), ensuring that the problem statement is accurate and free of solution-oriented language.
problem.md file within the project directory.Run the tdd-problem skill to define the problem for your current project.
High-intent search queries and answers about installing and using this skill.
To define problems for test-driven development without solution-oriented language, you must capture the essence of the challenge purely as a problem statement. This Skill evaluates your input and saves a structured problem definition in a markdown file.
The best way to document a TDD problem statement is to save it as a structured `problem.md` file within your project directory. This ensures the problem definition is accurately preserved for future reference during software development.
Separating problem definition from solution design in TDD workflows prevents biasing the development process toward a specific implementation early. It ensures the problem statement remains accurate and strictly focused on the challenge itself.
Yes, you can use this Skill for any software development project using TDD methodologies. It is specifically designed for TDD-driven development workflows to help articulate and document project challenges clearly.
Defining problems for TDD with this Skill requires no specific dependencies or environment setup. It operates independently to capture your problem statements and generate a structured markdown file directly in your project directory.
ghufronbagaskaraGenerate markdown implementation plans with test-driven development steps.
sirius-cc-wuConvert spec.md into a phase-based plan.md with milestones and verification steps.
YoshikemoloAnalyze Jira velocity and capacity to forecast sprint outcomes.
shiroginCapture project identity, principles, stakeholders, boundaries, and success criteria.