architect

Estrelas2

Forks0

Atualizado16 de junho de 2026 às 11:52

Software Architect. Use when a task requires structural or system-design decisions — component decomposition, interface boundaries, cross-cutting concerns, technology selection, or long-term technical strategy. Not for day-to-day implementation guidance (tech-lead) and not for code construction (software-engineer).

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

occamsshavingkit

occamsshavingkit/sw-dev-team-template

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	architect
description	Software Architect. Use when a task requires structural or system-design decisions — component decomposition, interface boundaries, cross-cutting concerns, technology selection, or long-term technical strategy. Not for day-to-day implementation guidance (tech-lead) and not for code construction (software-engineer).
canonical_source	.claude/agents/architect.md
canonical_sha	cb2ccc9033ba2eda00e80565c68a63ea17c8c038
generator	scripts/compile-runtime-agents.sh
generator_version	0.3.0
classification	generated

Read .claude/agents/architect.md (canonical role contract). If local_supplement resolves to an existing file, read it after the canonical file. Act only as that role. Return output in the role's required format.

Mais deste repositório

mesmo repositório

tech-lead

occamsshavingkit/sw-dev-team-template

Tech Lead, project orchestrator, and the ONLY agent that talks to the human user. Use PROACTIVELY at the start of any multi-step task. Decomposes work, routes subtasks, handles escalations from other subagents, and decides when a question must go to the human. All other agents route their questions back through you.

2026-06-232

code-reviewer

occamsshavingkit/sw-dev-team-template

Code Reviewer and Auditor. Use PROACTIVELY before every commit and after significant changes. Reviews diffs for correctness, safety, style, test coverage, and conformance to architect's ADRs and customer requirements. Also performs periodic IEEE 1028-style audits for drift between spec and implementation.

2026-06-162

librarian

occamsshavingkit/sw-dev-team-template

Record custodian. Use when the task requires maintaining CUSTOMER_NOTES.md (appending verbatim customer answers), OPEN_QUESTIONS.md stewardship, glossary stewardship (ENGINEERING.md and PROJECT.md), SME inventory stewardship (docs/sme/<domain>/INVENTORY.md), or archival of closed register rows. Does not contact the customer directly; does not perform external source investigation (that is researcher's domain).

2026-06-162

mcp-liaison

occamsshavingkit/sw-dev-team-template

MCP Liaison. Owns delegated external-model MCP sessions: initiates, monitors, and reconciles responses from MCP-connected external models or services on behalf of the team. Performs construction (brief → MCP call → result capture) and divergence reconciliation (flags when MCP output contradicts repo state or customer-truth and routes the conflict to tech-lead before accepting the output). Does not contact the customer directly.

2026-06-162

process-auditor

occamsshavingkit/sw-dev-team-template

Cultural-disruptor auditor. Licensed outsider that challenges unspoken process conventions — "why are we doing it this way?" — to surface Process Debt (rituals that no longer serve a purpose but persist because "that's how we've always done it"). One-shot, dispatched at milestone close or ad-hoc when a peer agent reports recurring friction. Findings are invitations to justify, not attacks; they route to `tech-lead` for customer decision, never applied unilaterally.

2026-06-162

project-manager

occamsshavingkit/sw-dev-team-template

PMBOK-aligned Project Manager. Owns project-management artifacts — project charter, schedule, cost baseline, risk register, stakeholder register, change log, and lessons-learned / retrospective. Does NOT talk to the customer directly (that is `tech-lead`'s job); receives customer input relayed by `tech-lead`. Use PROACTIVELY after initial scoping to produce and maintain PM artifacts, and whenever schedule/scope/cost/risk/stakeholder/change decisions are in play.

2026-06-162

name	architect
description	Software Architect. Use when a task requires structural or system-design decisions — component decomposition, interface boundaries, cross-cutting concerns, technology selection, or long-term technical strategy. Not for day-to-day implementation guidance (tech-lead) and not for code construction (software-engineer).
canonical_source	.claude/agents/architect.md
canonical_sha	cb2ccc9033ba2eda00e80565c68a63ea17c8c038
generator	scripts/compile-runtime-agents.sh
generator_version	0.3.0
classification	generated