promote-spec

Move a draft spec to ready via branch and pull request.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/jsnbuchanan/claude-code-spec-skills-example --skill promote-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote-spec
Source: https://github.com/jsnbuchanan/claude-code-spec-skills-example/tree/main/.claude/skills/promote-spec
Command: npx skills add https://github.com/jsnbuchanan/claude-code-spec-skills-example --skill promote-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Moves a draft spec from vault/specs/draft/ to vault/specs/ready/, wrapped in a branch + PR for traceability.

Core Features & Use Cases

  • Creates a dedicated branch and moves vault/specs/draft/{slug}/ to vault/specs/ready/{slug}/
  • Opens a review PR and gates the merge until explicit confirmation, ensuring traceability
  • Maintains spec lifecycle integrity by avoiding content edits during promotion

Quick Start

Promote the most recent draft spec to ready by invoking the promote-spec skill with an optional slug argument.

Frequently Asked Questions about promote-spec

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

FAQPage Schema
How do I move a draft spec to ready using a git branch and pull request?

To promote a draft spec to ready, this workflow creates a dedicated git branch, moves the spec directory, and opens a pull request. The merge is gated until explicit confirmation, ensuring traceability and formal readiness before implementation.

What is the best way to gate spec readiness before implementation begins?

Spec readiness gating is enforced by wrapping the directory move in a branch and pull request. The merge gate blocks the spec from entering the ready state until an explicit confirmation is provided, satisfying formal workflow gating requirements.

Can I edit spec content during the promotion process?

Editing spec content during promotion is not supported. The workflow maintains spec lifecycle integrity by strictly moving the draft directory to the ready directory without applying content modifications, ensuring the reviewed draft matches the promoted version.

Do I need a specific repository structure to use spec promotion?

Yes, spec promotion requires a specific repository structure. The workflow expects draft specs to reside in vault/specs/draft and moves them to vault/specs/ready, meaning these exact directory paths must exist for the promotion to function.

Why does my spec promotion require a pull request instead of a direct commit?

A pull request is required for spec promotion to ensure traceability and auditability. Wrapping the directory move in a PR provides a reviewable record of the readiness change and applies a final merge gate before the spec is officially promoted.