메뉴
Select and create accurate software architecture, workflow, interaction, data, state, and deployment diagrams.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
OpenAgentd workflow for version bumps, release PRs, GitHub releases, and release notes.
OpenAgentd workflow for keeping the compact feature catalogue and README aligned with user-visible changes.
Research first, propose a step-by-step implementation plan, and wait for explicit approval before writing any code.
Semantic search over the retained OpenAgentd feature catalogue, ADRs, and repository instructions using the turbovec experiment index.
OpenAgentd TDD workflow — write a failing test before the code that makes it pass, reproduce a bug with a test before fixing it. Use when implementing any logic, fixing any bug, or changing any existing behavior in backend (pytest) or frontend (Bun/RTL) code.
OpenAgentd testing reference — environment setup, run commands, and fix patterns for backend (pytest) and frontend (Bun/RTL). Load this for running, fixing, or adding coverage to existing tests. For writing a failing test before new code, use oad/test-driven-development instead.
SOC 직업 분류 기준
| name | oad/diagram |
| description | Select and create accurate software architecture, workflow, interaction, data, state, and deployment diagrams. |
Use this skill to select a diagram type, then read only its reference.
| Request | Reference |
|---|---|
| System/runtime architecture, integrations, components | architecture |
| User, business, or operational process | workflow |
| Requests, events, streaming, or cross-service interactions | sequence |
| Lifecycle, retry, cancellation, or status transitions | state |
| Persistent records and relationships | data |
| Device, process, network, and trust topology | deployment |
Before drawing, state the one question it answers and verify facts in code,
tests, configuration, docs, and the nearest AGENTS.md. Use the smallest
useful diagram; split crowded views. Label relationships and directions, mark
proposals/unknowns, and keep open questions separate from facts. Do not expose
secrets or private data, or add a renderer/dependency unless explicitly asked.
