メニュー
Use for F6 planning or implementation involving monitors, alert cards, thresholds, investigation missions, policy/control ownership, recurring checks, or demo replays.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for active docs, CFO Wiki docs, local-dev docs, eval docs, benchmark docs, roadmap, START_HERE, or docs that guide future Codex threads.
Use for proof bundles, evidence summaries, alert cards, monitoring results, reporting outputs, approval cards, validation ladders, or shipped-claim truthfulness.
Use when a task is complex, spans multiple files or packages, or needs a step-by-step execution document. Create or update a Finance Plan in plans/ that follows PLANS.md exactly, uses the F0-F6 roadmap, and remains live during implementation.
Use for any Pocket CFO task that creates, updates, audits, or executes Finance Plans, active roadmap docs, phase handoffs, or plan truthfulness. Do not use to widen scope beyond the current active plan.
Use when implementing GitHub webhooks, repository sync, installation auth, or repo-content ingestion. Enforces GitHub App-first integration, least privilege, webhook signature verification, installation-token caching, and connector-only scope inside Pocket CFO.
Use for implementation or planning tasks that touch module boundaries, route design, schema, runtime, approvals, reporting, monitoring, or package-level architecture.
| name | f6-monitoring-semantics-guard |
| description | Use for F6 planning or implementation involving monitors, alert cards, thresholds, investigation missions, policy/control ownership, recurring checks, or demo replays. |
Purpose: Define F6 monitoring safely: deterministic, source-backed, human-reviewable, and delivery-free unless later plans authorize otherwise.
General Pocket CFO invariants:
F6 hard boundaries:
