role-intake-and-job-description

$npx mdskill add Significant-Gravitas/skills-catalog/role-intake-and-job-description

Use this before publishing or revising a role.

SKILL.md

.github/skills/role-intake-and-job-descriptionView on GitHub ↗
---
name: "role-intake-and-job-description"
description: "Turn a hiring need into a plain job description based on outcomes, job-related evidence, and approved terms."
triggers: ["write job description", "role intake", "open a role", "job posting", "hiring brief"]
version: "1"
---

# Role intake and job description

Use this before publishing or revising a role.

## Intake

Get the reason for the hire, outcomes due in the first 30, 60, and 90 days, recurring work, decisions the role owns, manager, team, location, working hours, travel, approved level, approved pay range, and required legal text. For each requirement, ask what work would fail without it.

Sort requirements into:

- must show before hire;
- can be tested in the process;
- can be learned after hire;
- preference with no clear link to the work.

Remove the last group unless the hiring manager gives a job-related reason.

## Draft

Write the outcome first, then five to eight duties, then required evidence, useful experience, reporting line, work terms, process, and approved pay or benefits. Use plain verbs. Do not use inflated titles, personality labels, coded language, or a long tool list where a skill would do.

## Review checks

Show every fact whose approval is missing. Flag requirements that may screen people out without a stated work need, but do not give employment-law advice. Route policy or legal questions to the company's people lead or counsel.

## Output

Return the intake brief, the job-description draft, removed or changed requirements with reasons, and an approval checklist. Do not publish it.

More from Significant-Gravitas/skills-catalog

SkillDescription
account-health-and-qbrsUse when a support account wobbles or a quarterly business review looms: read the health signals, run the success plan, and prep the review from evidence.
accounts-receivable-follow-upReview open receivables and draft factual, staged payment follow-ups without inventing status or contacting a customer.
ad-copy-variantsWrite ad variants that each test one idea, within platform limits and supported claims.
alex-getting-startedUse on the first conversation with Alex, or whenever their memory has no product preferences yet: learn what the user is building and who for, where specs, roadmap and numbers live, who decides dates and scope, and get them to a first real product deliverable.
alliance-co-commercializationUse when a strategic alliance needs joint selling governance: operating model, joint targeting, steering prep, and milestone accountability.
anika-getting-startedUse on the first conversation with Anika, or whenever their memory has no partnership preferences yet: learn which partners and alliances the user owns, what motion they run, and get one real partner read on screen in the same session.
assure-partner-led-deliveryUse when partners deliver client work in your name: own the in-flight book, run the weekly delivery review, and rescue engagements before clients feel it.
automate-finance-reportingUse to connect a number source, map an export into the finance ledger, or QA a sheet: the column mapping, the dedupe key, the load summary, and the checks that must pass before a read ships.
billing-refunds-and-exceptionsUse when money is on the table: verify the charge, check the policy, and stage a refund or exception draft that stops at the owner's yes.
board-and-investor-metrics-briefPrepare a concise board or investor metrics brief with definitions, sources, comparisons, drivers, risks, and decisions needed.