bad-skill

Automate the end-to-end ATDD workflow from issue creation to merge.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/o3-ozono/atdd-kit --skill bad-skill-o3-ozono
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bad-skill
Source: https://github.com/o3-ozono/atdd-kit/tree/main/tests/fixtures/claude-code/lint_skill_descriptions/bad
Command: npx skills add https://github.com/o3-ozono/atdd-kit --skill bad-skill-o3-ozono

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the ATDD workflow by guiding from acceptance tests to unit tests to implementation, reducing manual steps and errors.

Core Features & Use Cases

  • End-to-end ATDD guidance from issue creation to code verification
  • Structured workflow enforcement ensuring tests are written before implementation
  • Quick-start prompts and deterministic task orchestration for common software projects

Quick Start

Register the skill in Claude and begin guiding the ATDD workflow from issue formulation to code verification.

Frequently Asked Questions about bad-skill

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

FAQPage Schema
How do I automate the ATDD workflow from issue creation to merge?

Automating the ATDD workflow involves guiding development from acceptance criteria to test scaffolding and implementation. This skill orchestrates that end-to-end process, ensuring tests are written before code to reduce manual steps and errors.

What is the best way to enforce a tests-first development approach in my software projects?

A tests-first approach is enforced through structured workflow determinism. This skill guides acceptance test-driven development by prompting for acceptance criteria and unit tests before implementation, ensuring a minimal but structured workflow.

How does issue-to-merge test-driven development guidance work?

Issue-to-merge guidance works by automating task orchestration from issue formulation to code verification. It provides quick-start prompts to guide developers through acceptance tests, unit tests, and final implementation.

Do I need any specific dependencies to run automated ATDD workflows?

No external dependencies are required to run automated ATDD workflows. The skill operates independently using frontmatter-driven configuration and optional asset directories to manage the end-to-end test-driven development process.

Can I use this ATDD workflow automation for any software engineering project?

Yes, this ATDD workflow automation suits common software projects adopting acceptance test-driven development. It uses deterministic task orchestration to guide the workflow from issue formulation directly to code verification.

What are the limitations of automating acceptance test-driven development with a guided workflow?

The scope is limited to projects adopting ATDD and relies on frontmatter-driven configuration. It provides a minimal but structured workflow, meaning highly customized testing frameworks may require manual intervention outside the guided steps.