design-preview

Review implementation designs for DDD and test-driven scenarios before coding.

2|1|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/is-ivanov/rpm-ddd --skill design-preview
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design-preview
Source: https://github.com/is-ivanov/rpm-ddd/tree/main/.opencode/skills/design-preview
Command: npx skills add https://github.com/is-ivanov/rpm-ddd --skill design-preview

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate an implementation approach before writing tests or production code, reducing rework when a scenario's design is unclear or potentially contentious.

Core Features & Use Cases

  • Pre-implementation design review: Gathers story requirements, scenario details, load expectations, existing code, ADRs, and acceptance tests to form a grounded design proposal.
  • Right-sized design output: Produces concise summaries for simple scenarios and richer artifacts such as method signatures, pseudocode, domain model changes, and flow descriptions for complex scenarios.
  • Approval-driven workflow: Captures user approval, supports ADR creation when needed, and escalates rejected designs to a broader architecture discussion.
  • Use Case: Before implementing a new filtering scenario in a DDD codebase, use this Skill to present the planned domain changes and port updates so stakeholders can approve the approach early.

Quick Start

Ask the AI to run the design-preview skill for your current story and scenario so it can summarize the planned design before any tests are written.

Frequently Asked Questions about design-preview

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

FAQPage Schema
How do I review an implementation design before writing code or tests?

Pre-implementation design review gathers story requirements, scenario details, load expectations, existing code, and ADRs to produce an approval-oriented design proposal without generating code. This validates the approach early, reducing rework when a scenario's design is contentious.

What is the best way to align on domain changes in a DDD workflow before coding?

Aligning on domain changes in a DDD workflow requires previewing planned port updates and model modifications against acceptance behavior and ADR constraints. This produces a grounded design proposal for stakeholder approval before any test-driven development begins.

Can I use a design preview for test-driven development scenarios?

Yes, design preview applies directly to test-driven workflows by analyzing scenario specifications and load assumptions to form a design proposal. It ensures acceptance behavior and domain changes are reviewed and approved before tests are written.

How do I handle rejected implementation designs during scenario planning?

Rejected implementation designs during scenario planning are escalated to a broader architecture discussion. The approval-driven workflow captures user approval and supports creating ADRs when needed, ensuring contentious design approaches are properly reviewed.

Does design preview work for simple scenarios or only complex domain changes?

Design preview works for both simple and complex scenarios. It produces concise summaries for straightforward scenarios and richer artifacts like method signatures, pseudocode, and flow descriptions for complex domain model changes requiring detailed review.

What inputs do I need for a pre-implementation design review?

Pre-implementation design review requires reading specification documents, existing code structure, load assumptions, ADR constraints, and progress tracking rules. These inputs form a grounded design proposal aligned with acceptance behavior and domain requirements.