kanbanzai-documents

Name: kanbanzai-documents
Availability: InStock
Author: sambeau

Enforce document lifecycle gates for registration, approval, and supersession in Kanbanzai.

5|Updated Mar 18, 2026

Search Tags:#documents #drift #lifecycle #workflows #approval #registration #kanbanzai

Ready to run

npx skills add https://github.com/sambeau/kanbanzai --skill kanbanzai-documents

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: kanbanzai-documents
Source: https://github.com/sambeau/kanbanzai/tree/main/.agents/skills/kanbanzai-documents
Command: npx skills add https://github.com/sambeau/kanbanzai --skill kanbanzai-documents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Kanbanzai documents require disciplined lifecycle management across creation, registration, approval, drift monitoring, and lifecycle transitions. This skill provides a centralized policy for when and how documents are created, registered, approved, moved, superseded, or deleted, reducing orphaned or out-of-sync content.

Core Features & Use Cases

Enforces document types and lifecycle gates (design, specification, dev-plan, research, report, policy) within Kanbanzai.
Handles document registration, approval, drift detection, and content hash refresh.
Supports operations like supersession, move, and deletion of documents while preserving history.

Quick Start

Frequently Asked Questions about kanbanzai-documents

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

FAQPage Schema

How do I enforce document approval workflows in a Kanbanzai-managed project?▼

Document approval workflows are enforced by applying lifecycle types and registration gates to markdown files. Documents pass through defined approval steps before being formally registered, ensuring ownership and traceability throughout the project lifecycle.

What document lifecycle types are supported for markdown files in Kanbanzai?▼

Supported document lifecycle types include design, specification, dev-plan, research, report, and policy. These types dictate the specific registration, approval, and progression gates applied to markdown documents within configured project roots.

How do I handle document drift and content hash refresh for markdown specifications?▼

Document drift is handled by monitoring content hashes and triggering a refresh when markdown specifications fall out of sync. The skill detects content changes and updates the hash to maintain traceability and lifecycle integrity.

Can I supersede or delete design documents while preserving version history?▼

Yes, you can supersede, move, or delete design documents while preserving their history. The skill manages these lifecycle transitions to prevent orphaned content and maintain a traceable record of ownership and progression.

Do I need configured document roots to register markdown files for approval tracking?▼

Yes, configured document roots are required. Markdown documents must be created within these specified roots to be recognized by the system for type enforcement, registration, and approval gate tracking.