Feature: user-level setup skill should bootstrap repo-local SDLC skills

[BaseInfinity]

Problem

Codex SDLC has a useful distribution shape: a user-level $setup-wizard can be installed once, then used to bootstrap repo-local lifecycle assets such as local skills, hooks, docs, and manifests.

That split is clean:

• global setup is always available wherever the agent starts
• repo-local /sdlc stays versioned with the project
• repo-local update/check flows can preserve project-specific customizations
• projects can compose SDLC with other local lifecycle skills without baking everything into one global command

Claude SDLC currently has repo-local setup/update/sdlc/feedback skills as part of the generated project suite. That works, but first-run setup and ongoing repo workflow are bundled into the same local surface.

Proposal

Add or document a Claude equivalent bootstrap model:

• user-level/global Claude setup-wizard bootstrapper
• setup installs or updates repo-local Claude skills/hooks/docs
• repo-local /sdlc remains the canonical implementation workflow
• repo-local /update-wizard handles maintenance after setup
• decide whether /feedback should be user-level, repo-local, or both

Design Questions

• Should setup-wizard be user-level only after install, or also copied repo-local for auditability/offline use?
• Should feedback be global because it targets the upstream wizard, or repo-local because it benefits from installed metadata and customization context?
• Should update-wizard stay repo-local because it operates on project files and manifests?
• How should npm/plugin install flows map to user-level vs repo-local skills?
• What migration path preserves the existing repo-local install behavior?

Why

• Matches the cleaner mental model: global bootstrap -> local lifecycle skills.
• Keeps /sdlc repo-specific and easy to compose with other local project workflows.
• Makes first-time setup easier: install once, run setup anywhere.
• Preserves project-local skill versioning for implementation and update behavior.
• Creates a clearer Claude/Codex adapter architecture without forcing every command to have the same scope.

Acceptance Criteria

• Document intended skill scopes for setup, sdlc, update, and feedback.
• Update install/update docs to explain the bootstrap model.
• Add tests or fixtures proving global setup can install the repo-local skill suite.
• Preserve the current repo-local install path as a compatible fallback or migration path.