skills.rest
DavidLam-oss
DavidLam-ossCOMMUNITY
Explore all skills by this author →
GitHub

openprd-diagram-review

Generate architectural and product flow diagrams with review checklists.

283|45|Updated Jan 25, 2026
Search Tags:#architecture#visualization#review#diagram#product-flow#openprd
One-click install
npx skills add https://github.com/DavidLam-oss/obsidian-wechat-converter --skill openprd-diagram-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openprd-diagram-review
Source: https://github.com/DavidLam-oss/obsidian-wechat-converter/tree/main/.claude/skills/openprd-diagram-review
Command: npx skills add https://github.com/DavidLam-oss/obsidian-wechat-converter --skill openprd-diagram-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the communication gap in product development by providing a structured way to generate and review architecture diagrams, product flows, and explanation visuals, ensuring alignment before final implementation.

Core Features & Use Cases

  • Visual Clarity: Create explanation SVGs to clarify complex relationships, state transitions, or system boundaries.
  • Structured Review: Generate formal diagram contracts for architecture and product flows that include review checklists and summary cards.
  • Use Case: When a team is debating a new system architecture, use this Skill to generate a visual contract that highlights components, dependencies, and potential risks for stakeholder sign-off.

Quick Start

Use the openprd-diagram-review skill to generate a product flow diagram for the user onboarding process.

Frequently Asked Questions about openprd-diagram-review

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

FAQPage Schema
How do I generate an architecture diagram for stakeholder review?▼

This Skill generates architecture diagrams for stakeholder review by creating formal visual contracts that highlight components, dependencies, and risks for sign-off.

What is the best way to visualize a product flow for user onboarding?▼

Visualizing a product flow for user onboarding is done by generating structured diagrams that map state transitions and system boundaries to clarify relationships before implementation.

Can I create explanation SVGs for complex system boundaries and state transitions?▼

Yes, you can create explanation SVGs to clarify complex relationships, state transitions, or system boundaries, ensuring team alignment on architectural constraints.

Does diagram generation include a review checklist for technical documentation?▼

Diagram generation includes a review checklist for technical documentation by producing formal diagram contracts that integrate summary cards and language-specific labeling requirements.

When do I need a formal visual contract for product flow architecture?▼

You need a formal visual contract for product flow architecture when a team is debating a new system design and requires structured alignment on components and dependencies before implementation.

What are the limitations of using automated diagrams for user journey mapping?▼

Automated diagrams for user journey mapping are limited by the input details provided, requiring clear architectural descriptions to accurately facilitate stakeholder alignment and technical review.

Related Skills

Explore More Product & Management Skills→
686f6c61686f6c61
105

architecture-docs

Generate architectural documentation with Mermaid diagrams for software systems.

Community
Intermediate
launchapp-devlaunchapp-dev
38

design-review-process

Codify a four-gate design review process with criteria, checklists, and approvals.

Official
Advanced
noloodnolood

solution-design

Transform task models into implementation designs with iterative user review.

Community
Advanced
coolguy1771coolguy1771

architecture-diagrams

Generate system architecture diagrams using Mermaid and PlantUML code.

Community
Intermediate