project-scaffold

Two jobs, one plugin.

Start a repo well. A router inspects the directory, asks at most two questions, and names exactly one of: scaffold an empty directory into a full local skeleton (CLAUDE.md hierarchy, Makefile, pre-commit config, README, .gitignore, first commit); generate a CLAUDE.md hierarchy for a repo that already has code; survey a repo for the architectural decisions its code already encodes and propose a docs/adr/ set, writing nothing until you approve; or audit and repair a repo's own Claude Code configuration.

Run a POC honestly. poc-start writes the contract — the question, the falsifiable success signal, the kill criteria, the time box, the target runtime. poc-validate is a read-only check of the POC against that contract, reporting met, unmet or unmeasurable per criterion. poc-graduate closes it out: promote to a real project on the runtime chosen at the start, or kill it and record why. A read-only poc-guardian subagent reviews proposed plans against the contract and returns approved, blocked, or needs-evidence.

Everything is stack-neutral and forge-neutral. It never creates a remote repository, pushes, or opens a pull request — project-new stops at the first local commit, and forge operations belong to github-workflow.