From pm-hr
Write a clear, inclusive, and structured job description for any role. Use when asked to write a job description, job posting, JD, or job advert. Produces a complete JD with role summary, responsibilities, requirements, and inclusive language review.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-hr:job-description-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes complete, inclusive job descriptions that attract the right candidates and reduce bias in the hiring process.
Writes complete, inclusive job descriptions that attract the right candidates and reduce bias in the hiring process.
[Company] | [Location] | [Remote policy] | [Salary range]
About [Company] [2-3 sentences. Specific and honest — not marketing copy.]
The Role [3-4 sentences. What this person will own, why the role exists now, what success looks like in year one.]
What You Will Do [6-8 bullet points. Outcomes and responsibilities, not activities. Start each with an action verb. Most important first.]
What We Are Looking For
Must have (4-6 items only):
Nice to have (3-4 items):
What We Offer [Compensation, benefits, development. Be specific.]
How to Apply [Clear instructions. What to send, where, timeline.]
Words to remove or replace:
| Original | Replace with | Why |
|---|---|---|
| "rockstar" | "experienced" | Gendered connotation |
| "ninja" | "skilled" | Same issue |
| "must have degree" | "relevant experience or qualification" | Excludes qualified non-graduates |
Requirement audit:
npx claudepluginhub thoniorf/pm-claude-skills --plugin pm-hrGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.
2plugins reuse this skill
First indexed Jul 8, 2026