메뉴
Document conventions, templates, and rules for OpenSearch feature/release reports. Use when creating or editing docs under docs/features/ or docs/releases/, including file naming, tag system, link rules, report templates, and Mermaid diagram conventions.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Common GitHub workflow patterns for this project. Use when creating branches, committing, pushing, creating PRs, merging, managing Issues (labels, comments, close), or detecting repository info. Covers the standard docs branch workflow used by investigate, summarize, refactor, and other agents.
Search OpenSearch documentation, blogs, and community forums. Use when the user asks about OpenSearch features, configuration, APIs, troubleshooting, k-NN, neural search, cluster settings, index mappings, query DSL, or any OpenSearch-related questions. Also use when investigating features and needing to find official documentation or blog posts.
Fetch web page content as Markdown using trafilatura. Use when sub-agents or agents need to read web page content but don't have access to the web_fetch tool. Works via shell with a Python one-liner.
Create and configure Kiro CLI custom agents (JSON config files). Use when user asks to "create a kiro agent", "make a custom agent", "configure agent tools", "set up MCP servers in an agent", "add hooks to an agent", "troubleshoot agent config", or any task involving kiro-cli agent JSON configuration, tool permissions, resources, hooks, steering, MCP integration, or code intelligence setup.
| name | document-conventions |
| description | Document conventions, templates, and rules for OpenSearch feature/release reports. Use when creating or editing docs under docs/features/ or docs/releases/, including file naming, tag system, link rules, report templates, and Mermaid diagram conventions. |
Single Source of Truth for report structure and formatting. See DEVELOPMENT.md for project-level conventions.
docs/
├── features/{repository}/ # Cumulative feature docs
│ ├── {repository}-{feature}.md
│ └── index.md
└── releases/v{version}/ # Version-specific docs
├── features/{repository}/
│ └── {item-name}.md
├── index.md
└── summary.md
| Type | Pattern | Example |
|---|---|---|
| Feature doc | {repository}/{repository}-{feature}.md | k-nn/k-nn-explain-api.md |
| Release doc | releases/v{ver}/features/{repository}/{item}.md | releases/v3.0.0/features/k-nn/explain-api.md |
Rules: lowercase, hyphen-separated, include repo prefix, avoid temporal suffixes (-bugfixes.md).
-plugin suffix for dashboards plugins: alerting-dashboards-plugin/ → alerting-dashboards/One tag per document: the repository name from file path.
---
tags:
- {repository}
---
No domain/, component/, or topic/ prefixes.
.md links — use plain text references insteadSee references/templates.md for Feature Report, Release Report, and Release Summary templates.
TB (top-to-bottom)LR only for simple flows (≤3 nodes)TB with subgraphs| Use Case | Syntax |
|---|---|
| Architecture | graph TB |
| Data Flow | flowchart TB |
| Sequence | sequenceDiagram |
| State | stateDiagram-v2 |
When updating existing reports: