kb-promote

Promote specification lifecycle statuses with assertion-gated validation and GOV-12 test enforcement.

2|1|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-promote-remaker-digital
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb-promote
Source: https://github.com/Remaker-Digital/groundtruth-kb/tree/main/.claude/skills/kb-promote
Command: npx skills add https://github.com/Remaker-Digital/groundtruth-kb --skill kb-promote-remaker-digital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents premature advancement of a specification’s lifecycle by requiring assertion-gated validation and proof that implementation and verification criteria are actually met.

Core Features & Use Cases

  • Lifecycle-safe promotion: Advances status along specified → implemented → verified (or any → retired) only after the required checks pass.
  • GOV-12 assertion and test enforcement: Blocks promotion when there are no linked non-stale tests for the spec, helping ensure evidence exists before moving forward.
  • Assertion run recording: Captures an assertion run outcome and results for auditability during the promotion transition.
  • Use Case: When you complete work for a given SPEC, you can promote it confidently only after code evidence, assertions, and the correct testing/verification signals are present.

Quick Start

Run kb-promote to promote SPEC-1803 to implemented once you have linked non-stale tests and all assertions are expected to pass.

Frequently Asked Questions about kb-promote

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

FAQPage Schema
How do I gate spec promotion with assertions to prevent premature lifecycle advancement?

Spec promotion gating blocks a specification's lifecycle transition until assertion-gated validation passes, ensuring implementation and verification criteria are fully met before advancing status.

What is GOV-12 assertion enforcement for specification lifecycle transitions?

GOV-12 assertion enforcement blocks specification promotion when no linked non-stale tests exist, ensuring code evidence and verification signals are present before moving from specified to implemented to verified.

How to promote a specification status from specified to implemented to verified?

Run kb-promote after linking non-stale tests and ensuring all assertions pass; the tool validates GOV-12 conditions, performs the status transition, and records assertion run results for auditability.

Do I need linked non-stale tests to advance a specification's lifecycle status?

Yes, linked non-stale tests are required for spec promotion. The GOV-12 check blocks any lifecycle transition when no evidence of implementation or verification testing exists for the specification.

Why does spec promotion fail when assertion validation does not pass?

Spec promotion fails when assertion-gated validation checks do not pass because the tool prevents premature advancement by requiring proof that implementation and verification criteria are actually met.

Can I retire a specification without passing all assertion checks?

The tool supports retiring specs with owner approval, applying lifecycle transition logic that records assertion run results while enforcing governance rules appropriate to the retired status path.