harness
Skill1 starsChanged 6 months agoMITView on GitHub
Build an engineering delivery harness for AI-assisted work: decompose business goals into multi-level steps, route each step to prompt, AgentSkill, Dify workflow, RPA, code, manual human intervention, or external tool, and define automatic checkpoints, retry strategy, escalation paths, evidence gates, and acceptance criteria. Use before implementing, auditing, or operationalizing a complex workflow.
36 other projects use a version of this.
Adopted by
Most recently taken up by
- DavidTeam2008/harness-engineering-kittheir own version, first seen Nov 15, 2026
- manhquydev/flow-skilltheir own version, first seen Nov 13, 2026
- hanzhangzzz/agent-skills-zhtheir own version, first seen Oct 29, 2026
- anlmalabs/skillstheir own version, first seen Oct 25, 2026
- gutomec/nirvana-os-enginetheir own version, first seen Oct 13, 2026
- es6kr/skillstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use retro, verify and 3 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
Microsoft AzureSkillverify
End-to-end app testing pipeline for browser-based web apps on cloud browsers via Azure Playwright Workspaces: verify the live app, author tests for working flows, heal failing tests, then re-run with video and produce one consolidated report. Three phases (app verification, test authoring, test healing) plus a scoped final sanity run; each phase emits a sub-report. Use when asked to "verify my app", "make sure my app works and has good test coverage", "do a full QA pass", "add tests where I'm missing coverage", "fix failing tests and add new ones", "smoke test before deploy", "QA my deployment", or any combined verify-and-test ask. Requires Azure CLI (`az login`) and a Playwright Workspace resource ID — bootstraps configs on first invocation. Browser-based web apps with Playwright only — not for unit/API tests, native mobile/desktop, load/perf, or full accessibility audits.
Also in 3 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 projects that use this
GoogleSkillgrill-me
A relentless interview to sharpen a plan or design.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 3 projects that use this
Other versions36 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 36
- revfactory/harness★ 9.1ksame name
- cexll/myclaude★ 2.8ksame name
- Simpleyyt/ai-manus★ 1.6ksame name
- BankrBot/skills★ 1.2ksame name
- BankrBot/openclaw-skills★ 1.2ksame name
- bam-bam-2/solo-skills★ 366same name
- serejaris/personal-corp-os★ 244same name
- serejaris/ris-claude-code★ 243same name
- SensorsIot/Embedded-AI-Harness★ 235same name
- skillsynchq/txcript★ 208same name
26 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository11 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .cursor/rules/audit-live-workbench.mdcCursor rule
- accept-fiveSkill
- agent-diagnoseSkill
- ai-product-auditSkill
- auditSkill
- deploy-checkSkill
- flow-testSkill
- physical-flow-testSkill
- skill-studySkill
- visual-qaSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 24 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Use this skill to turn a messy business objective into an executable delivery harness.
- Distinctive: line 23
Start from the business process, not from the tool.
- Distinctive: line 29
Keep source evidence, live evidence, tool evidence, and human decisions separate.
- Very specific: line 44
If the goal is to convert a manual business process into a process agent, also use references/process-agent-pattern.md.
- Distinctive: line 63
Add retry and escalation
- Distinctive: line 65
Never retry destructive actions blindly.
- Very specific: line 73
Run /audit for overall readiness.
- Very specific: line 74
Run /flow-test for user-visible workflows.
- Very specific: line 75
Run /deploy-check for production dependencies.
- Very specific: line 76
Run /accept-five for important workflows.
- Distinctive: line 129
No checkpoint between AI output and real-world action.
“Common” is measured: kept by at least 6 in 10 of the 24 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Harness
Use this skill to turn a messy business objective into an executable delivery harness.
The goal is to prevent AI work from becoming one giant prompt. Break the work into business stages, substeps, execution units, checkpoints, retries, and human decision points.
business objective -> stage tree -> execution router -> checkpoints -> retries/escalations -> acceptance harnessCore Rules
- Start from the business process, not from the tool.
- Decompose in layers until each unit has one clear owner, input, output, tool mode, checkpoint, and retry rule.
- Route each unit to the right execution mode: prompt, AgentSkill, Dify workflow, RPA, code task, manual human decision, or external system.
- Insert automatic checkpoints after every unit that can fail silently.
- Insert human checkpoints where judgment, permissions, money, private data, or irreversible actions appear.
- Define retry limits and escalation paths before execution.
- Keep source evidence, live evidence, tool evidence, and human decisions separate.
- Feed final outputs into
/audit,/flow-test,/deploy-check, or/accept-fivefor verification.
Workflow
- Scope the objective
- Name the business goal.
- Identify user/customer, operator, system, and decision owner.
- Define done, blocked, and out-of-scope.
- Build the stage tree
- Split into business stages.
- Split each stage into substeps.
- Continue until each unit is small enough to execute and verify independently.
- Use
references/business-decomposition.md. - If the goal is to convert a manual business process into a process agent, also use
references/process-agent-pattern.md.
- Route execution modes
- Choose the lightest reliable mode for each unit:
PROMPT: one-off reasoning or drafting.SKILL: repeatable agent workflow.DIFY: structured multi-step LLM workflow, API chain, or business automation.RPA: brittle UI-only workflow with no API or direct integration.CODE: deterministic transform, parser, test, or integration.HUMAN: judgment, approval, credential entry, payment, legal, brand, or safety decision.EXTERNAL: SaaS/API/platform action outside the agent.
- Use
references/execution-router.md.
- Choose the lightest reliable mode for each unit:
- Add checkpoints
- Define automatic checkpoint after each unit.
- Define human checkpoint before irreversible, private, paid, or high-judgment actions.
- Each checkpoint needs expected evidence, pass/fail condition, and owner.
- For process agents, add a signal ledger and iteration loop: collect signals, diagnose root cause, test change, verify reduction.
- Add retry and escalation
- Define retryable failures, retry count, backoff, fallback mode, and escalation owner.
- Never retry destructive actions blindly.
- Use
references/checkpoint-retry-policy.md.
- Output the harness
- Produce stage tree, execution matrix, checkpoint table, retry table, human-intervention map, risk register, and acceptance handoff.
- For process-agent work, also produce lifecycle and signal/iteration tables.
- Verify the harness
- Run
/auditfor overall readiness. - Run
/flow-testfor user-visible workflows. - Run
/deploy-checkfor production dependencies. - Run
/accept-fivefor important workflows.
- Run
Output Format
## Harness Summary
- Business goal:
- Scope:
- Done:
- Out of scope:
- Main risk:
## Stage Tree
| Level | Stage | Step | Input | Output | Owner | Dependency |
| --- | --- | --- | --- | --- | --- | --- |
## Execution Matrix
| Step | Mode | Why this mode | Tool/Skill/Workflow | Evidence | Fallback |
| --- | --- | --- | --- | --- | --- |
## Checkpoints
| Step | Checkpoint | Automatic/Human | Pass condition | Fail condition | Evidence | Owner |
| --- | --- | --- | --- | --- | --- | --- |
## Retry And Escalation
| Failure | Retryable | Retry limit | Backoff/Fallback | Human escalation | Stop condition |
| --- | --- | --- | --- | --- | --- |
## Acceptance Handoff
| Target | Next skill | What to verify |
| --- | --- | --- |
## Process Agent Lifecycle
| Stage | Business Question | Output | Checkpoint | Owner |
| --- | --- | --- | --- | --- |
## Signal And Iteration Loop
| Signal | Root Cause | Change Tried | Verification | Result |
| --- | --- | --- | --- | --- |Anti-Patterns
- One giant prompt for a multi-stage business process.
- Choosing Dify, RPA, or skills before mapping the business steps.
- No checkpoint between AI output and real-world action.
- Retrying the same bad prompt without changing input, context, or mode.
- Building a process agent before defining the business flow and data templates.
- Optimizing symptoms instead of diagnosing root causes from repeated signals.
- Treating RPA as robust when an API or deterministic code path exists.
- Letting the agent approve its own high-risk action.
- Hiding manual steps instead of marking them as human checkpoints.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

