Implement product specifications into incremental, tested source code.
npx skills add https://github.com/woink/harness-skills-plugin --skill harness-builder
Please help me install this Agent Skill. Skill: harness-builder Source: https://github.com/woink/harness-skills-plugin/tree/main/skills/harness-builder Command: npx skills add https://github.com/woink/harness-skills-plugin --skill harness-builder
Converts a planner's product specification into incrementally built, tested, and versioned source code while coordinating contracts with an independent evaluator, removing ad-hoc development and unclear acceptance criteria from the implementation phase.
Use the harness-builder skill to implement the next sprint from .harness/PRODUCT_SPEC.md and draft .harness/SPRINT_CONTRACT.md for evaluator review.
High-intent search queries and answers about installing and using this skill.
To implement product specifications incrementally, you propose sprint contracts, enforce test-driven development, and archive sprint artifacts. This process converts specifications into versioned source code while coordinating acceptance criteria with an independent evaluator.
Test-driven development with sprint contracts is a process where features are implemented incrementally based on a product spec, requiring a SPRINT_CONTRACT.md review by an evaluator before handoff. It ensures engineering discipline through enforced TDD and meaningful git commits per change.
To handle sprint-based builds for existing codebases, you should read a CODEBASE_AUDIT.md file to preserve architecture and conventions. You can also run a Sprint 0 for housekeeping tasks to align the existing project before implementing new features.
Yes, sprint-based implementation supports QA retries and polish iterations by handing off file-based state for cold QA and applying targeted refinements from a POLISH_REPORT.md. It also supports pivot accept and reject flows while documenting recovery tags.
You need to read and write .harness files to start building code from a product spec. Specifically, you reference .harness/PRODUCT_SPEC.md to plan the implementation and draft .harness/SPRINT_CONTRACT.md for the evaluator to review before coding begins.
You should not use an incremental sprint implementation approach if your project lacks a clear product specification or an independent evaluator to review sprint contracts, as the workflow relies on negotiating acceptance criteria and file-based state handoffs to ensure code quality.
sunLeeeTransform PRDs into technical specifications with API definitions, data models, and sequence diagrams.
WellApp-aiVerify commits against QA Contracts with lint, type, and test checks.
hbvg234Fetch current library and framework documentation via Context7 MCP.
ChegginCoordinate machine-verified sprint contracts between generator and evaluator agents.
