Problem
The README documents the manifest, but no "fork this and edit one file" path exists. The example/validation repos are the closest thing — but they're validation harnesses, not clean starters.
Proposed
Either:
- A
cascade init subcommand that scaffolds a working repo (manifest, callback skeletons for build + deploy, .github/CODEOWNERS, AWS OIDC role example, .github/manifest.yaml with cli_version pinned), OR
- A separate template repo wired with the same skeleton, marked "Template" in GH settings.
Scaffold should cover the two common shapes: no-env CLI/library and multi-env (dev → test → uat → prod).
Impact
First-adopter onboarding goes from "read 5 doc pages, reverse-engineer the test harness" to "run init, edit two values, push." Additive, zero schema risk — lands post-1.0.
Problem
The README documents the manifest, but no "fork this and edit one file" path exists. The example/validation repos are the closest thing — but they're validation harnesses, not clean starters.
Proposed
Either:
cascade initsubcommand that scaffolds a working repo (manifest, callback skeletons for build + deploy,.github/CODEOWNERS, AWS OIDC role example,.github/manifest.yamlwithcli_versionpinned), ORScaffold should cover the two common shapes: no-env CLI/library and multi-env (dev → test → uat → prod).
Impact
First-adopter onboarding goes from "read 5 doc pages, reverse-engineer the test harness" to "run init, edit two values, push." Additive, zero schema risk — lands post-1.0.