hr-product-gate
Skill1 starsChanged 6 months agoApache-2.0View on GitHub
Gates HR ERP product work: Feature briefs, UAC, friction checks (~10s employee pay tasks), standard HR terminology. Use when scoping features, writing UAC, reviewing HR/payroll UX, or before engineering starts a new capability.
In this repository37 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/agent-ai-governance.mdcCursor rule
- .cursor/rules/agent-architecture.mdcCursor rule
- .cursor/rules/agent-code-health.mdcCursor rule
- .cursor/rules/agent-db-migration-state.mdcCursor rule
- .cursor/rules/agent-developer-advocate.mdcCursor rule
- .cursor/rules/agent-devops-lifecycle.mdcCursor rule
- .cursor/rules/agent-finops.mdcCursor rule
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/agent-legal-hr-compliance.mdcCursor rule
- .cursor/rules/agent-mlops.mdcCursor rule
- .cursor/rules/agent-nextjs.mdcCursor rule
- .cursor/rules/agent-packaging-supply-chain.mdcCursor rule
- .cursor/rules/agent-qa.mdcCursor rule
- .cursor/rules/agent-security.mdcCursor rule
- .cursor/rules/orchestrator-hr-erp.mdcCursor rule
- .cursor/rules/repo-boundaries.mdcCursor rule
- .cursor/rules/site-contract.mdcCursor rule
- .cursor/rules/vercel-jwt-smoke.mdcCursor rule
- llms.txtllms.txt
- hr-contributor-handoffSkill
- hr-data-custodySkill
- hr-devops-lifecycleSkill
- hr-domain-boundariesSkill
- hr-foundation-governanceSkill
- hr-governance-learningSkill
- hr-human-collaborationSkill
- hr-orchestration-lanesSkill
- hr-product-mcp-governanceSkill
- hr-quality-labSkill
- hr-regulated-domainSkill
- hr-swarm-governanceSkill
- site-deliverySkill
- code-reviewSkill
- hr-data-custodySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 30
Verify brief under docs/product/feature-briefs/ or spike ADR exists.
- Distinctive: line 33
Use standard HR terms (paystub, earnings statement, headcount — not invented jargon).
≈ “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.
Files
HR product gate
Use this skill when
- Starting a new capability (Orchestrator step 1)
- Writing or reviewing Feature briefs and UAC
- QA derives tests from acceptance criteria
- Scope, persona, or friction checks are in play
Do not use this skill when
- T0 docs-only chore with
step 1 chore N/A - Pure infra with no user-visible outcome (still may need brief/spike ADR)
Instructions
- Read references/operating-model.md.
- Verify brief under
docs/product/feature-briefs/or spike ADR exists. - Confirm PO gate: user, pain, outcome, scope boundary filled.
- Emit PO checkpoint (≤6 lines) before Architecture.
- Use standard HR terms (paystub, earnings statement, headcount — not invented jargon).
- Value delivery hook (T1+) — When the brief ships this cycle, note S&OP cycle ID and point to
specs/templates/value-delivery-record.md; defer supply/reconcile to@devops-product-lifecycle.
Resources
- references/operating-model.md
- docs/product/feature-brief-template.md
- docs/product/stakeholder-value-plan.md §3 — demand priorities
Limitations
- Product gate only — not implementation or legal advice
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.

