/groundwork: a skill that makes any repo runnable from a fresh clone

A recurring problem in many organisations I've worked in is that a project is set up by a few developers, and from then on they are "the project's devs". Later, one leaves, another goes on holiday and the last is off ill for the day. This is the bus factor in action. Then a ticket comes in. Another developer on the team clones the repo and discovers: They don't have the .env file. They don't have a database. They have the code, but none of the very specific, undocumented things needed to actually run the project locally. Configuration that lives on one person's laptop isn't configuration, it's folklore (the Twelve-Factor App has been telling us to keep it explicit for years). Introducing /groundwork So I created /groundwork, a skill that finds those gaps and fixes them. Principally, it reviews your repo (or several repos) for anything that stops someone running it locally. It doesn't just read the README, it walks the path of a new joiner for real, in a fresh copy of the repo without…