Bump PromptPack Spec Version

Standardize PromptPack spec extension release checklists for version bumps.

6|Updated Oct 31, 2025
One-click install
npx skills add https://github.com/AltairaLabs/promptpack-spec --skill bump-promptpack-spec-version
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Bump PromptPack Spec Version
Source: https://github.com/AltairaLabs/promptpack-spec/tree/main
Command: npx skills add https://github.com/AltairaLabs/promptpack-spec --skill bump-promptpack-spec-version

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Keeps PromptPack spec extension releases from becoming chaotic by documenting every required update—from RFC creation through schema bumps to docs deployment—so maintainers never miss a step or forget to archive the previous version.

Core Features & Use Cases

  • RFC and schema orchestration: Copy the latest RFC template, set metadata, and update schema/promptpack.schema.json with the new version, descriptions, and $defs in lockstep.
  • Documentation propagation: Archive the prior version’s docs, refresh current spec and sidebar content, update shields/README summaries, and regenerate schema reference files while keeping the latest workflow, agents, and skills narratives intact.
  • Operational verification: Sync static schema assets, update RFC index and guides, run the docs build, and confirm the Docusaurus site reflects installment-specific highlights before tagging the release.

Quick Start

Follow the checklist to draft the RFC, bump schema and docs, archive the old version, sync static schema assets, and verify the docs build before tagging the new release.

Frequently Asked Questions about Bump PromptPack Spec Version

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

FAQPage Schema
How do I bump a PromptPack spec version without missing schema or docs updates?

To bump a PromptPack spec version safely, follow a standardized release checklist that orchestrates RFC creation, schema JSON updates, documentation archiving, and static asset syncing before tagging. This ensures every required update is completed in lockstep without missing steps.

What is the process for updating schema and Docusaurus docs during a spec extension release?

Spec extension release process involves copying the latest RFC template, updating promptpack.schema.json with new versions and $defs, archiving prior version docs, refreshing sidebar entries and README badges, then running the Docusaurus build to verify the site reflects installment-specific highlights.

Do I need to run a Docusaurus build when publishing a new PromptPack schema version?

Yes, running the Docusaurus build is required for operational verification. It confirms that the updated spec content, sidebar entries, and regenerated schema reference files are correctly deployed and reflect installment-specific highlights before you tag the final release.

How do I archive the previous version documentation when releasing a PromptPack spec update?

To archive previous version documentation during a PromptPack spec update, you move the prior version's docs into archived folders, update the RFC index and guides, then refresh the current spec content and sidebar entries to reflect the newly bumped version.

What documentation assets need refreshing when bumping a PromptPack spec version?

Documentation assets requiring refresh during a spec version bump include current spec content, sidebar entries, README badges and summaries, regenerated schema reference files, static schema copies, the RFC index, and workflow narratives to ensure consistent versioning across all files.