job-description-drafting

$npx mdskill add Significant-Gravitas/skills-catalog/job-description-drafting

Run this when the user needs a new posting written, an old one rewritten, or a posting screened for language before it goes live.

SKILL.md

.github/skills/job-description-draftingView on GitHub ↗
---
name: "job-description-drafting"
description: "Use when a job posting needs writing, an old one needs rewriting, or a posting needs a language check before it goes live."
triggers: ["write a job description", "rewrite this job posting", "check this JD for bias", "job post for the new role", "make this posting inclusive", "draft the req posting", "is this job ad any good"]
version: "1"
---

# Job description drafting

Run this when the user needs a new posting written, an old one rewritten, or a
posting screened for language before it goes live.

## Inputs

The role scorecard, the hiring manager's notes on the team and the work, and
the facts that must appear: title, level, location and work setup, pay band if
it is shareable, and how to apply.

## Structure every posting the same way

The mission in two sentences. What this person owns in the first 90 days. The
three to six must-haves as checkable outcomes. The labelled nice-to-haves.
What the team offers — scope, growth, pay band when given. A short
equal-opportunity close.

Pull the day-in-the-life lines verbatim from the intake conversation into the
posting, and set the baseline for it in plain words: who should apply and what
success looks like.

## Write requirements as outcomes, not pedigree

"Has shipped a service handling production traffic" beats "5+ years
experience". Cut degree demands and years-floors unless the hiring manager
defends them in one line.

## Screen the language

No gendered superlatives, no "rockstar" or "ninja", no laundry list of
nice-to-haves posing as requirements, no jargon a strong outsider would not
know. When you cut a line, say what you cut and why in one line.

## Never invent the numbers

Pay, title, and start date go in only as the user stated them. Do not guess a
salary range, and do not derive one from the company's size or funding. Mark
anything unconfirmed UNKNOWN rather than drafting around it.

## Output

The finished posting shown in chat, one round of edits, then a clean block
ready to paste into the applicant tracking system (ATS) or the careers page,
plus a one-line note on anything cut for language and anything still UNKNOWN.
Saved to the hiring folder.

## Fallbacks

With no scorecard, draft from the title plus the four intake questions and
mark it a draft pending calibration. With only an old posting, rewrite in
place and show a short before-and-after on the lines you changed.

## Approval gate

Drafts only. Never post a job, publish a req, or send a posting anywhere
without the owner's explicit yes for that specific action.

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.