implementation

Automate TDD-driven implementation workflows for Python and TypeScript projects.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/edlovesjava/horse-sense --skill implementation-edlovesjava
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: implementation
Source: https://github.com/edlovesjava/horse-sense/tree/main/horse/skills/implementation
Command: npx skills add https://github.com/edlovesjava/horse-sense --skill implementation-edlovesjava

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates disciplined software delivery by enforcing a test-driven, language-aware development workflow and aligning with project configurations.

Core Features & Use Cases

  • Guides the end-to-end implementation process from ticket intake to pull request.
  • Auto-detects project tooling (testRunner, linter, typeChecker) for Python and TypeScript projects and applies them throughout the workflow.
  • Enforces a test-first approach: write tests, implement, refactor, and validate with CI-ready steps.

Quick Start

Follow the outlined steps to implement a ticket using a TDD workflow.

Frequently Asked Questions about implementation

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

FAQPage Schema
How do I automate a TDD workflow for TypeScript and Python projects?

Automate your TDD workflow by applying language-aware tooling that auto-detects test runners, linters, and type checkers. This enforces a test-first development process from ticket analysis to pull request for Python and TypeScript projects.

What is the best way to structure a test-first development process from ticket intake to PR?

Structure your test-first development by guiding ticket analysis, branch naming, writing tests, creating minimal implementations, refactoring, running code quality checks, and updating sprint tracking before submitting a PR.

Can I enforce branching and pull request workflows across frontend and backend components?

Yes, you can enforce branching and pull request workflows across frontend and backend components by applying a structured, language-aware implementation process that standardizes ticket analysis to PR delivery.

Does this workflow support auto-detecting project tooling like linters and type checkers?

Yes, the workflow supports auto-detecting project tooling by automatically identifying and applying your configured test runners, linters, and type checkers throughout the Python and TypeScript development cycle.

How do I ensure my implementation passes CI-ready steps before submitting a pull request?

Ensure CI-ready steps by enforcing a test-first approach that validates your code through minimal implementation, refactoring, and automated code quality checks before finalizing the pull request workflow.