kanbanzai-design

Draft and review structured design documents for Kanbanzai projects.

5|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/sambeau/kanbanzai --skill kanbanzai-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kanbanzai-design
Source: https://github.com/sambeau/kanbanzai/tree/main/internal/kbzinit/skills/design
Command: npx skills add https://github.com/sambeau/kanbanzai --skill kanbanzai-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill guides the design process from an agreed scope to an approved design document, helping human decision-makers think through design choices, compare alternatives, and prepare for approval.

Core Features & Use Cases

  • Structured design workflows: draft, review, and finalize design documents with rationale and trade-offs.
  • Open questions management: surface unresolved decisions and track risks.
  • Alignment with Kanbanzai workflows: integrates with planning, workflow, and documentation practices to ensure consistency.

Quick Start

Draft a complete design document with alternatives and rationale once the scope is agreed.

Frequently Asked Questions about kanbanzai-design

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

FAQPage Schema
How do I draft a structured design document when project scope is unclear?

To draft a structured design document when scope is unclear, you can use guided workflows to define boundaries, explore technology or data-model directions, and surface unresolved questions for review.

What is the best way to compare architectural alternatives during a design review?

Comparing architectural alternatives during a design review is best handled by documenting each option with explicit trade-offs, rationale, and associated risks to guide human decision-makers toward an approved direction.

How do I manage open questions and risks in an architecture design document?

Managing open questions in an architecture design document involves explicitly listing unresolved decisions, tracking their associated risks, and aligning the outcomes with project workflows to ensure consistency.

Can I use this for data-model decisions or is it only for software architecture?

Yes, you can use this for data-model decisions. It applies to architectural, technology, or data-model choices whenever a design direction is needed and helps produce a complete design with a single chosen path.

When do I need a formal design document with rationale for my project?

You need a formal design document with rationale when scope is agreed but a clear design direction is missing, or during design reviews with the human design manager to secure formal approval and alignment.