builder-r

Automate multi-phase TDD lifecycles with iterative build and code-review cycles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill orchestrates the full lifecycle of a multi-phase TDD, automating review, improvement, build, code-review, updates, and phase advancement across multiple phases.

Core Features & Use Cases

  • Orchestrated phase loop: coordinates architect, builder, and code-review steps for each phase from review to completion.
  • Deterministic progression: enforces a repeatable cycle of review, build, review, update, and phase advance.
  • Progress-aware planning: tracks phase status and allows user confirmation before applying improvements or advancing.

Quick Start

Start the builder-r with /builder-r [path-to-tdd]. Example: /builder-r docs/tdd/angularjs-to-vue-migration.md

Frequently Asked Questions about builder-r

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

FAQPage Schema
How do I automate the test-driven development lifecycle across multiple phases?

Automating the test-driven development lifecycle requires orchestrating a multi-phase loop of review, build, code-review, and update steps. This Skill coordinates these recursive cycles automatically until all project phases are marked COMPLETE.

What is an orchestrated TDD phase loop and how does it work?

An orchestrated TDD phase loop coordinates architect, builder, and code-review steps for each phase. It enforces a deterministic progression by cycling through review, improvements, build, code-review, updates, and phase advancement.

How do I execute a multi-phase TDD build and review cycle?

To execute a multi-phase TDD build and review cycle, initiate the Skill with your TDD document path. It guides the project through iterative phase reviews, applies improvements, builds, and runs code-reviews until completion.

Can I track progress and confirm improvements during automated code review cycles?

Yes, progress-aware planning tracks phase status and requires user confirmation before applying improvements or advancing phases. This ensures manual oversight during the automated build and code-review cycles.

Do I need a specific document format to start the TDD orchestration?

You need a markdown document detailing your TDD phases. You start the orchestration by providing the path to this document, such as docs/tdd/migration.md, to initiate the automated lifecycle.