issue-review-design

Review design documents against generic software design principles.

12|1|Updated Dec 27, 2025
One-click install
npx skills add https://github.com/apokamo/kaji --skill issue-review-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-review-design
Source: https://github.com/apokamo/kaji/tree/main/.claude/skills/issue-review-design
Command: npx skills add https://github.com/apokamo/kaji --skill issue-review-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews design documents to verify they meet generic software design principles, ensuring clarity about What to build, constraints, and user experience without relying on implementation details.

Core Features & Use Cases

  • Gate-check style review to identify missing primary information (requirements, constraints, UX) before implementation.
  • Guidance on aligning design documents with referenced sources and best practices.
  • Issue-driven design validation that surfaces gaps and actionable fixes for the design team.

Quick Start

Submit the design document to kaji to start the review process.

Frequently Asked Questions about issue-review-design

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

FAQPage Schema
How do I review a software design document before implementation?

To review a software design document, submit it to validate requirements, constraints, and user experience against generic software design principles. This gate-check process identifies missing primary information and ensures abstraction and interface design are addressed before development begins.

What is a gate-check design review for software architecture?

A gate-check design review is a pre-implementation validation process that assesses software architecture documents for quality. It verifies alignment with primary sources and best practices, ensuring reliability, testability, and documentation alignment are properly addressed before development proceeds.

How do I validate if my design document covers all necessary constraints?

You validate design document constraints by applying an issue-driven review that surfaces gaps in requirements, user experience, and architectural limitations. This process ensures your design aligns with referenced sources and provides actionable fixes for the design team to implement.

Can I assess abstraction and interface design quality without implementation details?

Yes, you can assess abstraction and interface design quality without implementation details by reviewing the document against generic software design principles. This approach focuses on validating the conceptual architecture, reliability, and testability rather than specific code-level execution.

What is the best way to ensure testability and reliability in software design documents?

The best way to ensure testability and reliability is to conduct a rigorous design review that checks for documentation alignment and adherence to software architecture principles. This validation surfaces gaps early, providing actionable fixes to improve overall design quality.

When do I need a design review for my software architecture?

You need a design review during the pre-implementation phase to validate that your software architecture meets quality standards. This gate-check ensures your design documents address requirements, constraints, user experience, and testability before committing to development resources.