<< All versions

Skill v1.0.1

currentAutomated scan100/100
maicongambini/omp-harness-guide/harness-role-separation

+1 new

──Details
PublishedNovember 5, 2026 at 11:45 AM
Content Hashsha256:1cd12a8509f1b7af...
Git SHA504e1fc7fdf7
Bump Typepatch
Compare with v1.0.0
──Files
Files (1 file, 2.2 KB)
SKILL.md2.2 KBactive
SKILL.md · 62 lines · 2.2 KB

name: harness-role-separation description: "Separate planner, generator, and evaluator roles. Use when handling complex, UI-heavy, or subjective tasks. Do NOT use for scheduling parallel lanes (use orchestrate)." metadata: version: "1.0.1"


Harness Role Separation

Use when a task is complex, has subjective outcomes, touches UI, or where self-review would miss defects.

When to Use

  • Task involves UI/visual design decisions
  • Task spans multiple files or subsystems
  • Prior similar tasks had quality drift or missed requirements
  • Task is high-risk (auth, data integrity, public API)
  • Single-role approach produced incomplete output before

Role Definitions

Planner: Defines scope, writes sprint contract, defines AC, does NOT write implementation. Generator: Implements ONLY what is in sprint contract scope. No scope expansion. Evaluator: Judges against sprint contract AC using harness-evaluator-rubric. Does NOT self-approve.

In OpenCode, one agent can play all three roles — but sequentially, with explicit role transitions.

Workflow

1. Planner Phase

Fill docs/harness/sprint-contract.md before writing any code:

  • Sprint Overview: what and why
  • Scope In: explicit list of what will change
  • Scope Out: explicit list of what will NOT change
  • Roles: planner / generator / evaluator
  • Acceptance Criteria: observable, runnable
  • Verification Plan: commands + pass conditions
  • Evidence Log: leave empty, fill during/after Execute

State: "Planner complete. Switching to Generator role."

2. Generator Phase

Implement ONLY sprint contract scope:

  • If you discover adjacent work → add to feature_list.json as not_started. Do not implement now.
  • If scope must change → stop, update sprint contract, get approval, then continue.

State: "Generator complete. Switching to Evaluator role."

3. Evaluator Phase

Invoke harness-evaluator-rubric. Do not produce verdict in same response as implementation. Fill Evidence Log in sprint contract with actual command output. Record revision log entry if any rework was needed.

Revision Log Pattern

[timestamp] Revision 1: [what changed] | Reason: [why] | AC affected: [which]
← v1.0.0All versions