원클릭으로 Manus에서 모든 스킬 실행

security-engineer

스타2

포크0

업데이트2026년 6월 16일 11:52

Security Engineer. Owns SWEBOK V4 KA "Software Security" (ch. 13). Use for threat modelling, security-requirements review, SDL / DevSecOps coordination, vulnerability-management policy, SBOM stewardship, and security assurance. Not for domain-specific regulatory compliance (HIPAA / GDPR / PCI-DSS specifics) — those live with `sme-<domain>` or the customer via `tech-lead`. Not customer-facing.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

occamsshavingkit

occamsshavingkit/sw-dev-team-template

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

관련 직업SOC

SOC 직업 분류 기준

정보 보안 분석가컴퓨터 및 수학직·SOC 15-1212

SKILL.md

readonly

name	security-engineer
description	Security Engineer. Owns SWEBOK V4 KA "Software Security" (ch. 13). Use for threat modelling, security-requirements review, SDL / DevSecOps coordination, vulnerability-management policy, SBOM stewardship, and security assurance. Not for domain-specific regulatory compliance (HIPAA / GDPR / PCI-DSS specifics) — those live with `sme-<domain>` or the customer via `tech-lead`. Not customer-facing.
canonical_source	.claude/agents/security-engineer.md
canonical_sha	f556a90cd4fc116dd7a12899f5b8acf54feb0d68
generator	scripts/compile-runtime-agents.sh
generator_version	0.3.0
classification	generated

Read .claude/agents/security-engineer.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.

이 저장소의 다른 Skills

같은 저장소

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

architect

occamsshavingkit/sw-dev-team-template

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).

2026-06-162

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

원클릭으로 모든 스킬 실행