메뉴
Project-aware expert-role analysis for architecture, debugging, trade-offs, risk, performance, requirements, and design questions. Reads project docs first, then applies expert structured reasoning to the current repository context.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Language-agnostic endpoint documentation generator. Reads routing and codebase to produce structured API contract documentation for existing endpoints.
Expert-role parity check across project docs, platform instruction surfaces, skills, reusable prompts, workflows, quick-reference material, and implementation evidence when authority depends on the current codebase. Use when checking whether the template system still agrees with itself or when preparing cleanup after major changes.
Project-aware expert-role contract design for APIs, interfaces, repositories, services, message schemas, and module boundaries. Reads project docs first, then produces or reviews a contract consistent with the current repository.
Project-aware expert-role broad verification that reads project docs first, classifies the verification target, and routes to the best specialist skill for executable or non-executable checks across code, contracts, docs, architecture, quality, security, reliability, and project health.
Project-aware expert-role database schema and modeling design. Reads project docs first, then produces a schema design, migration plan, or query optimization strategy consistent with the current repository constraints.
Project-aware expert-role for CI/CD pipeline design and implementation. Reads project docs first, enforces build caching, security gates, test execution, and deployment safety.
| name | system-analysis |
| description | Project-aware expert-role analysis for architecture, debugging, trade-offs, risk, performance, requirements, and design questions. Reads project docs first, then applies expert structured reasoning to the current repository context. |
| argument-hint | Describe the problem, decision, artifact, or system to analyze |
Produces a rigorous, expert-level analysis of a problem, decision, artifact, or system after first reading the project documentation that defines the repository's actual context.
This skill is reusable across product, backend, frontend, infrastructure, monorepo, and documentation-heavy projects. It should not assume a particular stack until the project docs confirm it.
| Document | Why it matters |
|---|---|
docs/project-docs/foundation/prd.md | Clarifies goals, scope, stakeholders, and success metrics |
docs/project-docs/foundation/architecture.md | Defines stack, boundaries, integration model, constraints, and runtime assumptions |
docs/project-docs/foundation/status.md | Reveals maturity, roadmap, active workstreams, and known blockers |
docs/project-docs/development/testing.md | Shows what validation exists and how strong the available evidence can be |
| Relevant feature, workflow, API, or guideline docs | Supply domain-specific truth for the topic being analyzed |
| Relevant code, logs, tests, or runtime evidence | Support findings with direct evidence rather than guesswork |
If the required project docs are missing, note the gap explicitly and limit confidence accordingly.
| Trigger | Example request |
|---|---|
| Architecture review | "Analyze this module boundary for coupling risk" |
| Debugging | "Analyze why this workflow fails intermittently" |
| Trade-off decision | "Analyze option A vs option B for this integration" |
| Requirements review | "Analyze these specs for gaps and contradictions" |
| Risk assessment | "Analyze the release risk of this change" |
| Performance diagnosis | "Analyze where this request path will bottleneck" |
| Product or roadmap question | "Analyze whether this feature belongs in MVP" |
Read the relevant project docs first.
Extract:
Break the problem into:
Identify the most load-bearing parts first.
Prefer direct evidence from:
Separate:
Use one or more of:
When comparing options or hypotheses:
prd.md and status.mdWhen using this skill, the output should include:
@agent use system-analysis on [Target Directory/Component] focusing on [Specific Goal/Flow].