Skip to content

abrahamferga/harness

v0.3.0MIT

Always-on control plane: what the Plenipo platform already gives you (so you never rebuild it), how any Plenipo product is run and proven, the workflow.json/settings.json pair, config + guardrail validation, and the conductor that drives the scout -> define -> shape -> deliver loops end to end. Keep enabled in every loop.

conduct

Drive one product from an idea to merged, runtime-proven code by sequencing the four loops — scout, define, shape, deliver — handing each phase off to its own slash command and refusing to advance until that phase's exit check passes. Owns the gates, the run journal, the budget and stagnation ceilings, and the autonomy level; it delegates every procedure instead of restating one. USE FOR: starting or resuming a full end-to-end run, deciding which phase comes next and whether the previous one actually finished, draining a GitHub backlog issue by issue under a budget. DO NOT USE FOR: doing a single phase's work (invoke that phase's command directly), or grading evidence in the abstract (loop-discipline).

License
MIT
Read SKILL.md at the source

Pinned to revision a2ee8094fc23, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.