メニュー
Validate locally-emitted telemetry against a written narrative spec, or run a generic health check on the local OTel stack. Delegates to the observability-driven-development skill's Validation section.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Write, refactor, restructure, edit, or audit technical documentation using the Diátaxis framework (tutorials, how-to guides, reference, explanation). Produces clear, concise, scannable docs and fights the default tendency toward bloated, over-explained AI prose. Use this skill for ANY documentation work — README and CONTRIBUTING files, API/reference docs, runbooks, guides, getting-started pages, conceptual write-ups, docs-site content, or doc reviews — even when the user just says "document this," "write docs for X," "clean up these docs," "explain how this works in the docs," or "what's missing from our documentation." If the deliverable is documentation, reach for this skill rather than writing prose freehand.
Retroactively create Linear tickets and PRs from untracked commits. Use for commits without tickets, "founder mode", or formalizing experimental work.
Create well-structured git commits from analyzed changes. Use when the user asks to commit, save work, or create a commit.
Find architectural friction and propose deep-module refactors as RFC issues. Use to improve architecture, find refactoring opportunities, or deepen shallow modules.
Initialize the AI Engineering Harness (AGENTS.md + thoughts/ structure). Use on /init_harness or when setting up the harness in a repo.
Interview the user relentlessly to stress-test a plan or design. Use to validate design decisions, "drill in", or "ask me questions" before implementation.
| name | validate_telemetry |
| description | Validate locally-emitted telemetry against a written narrative spec, or run a generic health check on the local OTel stack. Delegates to the observability-driven-development skill's Validation section. |
| disable-model-invocation | true |
| argument-hint | [spec-file-path] |
| allowed-tools | Read, Bash, Grep, Glob |
Activate the observability-driven-development skill and run its Validation section.
thoughts/shared/telemetry/, run Mode A — Spec-Driven Validation.Before running either mode, confirm:
curl -sf http://localhost:18888
returns 2xx).OTEL_EXPORTER_OTLP_ENDPOINT set).If either fails, surface a one-line setup hint pointing at
observability-driven-development/local-setup.md and stop.
Per the report format in the ODD skill's Validation section. Don't modify code or config silently — the report is the output.
Ticket → /create_plan → [ODD: write narrative]
→ /implement_plan → /validate_plan (correctness)
→ /validate_telemetry (telemetry) → /commit