Project maintenance
Use this sub-skill when the user already has an Agent Starter Pack project and wants to modify, shrink, or upgrade it.
Covers
enhancefor templating Agent Starter Pack capabilities into an existing project.extractfor turning a scaffolded project into a minimal shareable agent.upgradefor merging a generated project forward to a newer ASP version.- Backup, version-lock, language-detection, metadata, and 3-way merge behavior that make those workflows safe.
Excludes
- Choosing a template for a brand-new project belongs in
project-scaffolding. - CI/CD provisioning, deployment, and Gemini Enterprise registration belong in
deployment-ops.
Read first
../../references/cli-reference.mdfor command ownership.../../references/package-overview.mdfor install and sanity-check guidance.references/workflows.mdfor the enhancement, extraction, and upgrade flows.references/troubleshooting.mdfor backup, merge, metadata, and version-lock failures.
Common workflow
- Determine whether the user is enhancing, extracting, or upgrading.
- Check the project metadata and current layout before changing anything.
- Use backups or dry-run modes when available.
- Prefer the merge logic already built into the package rather than inventing a custom file strategy.
- Hand off cloud-deployment questions to
deployment-opsafter the local project state is correct.
Useful signals
enhance,--base-template,--agent-directory,--dry-run,--prefer-new,--forceextract,--source,--force,--dry-runupgrade,asp_version,--dry-run,--auto-approve- backup, conflict, merge, metadata, or version-lock language
Validation mindset
- Do not assume every generated project uses the same language or directory layout.
- Treat missing metadata or version markers as a workflow problem that needs the maintenance reference, not as a template-selection issue.
- If the user only needs to understand the generated project’s deployment commands, route to
deployment-ops.


