agentleFS
SafetyMPSafetyMP/HR-ERP/.cursor/skills/hr-product-gate/SKILL.md

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.

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
  1. Very specific:

    Verify brief under docs/product/feature-briefs/ or spike ADR exists.

    line 30
  2. Distinctive:

    Use standard HR terms (paystub, earnings statement, headcount — not invented jargon).

    line 33

≈ “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 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

  1. Read references/operating-model.md.
  2. Verify brief under docs/product/feature-briefs/ or spike ADR exists.
  3. Confirm PO gate: user, pain, outcome, scope boundary filled.
  4. Emit PO checkpoint (≤6 lines) before Architecture.
  5. Use standard HR terms (paystub, earnings statement, headcount — not invented jargon).
  6. 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

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.