spec-promote

Promote validated draft specs to active by moving directories and updating metadata.

1|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/srnnkls/tropos --skill spec-promote
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-promote
Source: https://github.com/srnnkls/tropos/tree/main/skills/spec-promote
Command: npx skills add https://github.com/srnnkls/tropos --skill spec-promote

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Promotes validated specs from draft to active stage for implementation.

Core Features & Use Cases

  • Validate readiness by inspecting validation.yaml for markers and gates, and review spec.md for required sections.
  • Move the spec directory from ./specs/draft/{spec-name} to ./specs/active/{spec-name}.
  • Update spec.md frontmatter to status Active, stage active, and set a promoted date, preserving existing metadata.
  • Report success and outline next steps for execution.

Quick Start

Promoting a validated draft spec to active by moving it under specs/active and updating its metadata.

Frequently Asked Questions about spec-promote

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

FAQPage Schema
How do I promote a draft spec to active status?

Promoting a draft spec to active requires reading validation.yaml for passing markers and gates, moving the directory from ./specs/draft/ to ./specs/active/, and updating spec.md frontmatter to status Active.

What validation is required before promoting a spec to active?

Spec promotion requires inspecting validation.yaml for passing markers and gates, and reviewing spec.md for required sections. These validation checks ensure the draft spec is ready for active implementation.

How does spec workflow promotion update metadata?

Spec promotion updates metadata by modifying spec.md frontmatter to status Active and stage active, while setting a promoted date. Existing metadata is preserved during the directory transition from draft to active.

Can I move a spec from draft to active if validation gates fail?

Spec promotion applies to workflows where validation passes or gates allow promotion. If validation.yaml indicates failing gates, the spec is not ready and should not be moved from draft to active.

What happens after promoting a spec to active?

After promoting a spec to active, the workflow reports success and outlines next steps for execution. The spec is moved under ./specs/active/ with updated frontmatter, ready for implementation.