agentleFS
SafetyMPSafetyMP/HR-ERP/.cursor/skills/hr-human-collaboration/SKILL.md

hr-human-collaboration

Skill1 starsChanged 6 months agoApache-2.0View on GitHub

Collaboration plane (Harness HITL) — seven-phase human-agent loop: proposal, options, human tradeoffs, execute, revalidate, specialized tools, output review. Use at T1+ before specialized skills; load routing portion automatically at orchestration.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Timeout: never auto-approve revalidation.

    line 42

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

HR human collaboration (Collaboration plane)

Use when

  • Orchestrating T1+ work (Orchestrator step 0)
  • Presenting strategy options with risk/reward tradeoffs
  • Recording human decisions before specialized skills or Task delegation
  • Phase 7 output review against approved strategy

Do not use when

  • T0 docs-only chore (step 1 chore N/A)
  • Product employment-AI runtime actions — use Product HITL (lib/governance/hitl.ts)

Seven-phase checklist

PhaseModeAction
1 ProposalHOTLRestate intent, tier, bounded contexts
2 OptionsHOTL≥2 strategies with risk, reward, rollback, lanes
3 Human inputHITLRecord principal + timestamp; routing skills only
4 ExecuteHOTLImplement approved plan
5 RevalidateHOTLDrift check; human confirms before phase 6
6 SpecializedHITLTasks, MCP, @hr-regulated-domain, etc.
7 Output reviewHOTLVerifier confirms deliverables match chosenStrategy

Protocols

  • Reject at 3 or 5: return to phase 2; append rejectionHistory[]
  • Timeout: never auto-approve revalidation; deny specialized unlock or escalate to Human PO
  • Challenge: human edits plan sections or alternate chosenStrategy

Anti-patterns

  • Prompt-only “ask user first” without hook/manifest gate
  • Loading specialized skills before phase 6 / revalidation
  • Timeout-as-approval
  • Rubber-stamping options without reading rollback column

Resources

  • references/collaboration-loop.md
  • specs/templates/collaboration-plan.md
  • ADR 0020

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.