agentleFS
jp-solumhealthjp-solumhealth/jpstack/team-feedback/SKILL.md

team-feedback

Skill0 starsChanged 18 days agoMITView on GitHub

Format feedback for the Solum platform team — new rules (eligibility, insurance, copay), bug reports, and feature requests — using the WHEN/THEN/Example framework with Trading Partner IDs. Use this skill when the user wants to send feedback to the team or eng, report a platform bug, request a rule change, write a feature request, or convert raw clinic feedback into implementable rules. Triggers: "feedback for the team", "write this up for eng", "report this to the team", "new rule for the platform", "feature request", "convert this into a rule", "regla para la plataforma", or when the user pastes raw clinic feedback about eligibility, insurance, or copay behavior that needs to go to engineering.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    NOT for: strategy discussions, prose emails, customer-facing messages

    line 28
  2. Distinctive:

    Add new mappings here as they come up.

    line 98

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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

Team Feedback — WHEN/THEN/Example Framework

Overview

Feedback to the platform team must be implementable without a single clarifying question: explicit condition + explicit behavior + evidence.

Core principle: write the condition as the error you SEE, never the cause you assume. "If MCO fails" forces eng to investigate what an MCO is; "el check automático da failed" does not.

When to Use

  • New platform rules (eligibility, insurance, copay behavior)
  • Bug reports
  • Feature requests
  • NOT for: strategy discussions, prose emails, customer-facing messages

The Output Contract

The message consists of, in order:

  1. One template block per rule (below)
  2. Optionally, ONE line starting with Nota: flagging a concern for eng to consider

Nothing else. No intro paragraphs, no root-cause analysis, no recommendations to "investigate first" — the rule as observed is the deliverable; a concern is one Nota: line.

WHEN (condición):
Insurance = [Trading Partner ID] ([nombre])
Y [el error/estado que se ve en la plataforma]

THEN (comportamiento):
[acción concreta]

Ejemplo (evidencia):
[clínica], paciente/check [ID]

Rules

  1. Insurance = Trading Partner ID, always. The TPID is the same across all clinics; display names are not. Name goes in parentheses for readability only. If the TPID is unknown, ask the user — never guess or substitute the name.
  2. Condition = observed error/state, exactly as seen in the platform UI (e.g., "el check automático da failed", "la insurance tiene más de un copay").
  3. THEN = one concrete action the platform should take (retry with X, choose Y, allow Z).
  4. Evidence required: clinic + patient ID or check ID. If missing, ask for it.
  5. Feature requests state the behavior, never a question or timeline ask: "Cuando los usuarios crean un Prior Auth, permitir agregar modifiers a los CPT codes."
  6. Language: match the user's draft language (team usually writes Spanish); keep WHEN/THEN keywords as-is.
  7. Output as plain copy-paste-ready text — no markdown formatting in the message itself.

Example: Before → After

Raw feedback:

"if MCO fails, run with straight Medicaid. [Clinic A]: 00000000-0000-0000-0000-000000000001"

Formatted:

WHEN (condición):
Insurance = 68049 (Peach State Health Plan)
Y el check automático da failed

THEN (comportamiento):
Reintentar el check con Insurance = QBZJV

Ejemplo (evidencia):
[Clinic A], paciente 00000000-0000-0000-0000-000000000001

Example: Non-Insurance Rule (Copays)

WHEN (condición):
La insurance tiene más de un copay

THEN (comportamiento):
Elegir el copay cuyo mensaje contenga "freestanding"

Ejemplo (evidencia):
[Clinic B], check 00000000-0000-0000-0000-000000000002

Known Trading Partner IDs

PayerTPIDNotes
Peach State Health Plan (GA Medicaid MCO)68049On failed check → retry with QBZJV
Georgia straight MedicaidQBZJVFallback payer for 68049

Add new mappings here as they come up.

Common Mistakes

MistakeFix
Insurance referenced by name onlyAlways TPID; name in parentheses
Condition written as assumed cause ("if MCO fails")Condition = visible error ("el check da failed")
Root-cause essay or pushback instead of the ruleTemplate block + at most one Nota: line
Feature request as a question or timeline askState the behavior: "Cuando [acción], [comportamiento]"
No evidenceClinic + patient/check ID, always

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.

Reviews can't be read right now.

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.