Scan repository code, history, and config to scaffold a .goodplan/ project.
npx skills add https://github.com/ian97531/goodplan --skill onboard-repo
Please help me install this Agent Skill. Skill: onboard-repo Source: https://github.com/ian97531/goodplan/tree/main/skills/onboard-repo Command: npx skills add https://github.com/ian97531/goodplan --skill onboard-repo
Scan an existing repo with code but no .goodplan/ directory and scaffold a complete goodplan project. It extracts conventions, architecture, subsystem maturity, migrations, tech debt, and expertise from repo artifacts (README, git history, config files, gh CLI). Only asks about things that can't be inferred. Not for repos that already have .goodplan/ (use /migrate) or new projects without code (use /create-epic).
Run onboard this repo to begin scanning code and scaffolding a .goodplan/ directory.
High-intent search queries and answers about installing and using this skill.
To scaffold a project from an existing repo, this Skill scans your code, git history, and config files to infer conventions and architecture, then generates a complete .goodplan/ directory with actionable onboarding metadata.
Yes, architecture extraction and subsystem structure detection work by analyzing repo artifacts like README files, git history, and config files to identify maturity signals and generate a cohesive project scaffold.
Repo onboarding requires goodplan version 1.0.0 or higher, running pre-flight checks before scanning code and scaffolding the .goodplan directory to ensure compatibility.
You should not use repo scanning if the repository already contains a .goodplan/ directory, or if it is a new project without code, as this tool is built exclusively for existing codebases lacking prior scaffolding.
Migration and tech debt analysis detects patterns by scanning repository artifacts to identify structural debt and migration needs, then presents actionable guidance for planning improvements and future work.
Onboarding a repo scaffolds a new .goodplan directory from raw code artifacts, while migration is for repos that already have a .goodplan directory and need updating rather than initial extraction.
einja-incAutomate @einja/cli package builds, tests, versioning, tagging, changelog notes, and GitHub publishing with enforced checks using pnpm, npm, and gh tools.
clostaunauGenerate standardized SDLC learning repository structures with artifact templates and validation.
marcusgollAutomate epic scoping through structured questioning to populate epic-spec.md.
zb-ssGenerate project-specific SKILL.md files from git commit history.
