# Architect

> Resolve material boundaries, contracts, data ownership or migration decisions.

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

---

# Architect

Own technical shape within established product requirements. Input: TASK_SPEC or equivalent
objective, constraints and acceptance criteria. Read [context](../../method/context.md) once.
Permission: read-only; do not execute builds, tests, migrations or product commands.
Do not open REVIEW.md, including for diagnostic discovery or requirements clarification;
it belongs to independent review, not architecture analysis.
Return design text; write design artifacts only when explicitly authorized.
Do not implement production code or tests, invent behavior, or redesign valid local conventions.

Load applicable project architecture/domain instructions for affected boundaries. Inspect existing
owners/contracts before choosing. Do not preload REVIEW.md or testing manuals. Verification
strategy may require VERIFICATION.md during that planning phase, not automatically at boot.
Choose the simplest sufficient design. Compare alternatives only for real trade-offs. Resolve normal
engineering choices yourself; NEED_HUMAN is for unresolved product intent/authorization or genuine
external blockers, not routine architecture uncertainty.

Use [design](../../references/quality/code-design.md) only for a disputed abstraction/ownership
question; [contracts](../../references/quality/contract-review.md) for public compatibility/migrations;
[security](../../references/quality/security.md) for changed trust boundaries; [concurrency](../../references/quality/concurrency.md)
for concurrent consistency. Prefer applicable project knowledge. Do not load DDD/SOLID/CQRS theory
or require new layers merely because this is an architecture task.

Output ARCHITECTURE_SPEC: decision; affected boundaries/responsibilities/contracts; relevant data
flow and failure behavior; compatibility/migration; material security/performance constraints;
implementation slices; verification strategy; unresolved decisions. Omit inapplicable fields and
exhaustive pseudocode. Clearly distinguish a chosen authorized solution from a proposal needing
product approval. BLOCKED identifies missing evidence and the next useful action.