plan-eng-review

Orchestrate engineering planning and architecture review workflows with ASCII diagrams.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill plan-eng-review-akiyoshi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-eng-review
Source: https://github.com/akiyoshi/gstack-copilot-jp/tree/main/.github/skills/plan-eng-review
Command: npx skills add https://github.com/akiyoshi/gstack-copilot-jp --skill plan-eng-review-akiyoshi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Engineering managers often struggle to coordinate comprehensive architecture reviews and design plans across teams. This Skill provides a structured workflow to surface risks, align on scope, and produce a clear plan before coding begins.

Core Features & Use Cases

  • ASCII diagrams for data flow and state transitions in design plans.
  • Step-by-step review process: Scope check, architecture review, code quality, tests, performance, and risk assessment.
  • Design doc generation prompts and artifact guidance to ensure consistent outputs.

Quick Start

Trigger a full ENG plan review by invoking the /plan-eng-review workflow and following the on-screen prompts.

Frequently Asked Questions about plan-eng-review

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

FAQPage Schema
How do I conduct an engineering plan review before coding begins?

An engineering plan review assesses scope, architecture, code quality, tests, and performance through a structured workflow. It enforces multi-section evaluations to surface risks and align teams on scope before implementation starts.

What is included in a system design review for architecture planning?

A system design review includes data flow visualization, risk identification, and test planning. It provides structured sections for scope checks, architecture reviews, and performance assessments, plus optional tension checks.

How do I visualize data flow and state transitions in a design doc?

Visualize data flow and state transitions in a design doc using ASCII diagrams. These diagrams illustrate plans and state transitions directly within the engineering review workflow artifacts.

Can I generate design doc artifacts during an architecture review?

Yes, generate design doc artifacts during an architecture review using built-in prompts and artifact guidance. The workflow ensures consistent outputs across comprehensive design assessments.

Does the engineering review workflow support outside opinions and tension checks?

Yes, the engineering review workflow supports optional outside opinions and tension checks. These sections augment the core review process, which covers scope, architecture, code quality, tests, and performance.

What is the best way to identify risks in a software engineering plan?

The best way to identify risks in a software engineering plan is to enforce a structured, multi-section review process. This approach evaluates scope, architecture, and performance to surface risks before coding begins.