adopt-ai-properly
Workflow recipe — the org-side AI adoption arc, policy to proof, by chaining 4 skills.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/mohitagw15856/pm-claude-skills/HEAD/commands/adopt-ai-properly.md -o ~/.claude/commands/adopt-ai-properly.mdadopt-ai-properly.md
Run the **Adopt AI Properly** workflow recipe for: $ARGUMENTS This is a *chain* of skills. Run each stage in order and **carry every stage's output forward as context** for the next. Open with a one-line plan of the 4 stages, then ask once for essential missing inputs (regulatory exposure, current tool spend, which roles AI has changed most, the review framework in use). Don't re-ask between stages. Run each stage under a clear `## Stage N — <name>` heading: 1. **Set the rules** — apply the `ai-usage-policy` skill: the one-page policy with the data traffic-light (grounded in this org's real data classes), approved tools, disclosure lines, and the decision log for counsel. 2. **Redesign the roles** — apply the `role-redesign-for-ai` skill to the role(s) AI changed most: the before/after task inventory with verification counted as work, capacity deliberately reallocated, and the junior-ladder answer — consistent with the policy from stage 1. 3. **Fix the reviews** — apply the `ai-assisted-performance-review` skill: criteria that measure judgment, verification, outcomes, and leverage; calibration rules for uneven adoption; the three hard-case scripts — aligned to the charters from stage 2. 4. **Prove what paid** — apply the `ai-roi-audit` skill across the tool spend: per-tool verdicts with the measurement method behind each number, the hidden-cost ledger, and baseline plans for the unknowns. Close with a **leadership one-pager**: the policy headline, the role changes, the new review frame, and the renewal decisions — the packet that turns "we should figure out AI" into four signed-off documents.
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.