skills.rest
VanLengs
VanLengsCOMMUNITY
Explore all skills by this author →
GitHub

promote

Finalize plugin production manifests and archive design docs for ship cycles.

1|Updated Mar 27, 2026
Search Tags:#workflow#versioning#plugin#archive#software-engineering#design-docs#promote
One-click install
npx skills add https://github.com/VanLengs/astra-studio-plugins --skill promote-vanlengs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/VanLengs/astra-studio-plugins/tree/main/studio-core/skills/promote
Command: npx skills add https://github.com/VanLengs/astra-studio-plugins --skill promote-vanlengs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promote a validated plugin to production by finalizing the manifest and snapshotting design documents, enabling continuous iteration.

Core Features & Use Cases

  • Finalize the production manifest at {target_dir}/.claude-plugin/plugin.json by applying the draft, bumping the version, and wiring in optional components (commands, hooks, mcp) as available.
  • Snapshot design documents from studio/changes to the archive for traceable iteration history and set the active workspace to the next iteration.
  • Validate prerequisites and perform the promotion workflow to prepare for the next ship cycle.

Quick Start

Run the promote command for the selected plugin to finalize its manifest and snapshot design docs.

Frequently Asked Questions about promote

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I finalize a plugin manifest for production release?▼

To finalize a plugin manifest, apply the draft changes to plugin.json, bump the shipped version, and wire in optional components like commands, hooks, and mcp resources to complete the promotion workflow.

What is the best way to archive design docs during a software release cycle?▼

Archiving design docs during a release cycle involves snapshotting files from the studio/changes workspace to an archive directory, ensuring traceable iteration history before setting the active workspace to the next iteration.

How do I bump plugin versions and update status fields for a shipped release?▼

Bumping plugin versions and updating status fields requires reading the draft manifest, applying changes to the production plugin.json, and setting fields like shipped_version, last_shipped_at, and archive_path.

Do I need specific workspace directories to promote a plugin milestone?▼

Yes, promoting a plugin milestone requires specific workspace directories to exist, including the target directory for the production manifest and the studio/changes directory containing the draft file.

Why does promoting a plugin snapshot design workspaces?▼

Promoting a plugin snapshots design workspaces to store a traceable record of iteration history, enabling continuous development by setting the active workspace to the next iteration cycle.

Can I wire optional components like hooks and mcp into a plugin manifest during promotion?▼

Yes, the promotion workflow wires optional components such as commands, hooks, and mcp into the production plugin.json manifest as available, finalizing the plugin configuration for the ship cycle.

Related Skills

Explore More Software Engineering Skills→
Ameng2001Ameng2001
1

promote

Finalize production plugin manifests and archive approved design workspaces.

Community
Intermediate
malinskibeniaminmalinskibeniamin
3

swarm

Coordinate parallel task execution across lanes with workspace policies and merged results.

Community
Advanced
nsalvacaonsalvacao

plugin-anatomy

Inspect and scaffold Claude Code plugins with canonical directory layout and frontmatter.

Community
Advanced
justincordovajustincordova
1

sync-docs

Scan recent code changes and merge design decisions into SPEC.md.

Community
Intermediate