pi-architecture

Standardize and trace application architecture analysis from As-Is diagnosis to To-Be design.

Updated May 26, 2026
One-click install
npx skills add https://github.com/koasis89/ite-ai-agent --skill pi-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pi-architecture
Source: https://github.com/koasis89/ite-ai-agent/tree/main/skills/pi-architecture
Command: npx skills add https://github.com/koasis89/ite-ai-agent --skill pi-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill aids in the standardization and traceability of application architecture analysis and design in PI consulting, reducing the need for rework and minimizing gaps between As-Is and To-Be systems.

Core Features & Use Cases

  • As-Is Analysis: Perform comprehensive As-Is system diagnosis with standard outputs.
  • Gap Analysis: Identify and document technical and business gaps between As-Is and To-Be systems.
  • Architecture Design: Generate architecture diagrams and ADRs for To-Be systems.
  • Effort Estimation: Calculate project effort with WBS and M/M estimation methods.
  • Use Case: A PI consultant uses this Skill to analyze a legacy system, identify gaps, design a new architecture, and estimate the effort required for the migration.

Quick Start

Use the pi-architecture skill to perform an As-Is analysis of the current system and generate a To-Be architecture design.

Frequently Asked Questions about pi-architecture

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

FAQPage Schema
How do I standardize application architecture analysis and reduce rework in PI consulting?

Standardize application architecture analysis by tracing processes from As-Is diagnosis to To-Be design, ensuring traceability and reducing rework. This approach utilizes mission sequences, templates, and ID tracking systems for consistency.

What is the best way to identify technical and business gaps between As-Is and To-Be systems?

Identify technical and business gaps by performing a comprehensive As-Is system diagnosis and comparing it against To-Be requirements. This structured gap analysis ensures all architectural discrepancies are formally documented and addressed.

How do I generate architecture diagrams and ADRs for a To-Be system design?

Generate architecture diagrams and ADRs for To-Be systems by standardizing the architecture design process. This ensures consistent outputs that trace directly back to the identified gaps from the As-Is analysis phase.

How do I calculate project effort estimation for an application architecture migration?

Calculate project effort estimation for architecture migrations using WBS and M/M estimation methods. This provides a structured breakdown of tasks and resources needed to transition from As-Is to To-Be systems.

Can I trace architecture design decisions back to the original As-Is system diagnosis?

Yes, you can trace architecture design decisions back to the original As-Is diagnosis. The process uses an ID tracking system and templates to maintain consistency and ensure full traceability throughout the consulting lifecycle.