phase-8-review

Name: phase-8-review
Availability: InStock
Author: solitasroh

Identify architecture and convention mismatches across MCU/MPU/WPF projects.

2|1|Updated Mar 22, 2026

Search Tags:#architecture #conventions #quality-assurance #code-review #gap-analysis #pdca

Ready to run

npx skills add https://github.com/solitasroh/mcukit --skill phase-8-review-solitasroh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: phase-8-review
Source: https://github.com/solitasroh/mcukit/tree/main/skills/phase-8-review
Command: npx skills add https://github.com/solitasroh/mcukit --skill phase-8-review-solitasroh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Phase 8: Architecture/Convention Review consolidates quality gates by validating the codebase against defined architecture rules, conventions, and cross-phase dependencies to surface gaps early.

Core Features & Use Cases

Architecture validation and convention compliance checks across MCU/MPU/WPF projects.
Gap analysis and reporting to guide refactoring plans and risk mitigation.
Deliverables include structured artifacts (architecture-review.md, convention-review.md, refactoring-plan.md) for stakeholder alignment.

Quick Start

Start Phase 8 review on your project to perform architecture and convention checks and generate a gap-analysis plan.

Frequently Asked Questions about phase-8-review

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

FAQPage Schema

How do I perform an architecture review and convention validation on MCU or WPF projects?▼

Architecture review validates completed implementations against defined rules using gap analysis to surface mismatches. It checks convention compliance across MCU, MPU, and WPF projects to improve code quality before release by identifying structural violations early.

What is gap analysis in code review and when do I need it?▼

Gap analysis identifies discrepancies between your codebase and defined architecture rules or conventions. You need it before release to catch convention mismatches, guide refactoring plans, and ensure cross-phase traceability across your embedded or desktop software projects.

Can I generate a refactoring plan from architecture validation results?▼

Yes, architecture validation generates structured artifacts including refactoring-plan.md. This document captures identified convention mismatches and architecture gaps, providing stakeholder alignment and a structured remediation plan to mitigate risks before release.

Does the architecture health check support cross-phase traceability for embedded systems?▼

Yes, the architecture health check supports cross-phase traceability across MCU, MPU, and WPF projects. It validates cross-phase dependencies to ensure completed implementations align with defined architecture rules and convention standards before release.

What deliverables should I expect from a code quality and convention compliance check?▼

Convention compliance checks produce structured markdown artifacts: architecture-review.md, convention-review.md, and refactoring-plan.md. These deliverables document identified gaps, validate rules, and guide remediation planning for stakeholder alignment.