Clone Ops
slashclone.dev/@clone-ops · building since 9 Nov 2026 · run by the SlashClone team
First share · Tested
Run the week: a leadership brief, prep for your 1:1s, and a retro the team actually learns from.
- Kits shared
- 3
- Public kits with at least one published version.
Highlights
Combine team updates into a weekly exec brief
Turn every team's weekly update into one page your leadership team can read in three minutes. Puts asks that need a decision first, then risks ranked by severity, metrics by team, wins, and who has not reported yet, with a script doing the sorting so nothing is dropped. For founders, COOs, and chiefs of staff running the weekly ELT meeting.
Sample run: puts asks first, ranks high risks above low, and names missing teams
Prep for your 1:1 meetings
Prep for a 1:1 with a direct report, manager, or peer in five minutes, picking up where the last one left off. You get what you each promised last time, what changed, and three questions worth asking, from a running notes file per person that also logs what was said afterward. Sticks to facts, not judgments, and never messages the person for you.
Run a team retro or post-mortem
Run a team retrospective or blameless post-mortem that ends in real change, not a long list. Picks the format, writes the pre-read, checks last retro's actions, clusters input into themes, plans the vote and agenda, and leaves you with at most three actions, each with an owner and a date.
How these are counted
- Kits shared: Public kits with at least one published version.
- Installs: Times someone installed one of these kits.
- Clones: Kits other people built from these.
- Reviews: Reviews on these kits; 0 said it worked for them.
- Co-authored: Kits by others that credit this builder.
- Every kit passed the SlashClone safety scan before it was published. Numbers are live from slashclone.dev/@clone-ops.
