What problem does it solve? Creating a new repository or adding components to an existing one often means hand-assembling files across Python, frontend, Terraform, Helm, container, and CI concerns, with risks of overwriting existing content or drifting from the approved architecture. This Skill converts an approved architecture into a path-owned scaffold plan and applies it only through a validated, digest-bound executor. ## Core Features & Use Cases - Path-ownership planning: Assigns exactly one specialist owner (python-project, frontend-project, container, terraform, helmchart, github-workflows, gitignore, shell-scripting) to every planned file and rejects collisions or unsupported artifacts. - Digest-bound guarded apply: Finalizes candidates into a private 0700 bundle, validates manifests and preconditions, and applies only after explicit approval of the exact bundle digest, with atomic no-replace publication and a crash-safe journal. - Brownfield-safe merges: Supports create, unchanged, and restricted semantic-merge operations for .gitignore, README.md, and Makefile without deleting or blindly overwriting existing content. - Use Case: After an app-stack decision approves a React/Vite frontend plus Python backend, invoke the skill to produce the full repository tree, review the operations and digest, then apply it with zero network, Git, or install side effects. ## Quick Start Ask the agent to run $scaffold-project to plan a new repository scaffold from your approved architecture, review the proposed tree and digest, then approve that exact digest to apply it.
