---
title: "engineering-process-demo"
description: "Demonstrates how Agent Plugins 1.0 can package a reusable software architecture review procedure as a portable engineering capability."
canonical: https://agentpluginsdirectory.com/plugins/engineering-process-demo
last-updated: 2026-10-02
---

# engineering-process-demo
Demonstrates how Agent Plugins 1.0 can package a reusable software architecture review procedure as a portable engineering capability.
- Slug: engineering-process-demo
- Publisher: Suyog Joshi
- Repository: https://github.com/suyog19/agent-plugins-engineering-process-demo
- Manifest: plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): code-review
- Skills: 1 (architecture-review)
- MCP servers: 0
- Stars: 0
- Repository created: 2026-08-17
- Repository last pushed: 2026-08-24
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/engineering-process-demo
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What engineering-process-demo does, in the publisher's words

A small, concrete demonstration of the idea that an engineering procedure can be packaged as a portable, versioned agent capability.

This repository is itself an Agent Plugins 1.0 package. It contains one portable Agent Skill, architecture-review, plus a deliberately small demo application with repository-local architecture rules.

The point is the separation:

- The plugin packages the reusable engineering procedure.
- The repository supplies the architecture and change-specific context.
- reads the local architecture rules before judging the change,
- ties findings to exact code evidence,
- identifies violations of documented boundaries,
- separates documented rules from architectural inference, and

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/suyog19/agent-plugins-engineering-process-demo/HEAD/README.md

## Skills

- architecture-review: Review a proposed software change for architecture boundary violations, dependency-direction problems, public contract impact, unnecessary coupling, and missing architectural justification. Use when asked for an architecture review, design review, dependency review, or architectural assessment of a…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.
