build

Execute sprint plans by implementing steps, running tests, and preparing pull requests.

4|Updated Apr 15, 2026

Search Tags:#automation #testing #branching #pr #sprint #build-plan

Ready to run

npx skills add https://github.com/markhazlett/agent-harness --skill build-markhazlett

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build
Source: https://github.com/markhazlett/agent-harness/tree/main/.claude/skills/build-plan
Command: npx skills add https://github.com/markhazlett/agent-harness --skill build-markhazlett

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sprint planning and delivery often stall due to manual orchestration, conflicting steps, and inconsistent verification. This Skill provides an end-to-end workflow to read a sprint plan, implement steps, run tests, verify in the browser, and prepare incremental changes for PRs.

Core Features & Use Cases

End-to-end sprint plan execution: read plan documents, implement steps, and ensure ongoing validation through tests and browser checks.
Guardrails and safety: enforce branching rules, automated checks, and safe commits to protect main and maintain code quality.
Incremental delivery: commit changes step-by-step as each plan item is completed, with traceable progress and PR readiness.

Quick Start

Follow the on-demand sprint-plan process to execute a given plan document and verify results.

Frequently Asked Questions about build

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

FAQPage Schema

How do I automate sprint plan execution from implementation to pull request?▼

You can automate sprint plan execution by reading a plan document, implementing each step incrementally, running tests, verifying changes in the browser, and preparing a pull request with branching guardrails to protect mainline safety.

What is the best way to ensure mainline safety when automating incremental commits?▼

To ensure mainline safety during incremental commits, apply automated guardrails that enforce branching rules, run automated tests, and perform browser verification before allowing changes to be prepared for a pull request.

Do I need existing repository conventions to automate end-to-end sprint delivery?▼

Yes, automating end-to-end sprint delivery requires existing repository conventions for plan structure, test orchestration, and browser verification to properly execute steps and report progress via helper scripts.

How does automated browser verification work during sprint plan execution?▼

Automated browser verification works by validating implemented sprint plan steps directly in the browser environment, ensuring that incremental code changes function correctly before proceeding to commit and pull request preparation.

Can I track sprint progress automatically when executing a plan document?▼

Yes, you can track sprint progress automatically by integrating with helper scripts like bin/conductor-status, which report traceable progress as each plan item is completed through incremental commits.

Why use automated guardrails for branching and test orchestration during development?▼

Automated guardrails for branching and test orchestration prevent manual orchestration errors, avoid conflicting implementation steps, and maintain consistent verification to protect code quality throughout the sprint delivery workflow.