builder

Implement Technical Design Documents into phased, code-reviewed features.

Updated Jan 31, 2026
One-click install
npx skills add https://github.com/Kibbey/fyli --skill builder-kibbey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: builder
Source: https://github.com/Kibbey/fyli/tree/main/.claude/skills/builder
Command: npx skills add https://github.com/Kibbey/fyli --skill builder-kibbey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams convert Technical Design Documents into working software by enforcing TDD-driven, phased development and rigorous code reviews.

Core Features & Use Cases

  • TDD-Driven Implementation: Convert a TDD into incremental, test-backed code.
  • Phased Delivery: Execute work in clearly defined phases with milestones.
  • Code Review Automation: Prepare and submit work for code review to ensure quality.
  • Ambiguity Handling: Identify and surface uncertainties early to align with stakeholders.

Quick Start

Provide a TDD document to the builder to begin phased implementation, for example: /builder docs/tdd/new-feature.md. The skill will guide you through Phase 1: Analysis, then Phase 2: Foundation, etc.

Frequently Asked Questions about builder

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

FAQPage Schema
How do I implement features from a Technical Design Document using TDD?

To implement features from a Technical Design Document using TDD, provide the TDD to the builder skill. It executes work in defined phases, enforcing TDD discipline and isolating tasks to output incremental, code-reviewed features.

What is the best way to convert TDDs into phased, incremental code?

The best way to convert TDDs into incremental code is using a phased implementation approach. The builder skill analyzes the TDD, establishes a foundation, and delivers test-backed code through isolated, milestone-driven phases.

Can I handle ambiguity in requirements analysis before phased implementation?

Yes, you can handle ambiguity in requirements analysis before phased implementation. The builder skill identifies and surfaces uncertainties early during Phase 1 Analysis to align with stakeholders before writing code.

Does this phased implementation approach prepare work for code review?

Yes, this phased implementation approach prepares work for code review. The builder skill outputs task progress and automatically prepares and submits incremental, test-backed features for rigorous code reviews.