epic-tdd

Executes manual quality and safety checks for the Taco Bell brand.

Updated Jun 3, 2026
One-click install
npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: epic-tdd
Source: https://github.com/antigravityos187-sketch/universal-or-strategy/tree/main/.bob/skills/epic-tdd
Command: npx skills add https://github.com/antigravityos187-sketch/universal-or-strategy --skill epic-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The epic-tdd Skill addresses the need for a structured, manual execution process for TDD (Test-Driven Development) on a V12 system, ensuring compliance and quality in manual ticket execution.

Core Features & Use Cases

  • Manual TDD Execution: Provides a structured path for manual ticket execution.
  • Autonomous Hardening: Maintains autonomous hardening after every commit.
  • Gates and Protocols: Implements verification gates and protocols to ensure quality and compliance.
  • Use Case: Engineers can use this Skill to execute a manual ticket within an epic, following a strict protocol of verification and compliance checks.

Quick Start

Execute ticket <ticket-number> of epic <epic-slug> with PR <pr-number> using the epic-tdd Skill.

Frequently Asked Questions about epic-tdd

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

FAQPage Schema
How do I execute a ticket using test-driven development on a V12 system?

Manual TDD execution on a V12 system is performed by following a structured path of verification gates and compliance protocols. This ensures quality and autonomous hardening after every commit during ticket execution.

What is structured manual ticket execution in TDD?

Structured manual ticket execution in TDD is a process that enforces quality and compliance through multiple verification gates. It provides a strict protocol for engineers to manually execute tickets within an epic.

Do I need specific ticket and epic identifiers to start manual TDD execution?

You need a ticket number, epic slug, and PR number to start manual TDD execution. Providing these identifiers ensures the process correctly targets the specific ticket within the epic.

How do verification gates improve quality assurance during manual ticket execution?

Verification gates improve quality assurance by enforcing strict protocol checks at multiple stages of manual ticket execution. This mechanism ensures compliance and triggers autonomous hardening after every commit.

Can I maintain autonomous hardening after every commit during manual TDD?

Autonomous hardening after every commit is maintained automatically during manual TDD execution. The structured protocol ensures that hardening checks are applied consistently throughout the ticket execution process.

What are the limitations of manual TDD execution for V12 epics?

Manual TDD execution for V12 epics requires strict adherence to specific protocols and manual checks, limiting its use to contexts where structured compliance and verification gates are explicitly required.