generator-execution

Execute a contract-bound sprint and produce runtime.md and handoff.md artifacts.

28|2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/thompson0012/agents-stack --skill generator-execution
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: generator-execution
Source: https://github.com/thompson0012/agents-stack/tree/main/templates/.agents/skills/using-agents-stack/generator-execution
Command: npx skills add https://github.com/thompson0012/agents-stack --skill generator-execution

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual and error-prone sprint execution after contract approval is prone to drift and missing reproducibility. This skill ensures a single, contract-bound sprint is executed with verifiable runtime evidence and a clean handoff.

Core Features & Use Cases

  • Enforces contract scope by executing only files allowed by contract.
  • Produces runtime artifacts like runtime.md and handoff.md for reviewer verification.
  • Supports retry and reconciliation states to maintain consistent sprint state and audit trail.

Quick Start

Provide an approved sprint contract and trigger generator-execution to produce a reproducible runtime and handoff.

Frequently Asked Questions about generator-execution

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

FAQPage Schema
How do I execute an approved sprint contract without scope creep?

Sprint contract execution uses generator-execution to process only files and artifacts listed in the contract, such as .harness/<sprint-id>/* and contract.md. It prevents scope creep by enforcing strict contract boundaries during runtime execution.

What is runtime evidence in sprint execution and why do I need it?

Runtime evidence provides reproducible artifacts like runtime.md and handoff.md generated during sprint execution. These artifacts capture verifiable proof of contract-bound changes, enabling reviewers to validate that execution stayed within approved scope.

How do I handle a failed contract review during sprint execution?

After state-update reconciles a failed evaluator-contract-review, generator-execution triggers to resume the sprint. It supports retry and reconciliation states to maintain consistent sprint state and a complete audit trail across execution attempts.

Can I modify acceptance criteria during contract-bound sprint execution?

Contract-bound sprint execution does not rewrite acceptance criteria or widen scope. It touches only files and artifacts explicitly listed in the approved contract, ensuring that any changes remain verifiable within the original contract boundaries.

What's the best way to produce reproducible runtime artifacts for sprint verification?

Provide an approved sprint contract and trigger generator-execution to produce a reproducible runtime and handoff. It generates runtime.md and handoff.md artifacts that document execution evidence for reviewer verification and clean sprint handoff.

Do I need an approved contract before starting sprint execution?

Sprint execution requires an approved contract from evaluator-contract-review or a reconciled state after a failed review. Without contract approval, execution cannot trigger, ensuring all changes remain bound to verified acceptance criteria.