agentleFS
Sign inStart free
martincjarvismartincjarvis/development-skills/skills/best-practice-introduction/SKILL.md

best-practice-introduction

Skill4 starsChanged 10 months agoMITView on GitHub

Use when introducing new standards, tooling, practices, or asking for adoption/rollout guidance. Produces phased rollout plan with adoption criteria, risk assessment, and rollback triggers.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Opt-out: Document in docs/practice-decisions.md

    line 22

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Best Practice Introduction

Overview

P2 Change Management - Phased rollout with pilot validation. Rollback defined upfront.

REQUIRED: superpowers:brainstorming, superpowers:verification-before-completion

When to Use

  • Introducing new standards, tooling, or practices
  • Rolling out team-wide process changes
  • Adopting architectural patterns or quality gates
  • Opt-out: Document in docs/practice-decisions.md

Core Workflow

  1. Announce skill and identify practice being introduced
  2. Define phased rollout plan (minimum 2 phases):
    • Pilot/validation phase (volunteers or smallest scope)
    • Broader adoption phase(s) with escalating enforcement
  3. For each phase specify: scope, enforcement level, duration, success criteria
  4. Define rollback criteria (productivity, adoption, technical triggers)
  5. Define communication plan (announcement, feedback, updates)
  6. Track in docs/practice-rollout.md

See Rollout Patterns for strategies.

Quick Reference

Practice TypeStrategyPilot Scope
Linting/ToolingOpt-in pilot1-2 volunteer teams
ArchitectureComponent-by-typeNewest/smallest
Security (urgent)Immediate + baselineAll, baseline exceptions
Process changeTeam-by-teamWilling early adopters

Red Flags - STOP

  • "Apply everywhere immediately"
  • "No time for pilot"
  • "Already paid for it"
  • "Mandate is non-negotiable"
  • "Team must adapt"

All mean: Apply phased approach or document explicit skip.

See Rationalizations for detailed rebuttals.

Evidence Checklist

  • Phased rollout plan defined (minimum 2 phases)
  • Each phase has scope, enforcement level, duration, success criteria
  • Rollback criteria defined
  • Communication plan included
  • Success metrics defined
  • Adoption support specified (docs, training, office hours)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free