plan-architecture

Name: plan-architecture
Availability: InStock
Author: dthompson-jti

Map PRD requirements to architectural components, data models, and system interfaces.

Updated Aug 27, 2026

Search Tags:#planning #architecture #system-design #data-models #risk-analysis #component-hierarchy

Ready to run

npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-architecture

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: plan-architecture
Source: https://github.com/dthompson-jti/safety-check-app-concept/tree/main/.agent/skills/plan/architecture
Command: npx skills add https://github.com/dthompson-jti/safety-check-app-concept --skill plan-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create a comprehensive technical architecture specification that maps PRD requirements to data models, component hierarchy, and risk analysis, enabling informed architectural decisions for large features.

Core Features & Use Cases

Data Flow Diagram: Show data movement across systems and boundaries, including interfaces and persistence.
Data Model & State: Define types, interfaces, and atoms/state for the proposed solution.
Component Hierarchy: Provide a clear parent-child structure and interactions across layers.
Risk Analysis: Identify trade-offs, constraints, and failure modes with mitigations.
Use Case: After PRD approval for a large feature, generate 3-4 architectural options with rationale.

Quick Start

Generate a complete architecture specification for a large feature after PRD approval, including data models, component hierarchy, and risk analysis.

Frequently Asked Questions about plan-architecture

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

FAQPage Schema

How do I map PRD requirements to technical architecture specifications?▼

Map PRD requirements to technical architecture specifications by defining data models, component hierarchy, and system interfaces alongside a structured risk analysis. This process translates feature requirements into clear architectural components and data flow diagrams.

What's the best way to design system architecture for a large feature?▼

Design system architecture for a large feature by generating 3-4 architectural options with rationale, data flow diagrams, and state management strategy. This approach ensures informed decisions for cross-cutting system changes.

How do I create a risk-focused phased implementation plan for cross-cutting system changes?▼

Create a risk-focused phased implementation plan by identifying trade-offs, constraints, and failure modes with mitigations. Specify phase-based deliverables to address architectural risks systematically during cross-cutting system changes.

Does this architecture planning approach work for small features or only large ones?▼

This architecture planning approach is specifically designed for large features and cross-cutting system changes. It requires generating multiple architectural options and comprehensive risk analysis, making it excessive for small feature modifications.

How do I define data models and state management strategy for proposed system interfaces?▼

Define data models and state management strategy by specifying types, interfaces, and atoms/state for the proposed solution. Include data flow diagrams showing data movement across systems, boundaries, and persistence layers.