dharma-eng-review

Name: dharma-eng-review
Availability: InStock
Author: AIKAGRYA

Reviews architecture, interfaces, failure modes, and test plans before implementation begins.

1|3|Updated Mar 9, 2026

Search Tags:#refactoring #data flow #design review #engineering management #architecture review #test plan #failure modes

Ready to run

npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-eng-review-aikagrya

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: dharma-eng-review
Source: https://github.com/AIKAGRYA/dharma_swarm/tree/main/mode_pack/claude/eng-review
Command: npx skills add https://github.com/AIKAGRYA/dharma_swarm --skill dharma-eng-review-aikagrya

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often jump into implementation without locking down architecture, leading to over-engineering, unclear interfaces, and missing test coverage. This Skill enforces an engineering-manager review pass that maps the system before code is written. ## Core Features & Use Cases - Architecture Mapping: Produces an architecture map, data flow diagram, and trust boundary analysis for the planned work. - Failure Mode Analysis: Identifies failure modes and calls out both over-engineering and under-engineering. - Test Planning: Delivers a concrete test plan and a minimal-diff recommendation before implementation starts. - Use Case: After product direction is set for a new feature, run this review to lock the minimal viable architecture, then hand off to implementation and later to a preflight review. ## Quick Start Ask the assistant to run an engineering review of the proposed feature, covering architecture, data flow, failure modes, and a test plan.

Frequently Asked Questions about dharma-eng-review

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

FAQPage Schema

How do I review software architecture before implementation?▼

Run an engineering review that maps the architecture, data flow, trust boundaries, and failure modes, then produces a test plan and minimal-diff recommendation. Implementation should not start until this review is complete.

What should an engineering design review include?▼

A design review should include an architecture map, data flow, failure modes, a test plan, and a minimal-diff recommendation. It should also call out over-engineering and under-engineering and name what should be deferred.

When should I run an architecture review in the development workflow?▼

Run it after product direction is set and before implementation or major refactoring begins. After implementation, hand off to a preflight review step.

How do I avoid over-engineering a new feature?▼

Prefer explicit designs over clever ones and choose the fewest moving parts that solve the problem. A structured review that names what should be deferred helps keep scope minimal.

What are the limitations of a pre-implementation design review?▼

A design review validates plans, not running code, so it cannot catch runtime defects or integration bugs. It must be followed by implementation and a post-implementation preflight review for full coverage.