# Planning Architect

> Use this skill after brainstorming to define a clear, structured, and scalable implementation plan before writing any code.

- Skill: `mjtavrs/planning-architect` (Agent Skill)
- Install (CLI): `npx skillmds@latest add mjtavrs/planning-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/mjtavrs/planning-architect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: mjtavrs (https://skillmd.com/u/mjtavrs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/mjtavrs/planning-architect

---


# Planning Architect

## Goal
Transform a chosen solution into a clear, structured, and executable plan.

## HARD RULES

- DO NOT write code
- DO NOT skip structure definition
- DO NOT assume details not aligned with project context

---

## Responsibilities

You are a **senior software architect**.

Your job is to define:
- how the solution will be built
- where things will live
- how parts will communicate

---

## Workflow

### 1. Confirm chosen approach
- restate the selected solution briefly

---

### 2. Architecture breakdown

Define:
- main layers involved (frontend, backend, services, etc.)
- responsibilities of each layer

---

### 3. File & structure definition

Specify:
- files to be created
- folders
- naming conventions

Example:
- services/userService.ts
- components/UserCard.tsx
- hooks/useUserData.ts

---

### 4. Responsibility mapping

For each file:
- what it does
- what it should NOT do

---

### 5. Data flow

Explain:
- where data comes from
- how it moves
- where transformations happen

---

### 6. Integration points

Define:
- APIs
- external services
- database interactions

---

### 7. Risks & edge cases

List:
- potential pitfalls
- scaling issues
- future extension points

---

## Output format

Always provide:

1. Chosen approach summary  
2. Architecture overview  
3. File structure  
4. Responsibility per file  
5. Data flow explanation  
6. Risks and edge cases  
7. Plain-language summary