What are 'living docs' in the WF Builder system?

Living docs are design documents, architecture maps, and principles stored directly in the repository that describe the current state of the system, updated immediately after code changes.

Where does WF Builder store its documentation?

It uses a standardized hierarchy, placing system-level docs in a root design-docs folder and package-specific docs within respective package directories.

How does WF Builder handle changes to the original plan?

It follows a strict deviation protocol: if a plan conflict arises, it stops, explains the conflict, proposes a solution, and records the final decision before continuing.

What is the primary role of the WF Builder skill?

WF Builder acts as an implementation agent that translates technical plans into production-ready code and tests while simultaneously updating the project's living documentation.

Does this skill support test-driven development?

Yes, WF Builder treats tests as a core part of implementation rather than a separate phase, focusing on verifying real behavior rather than mocked abstractions.

WF Builder

Name: WF Builder
Author: JSai23

byJSai23

•

Productividad y Flujo de Trabajo

Implements production-ready code and tests from existing plans while maintaining synchronized living documentation.

WF Builder is a specialized Claude Code skill designed for the implementation phase of software development. It functions as a disciplined agent that executes milestones from a pre-defined plan, writes high-quality production code alongside comprehensive tests, and ensures that project documentation stays perfectly in sync with the codebase. By enforcing a strict deviation protocol and a documentation duty, it prevents architectural drift and ensures that every code change is reflected in the system's design docs, ARCHITECTURE.md, and relevant package-level guides, making it ideal for teams requiring high standards of maintainability.

Características Principales

01Concurrent test-driven development (TDD) with no stubs or placeholders

021 GitHub stars

03Strict deviation protocol for handling plan-to-code mismatches

04Automatic maintenance of living design documentation and ARCHITECTURE.md

05Milestone-based code implementation from structured plans

06Standardized directory structure for system and package-level docs

Casos de Uso

01Maintaining large codebases where documentation staleness is a critical risk

02Standardizing the transition between high-level planning and code implementation

03Executing technical implementation plans while keeping documentation updated in real-time

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add jsai23/claude-tooling wf-builder

For use in Claude.ai and ChatGPT

Download Skill