kanbanzai-specification

Name: kanbanzai-specification
Availability: InStock
Author: sambeau

Draft testable specifications with acceptance criteria from approved designs.

5|Updated Mar 18, 2026

Search Tags:#workflow #specification #quality-assurance #acceptance-criteria #design-review #stakeholder-alignment

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating an approved design into a clear, testable specification that can drive development and testing, ensuring alignment between stakeholders and the build.

Core Features & Use Cases

Scope definition: distills design into a concise, testable set of acceptance criteria.
Ambiguity resolution: flags open questions and reduces interpretation drift.
Traceability: ensures every criterion traces back to the approved design.
Use Case: a product owner uses this to finalize what must be built before development begins.

Quick Start

Draft a concise, testable specification from the current design and share it for approval.

Frequently Asked Questions about kanbanzai-specification

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

FAQPage Schema

How do I write testable acceptance criteria from an approved design?▼

To write testable acceptance criteria, distill the approved design into a concise, independent specification that covers edge cases and ambiguities while remaining free of implementation details. This ensures alignment between stakeholders before development begins.

What is the best way to resolve ambiguities when translating a design into a specification?▼

Resolving ambiguities requires flagging open questions during the transition from design to development plan. The specification process enforces a single direction by identifying interpretation drift and requiring human approval before the build starts.

How do I draft a development specification that keeps stakeholders aligned?▼

Draft a development specification that ensures traceability by linking every acceptance criterion back to the approved design. Sharing this concise specification for human approval finalizes what must be built and maintains stakeholder alignment.

Does a project specification need to include implementation details?▼

A project specification must be terse, independent, and free of implementation details. It focuses strictly on defining scope and testable acceptance criteria to guide development and quality assurance without dictating the code structure.

Can I use this specification process for quality assurance planning?▼

Yes, this specification process supports quality assurance by producing a testable set of acceptance criteria. QA teams use these precise specs to verify that the finalized build matches the approved design and handles defined edge cases.

When do I need to draft a specification from a design?▼

You need to draft a specification during the transition from design to development plan. It is required when a product owner needs to finalize what must be built, resolving open questions and enforcing a single direction before coding starts.