feature

Orchestrate Test-Driven Development for new feature implementation with API contracts.

24|3|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/Borda/.home --skill feature-borda
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature
Source: https://github.com/Borda/.home/tree/main/.claude/skills/feature
Command: npx skills add https://github.com/Borda/.home --skill feature-borda

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of developing new features using a Test-Driven Development (TDD) approach, ensuring code quality and adherence to best practices from the outset.

Core Features & Use Cases

  • TDD Orchestration: Guides the entire feature development lifecycle, from initial analysis to final review.
  • API Contract First: Prioritizes defining the feature's API through a failing demo use-case (doctest or script) before writing implementation code.
  • Iterative Implementation: Drives development through a loop of writing tests, implementing minimal code, and verifying against the full test suite.
  • Integrated Quality Gates: Includes mandatory steps for documentation, QA, linting, and code review.
  • Use Case: When adding a new predict_proba method to a machine learning model, this Skill ensures a clear API is defined via a doctest, the implementation passes that test and others, documentation is updated, and the code is linted and reviewed before merging.

Quick Start

Use the feature skill to add a batched predict() method to the Classifier, starting with a demo use-case doctest.

Frequently Asked Questions about feature

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

FAQPage Schema
How do I use TDD to develop a new feature from scratch?

Test-driven development for new features starts by analyzing scope and compatibility, defining an API contract via a failing demo doctest, then iterating through test-writing and minimal code implementation cycles.

What is an API contract-first approach in feature development?

An API contract-first approach establishes the feature's interface by writing a failing demo use-case doctest or test script before any implementation code, ensuring test-driven development drives the design.

How do I ensure code quality when adding new methods to an existing codebase?

Ensure code quality by orchestrating an iterative test-driven development loop that concludes with mandatory documentation updates, QA checks, linting, and a comprehensive code review pass.

Can I use this TDD workflow for adding machine learning methods like predict_proba?

Yes, this test-driven development workflow suits adding methods like predict_proba by defining the API via a doctest, implementing minimal code to pass tests, and running linting before merging.

What steps are included in an automated TDD feature lifecycle?

An automated TDD lifecycle includes initial purpose analysis, API contract creation via failing tests, iterative implementation, and final gates for documentation, QA, linting, and code review.

Does test-driven development work without external dependencies for new features?

Yes, this test-driven development workflow operates with no external dependencies, analyzing feature scope and compatibility internally before driving implementation through iterative test cycles.