onboarding

I almost copied a skill folder into every repository. The healthier shape turned out to be one onboarding door and tiny consumer footprints.

TL;DR: Instead of copying the skill to every repo, it stays centralized and consumers keep only light config and templates. This avoids maintenance debt since fixes happen once, while staying cheap because Claude Code only loads skill details when used. An offline helper handles scaffolding safely and idempotently, while online work runs through Plane's MCP tools.