role-redesign-for-ai
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
npx skills add mohitagw15856/pm-claude-skills --skill role-redesign-for-ai --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Role Redesign For AI Skill When AI absorbs 40% of a role's tasks, orgs default to the worst option: say nothing, and let expectations quietly inflate until the human is doing their old job *plus* supervising the machine, evaluated by standards from neither. This skill makes the redesign explicit — what the role stops doing, what it now owns, and what "good" means after the shift. ## What This Skill Produces - A **task inventory, before/after**: what AI took, what it created, what stayed human — with hours - The **redefined core**: the role's new centre of gravity, written as a charter - **New expectations & metrics**: what performance means now (and which old metrics are dead) - **Level and growth-path implications** — including the junior-pipeline problem, faced honestly ## Required Inputs Ask for (if not already provided): - **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 h
- What This Skill Produces
- Required Inputs
- Redesign Method
- Output Format
- Role Redesign: [title] — post-AI charter
- Quality Checks
- Anti-Patterns
What does the role-redesign-for-ai skill do?
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
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill role-redesign-for-ai --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.