wf-builder

Generate production code, tests, and living documentation from milestone plans.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill wf-builder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-builder
Source: https://github.com/JSai23/claude-tooling/tree/main/compiled/wf/agentskills/wf-builder
Command: npx skills add https://github.com/JSai23/claude-tooling --skill wf-builder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineering teams reliably turn plans into concrete, testable software while keeping living documentation in sync with code and architecture.

Core Features & Use Cases

  • Production code and tests — working implementation with tests that verify behavior
  • Updated plan — progress, surprises, and decisions recorded as you build
  • Living docs — agent docs describing how the system works now, created or updated after implementation

Quick Start

Implement the first milestone from the current plan by writing production code, accompanying tests, and updating the living docs to reflect the changes.

Frequently Asked Questions about wf-builder

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

FAQPage Schema
How do I turn development plans into production code with tests?

To turn plans into production code, you implement each milestone by writing working code, verifying behavior with tests, and updating living documentation to reflect the architectural changes.

What is living documentation and how does it stay in sync with code?

Living documentation is agent docs describing how the system currently works, kept in sync by requiring code, tests, and doc updates to be completed together after each milestone implementation.

How do I enforce design-doc alignment during plan-driven development?

You enforce design-doc alignment by requiring implemented production code, accompanying tests, and updated living docs to be completed and recorded after each milestone is reached.

Can I use this for plan-driven workflows with milestone-based architecture updates?

Yes, this approach is designed for plan-driven development workflows where milestones drive implementation and require documentation updates across the codebase to maintain alignment.

What's the best way to manage surprises and decisions during code implementation?

The best way to manage surprises is by updating the plan during implementation, recording progress, unexpected issues, and decisions as you build each milestone.

Do I need existing tests and docs to start a plan-to-code workflow?

No, living docs are created or updated after implementation, and production tests are written alongside the code to verify behavior as you implement each milestone.