design-review-notes

Extract decisions, action items, and required changes from design review transcripts.

Updated Apr 10, 2026

Search Tags:#decisions #notes #traceability #actions #meetings #design-review

Ready to run

npx skills add https://github.com/ramybarsoum/RStack-V0 --skill design-review-notes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: design-review-notes
Source: https://github.com/ramybarsoum/RStack-V0/tree/main/skill/design-review-notes
Command: npx skills add https://github.com/ramybarsoum/RStack-V0 --skill design-review-notes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture and structure notes from tech design review meetings with decisions, action items, and required changes.

Core Features & Use Cases

Structured capture: automatically tag decisions, actions, and changes from design discussions.
Link to artifacts: connect notes to design documents, PRs, and tickets.
Searchable knowledge: generate summaries and follow-ups from past reviews.

Quick Start

Paste the design review notes to capture decisions, actions, and required changes.

Frequently Asked Questions about design-review-notes

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

FAQPage Schema

How do I extract decisions and action items from a design review transcript?▼

Capture design review decisions by pasting the transcript into the skill, which automatically extracts decisions, action items, and required changes, then saves them to a structured markdown file.

How do I structure design review notes with owners and due dates?▼

Structure design review notes by processing the transcript through the skill, which identifies required changes and organizes them into a markdown file with dedicated sections for decisions, owners, due dates, and follow-ups.

Can I link design review notes to existing artifacts like PRs and tickets?▼

Yes, the skill connects captured notes to design documents, PRs, and tickets, preserving traceability across design artifacts to maintain a searchable knowledge base of past reviews.

What is the best way to maintain traceability across design artifacts after a meeting?▼

Maintain traceability across design artifacts by using the skill to validate input quality and connect extracted decisions, actions, and required changes directly to their related design documents, PRs, and tickets.

Does this tool require a specific meeting transcript format to capture design actions?▼

The skill does not require a specific meeting transcript format; it validates the input quality of pasted design review notes and extracts decisions, actions, and changes to generate a structured markdown file.

Where are the extracted design decisions and follow-ups saved?▼

Extracted design decisions and follow-ups are saved to a structured markdown file at work/analyses/[design]-design-notes.md, organizing decisions, owners, due dates, and follow-ups for searchable knowledge.