skills.rest
agwacom
agwacomOFFICIAL
Explore all skills by this author →
GitHub

avad-plan-eng-review

Formalize engineering plan reviews validating architecture, data flow, risk, and test coverage.

Updated Mar 18, 2026
Search Tags:#architecture#engineering#code-quality#design-docs#plan-review#ascii-diagrams#testing-plan
One-click install
npx skills add https://github.com/agwacom/avadbot --skill avad-plan-eng-review
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: avad-plan-eng-review
Source: https://github.com/agwacom/avadbot/tree/main/skills/avad-plan-eng-review
Command: npx skills add https://github.com/agwacom/avadbot --skill avad-plan-eng-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineering teams lock in execution plans by performing a thorough review of architecture, data flows, edge cases, and test coverage before coding begins, providing opinionated recommendations and ensuring documentation and design intent stay aligned.

Core Features & Use Cases

  • Thorough architecture and data-flow review across systems to surface risks and gaps.
  • Opinionated recommendations that prioritize correctness, testability, and maintainability.
  • ASCII diagrams and design-doc checks to keep critical decisions visible and up-to-date.
  • Before-you-start guardrails: validate design docs, constraints, and alignment with project goals.

Quick Start

Run the eng-review workflow against the repository to generate an architecture-focused plan.

Frequently Asked Questions about avad-plan-eng-review

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

FAQPage Schema
What is an engineering plan review and when do I need one?▼

An engineering plan review validates architecture, data flow, risk, and test coverage before coding begins. You need this process when formalizing design docs to surface gaps and ensure documentation aligns with project goals.

How do I review a software architecture design doc before implementation?▼

Review a software architecture design doc by validating data flows, checking scope decisions, verifying ASCII diagram conventions, and ensuring test coverage plans are formalized to surface risks before execution starts.

Can I use ASCII diagrams to validate data flow in my engineering plan?▼

Yes, ASCII diagrams validate data flow by keeping critical architecture decisions visible and up-to-date. The review process codifies these diagram conventions to ensure consistent and reusable engineering checks.

Does this approach generate a testing plan as part of the design review?▼

Yes, this approach generates a test-plan artifact as part of the design review. It validates test coverage alongside architecture and constraints to provide opinionated recommendations prioritizing correctness and maintainability.

What is the best way to identify edge cases and risks in a software architecture?▼

The best way to identify edge cases is performing a thorough data-flow review across systems using opinionated guardrails. This validates constraints and scope decisions to surface risks before coding begins.

Related Skills

Explore More Software Engineering Skills→
cshyangcshyang

gsd:workflow:discovery-phase

Plan and execute a project discovery phase to define requirements and scope.

Community
Intermediate
sennett-lausennett-lau

plan-eng-review

Review engineering plans for architecture, data flows, edge cases, and test coverage.

Community
Advanced
knckknckknckknck

go-style-guide

Standardize Go code quality and style across projects.

Community
Intermediate
ai-enhanced-engineerai-enhanced-engineer
3

arch-diagrams

Visualize software architectures and dependencies with Mermaid and ASCII diagrams.

Official
Intermediate