Generate design documents with problem, design, alternatives, and decisions sections.
npx skills add https://github.com/sambeau/kanbanzai --skill write-design-sambeau
Please help me install this Agent Skill. Skill: write-design Source: https://github.com/sambeau/kanbanzai/tree/main/.kbz/skills/write-design Command: npx skills add https://github.com/sambeau/kanbanzai --skill write-design-sambeau
The skill addresses the need for disciplined, repeatable design documentation to capture problems, proposed designs, alternatives, and decisions, ensuring clear traceability across features.
Draft a design document that outlines the problem, proposed approach, evaluated alternatives, and decisions in the required four-section structure.
High-intent search queries and answers about installing and using this skill.
An architectural decision record (ADR) captures design rationale, alternatives, and trade-offs. You need one for feature design and system architecture tasks to ensure traceability and disciplined documentation of decisions across a project.
To write a design document, draft four sections: Problem and Motivation, Design, Alternatives Considered, and Decisions. This structure enforces frontmatter metadata and traces architectural decisions, ensuring clear rationale for system architecture tasks.
Yes, the design document format applies to system architecture tasks within Kanbanzai and similar projects. It enforces a required four-section structure and frontmatter conventions that support reuse and auditing of design decisions across various features.
The best way to structure a design document for traceability is using four sections: Problem and Motivation, Design, Alternatives Considered, and Decisions. This enforces frontmatter and related work conventions to aid corpus alignment and review.
Your design document needs frontmatter and related work conventions to aid corpus alignment and review. These conventions enforce required structure and metadata, supporting the reuse and auditing of architectural decisions across features.
You should avoid a structured four-section design document when a task lacks significant trade-offs or architectural decisions. The format is designed for feature design and system architecture tasks requiring disciplined documentation of alternatives and rationale.
IcekoleGuide PRD creation through user interviews, codebase analysis, and module design.
h4vzzGenerates formatted technical documentation from code, design documents, or API schemas.
harnessprotocolManage Kanban tasks with MCP tools for creation, updates, and workflow moves.
cescrafliCapture architectural decisions as structured ADR documents with context and alternatives.
