Redesign a job role that AI now does a large part of — deliberately, instead of quietly expecting the same headcount to absorb 140% output. Use when AI has changed what a role spends time on, when writing a revised role charter or job description post-AI, when a team asks 'what is my job now', or when planning capacity after AI adoption. Produces a role redesign: the task inventory before/after, the redefined core of the role, new expectations and metrics, and the growth-path implications. For hiring rubrics use hiring-rubric; for org-wide skills planning use ai-upskilling or career-ladder-map.
▸The role today — title, level, the real task list (or the JD plus what the JD lies about)
▸What AI actually absorbed — observed, not vendor-promised: which tasks, how completely, with what verification burden
▸The person / team context — one person or a team of eight? tenure mix? current performance framework?
▸The org's honest intent — same headcount doing more? fewer people? higher-value work? (The redesign differs; refusing to pick is itself the problem — flag it.)
✅ The bar it holds itself to
Every skill in this library self-verifies — these are this skill's own quality checks, straight from its definition.
✓The AI-created work (verification, supervision) appears in the inventory with hours
✓Freed capacity is explicitly allocated — no silent 140% expectation
✓At least one legacy throughput metric is explicitly killed
✓The "no longer does" list is concrete enough that someone could stop doing those things tomorrow
✓The junior-pipeline question is answered, not deferred
✓The org's intent (headcount vs scope) is stated in the document
⚠️ What it refuses to do
Do not redesign the role without the people in it — a charter discovered in a reorg deck creates the resistance it deserved
Do not keep old throughput metrics "for continuity" — they now measure the vendor, not the human
Do not treat verification as slack time — reviewing machine output at quality is skilled work with hours
Do not write "focus on higher-value work" without naming the work — that phrase is where redesigns go to die
Do not skip the intent question — a redesign that won't say whether headcount changes will be read as concealing it, correctly
Install
npx pm-claude-skills add --agent claude # or codex · cursor · gemini · hermes
# or one-line MCP (every skill, any client):
claude mcp add pm-skills -- npx -y pm-claude-skills-mcp