メニュー
Use when setting up agent governance for a repo, or when working in a repo that contains agent-policy.yaml. Classifies structural risk and routes human attention to red-zone changes.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when showing or updating roadmap state in a repo with the minimap roadmap convention (board.md, scope.md, features/, ideas/). Not for arbitrary spec review.
Use when you need to explicitly search, store, or debug Pallium memory beyond what automatic injection provides. Triggers on: "remember this", "why don't you remember", "what do you know about", memory debugging, or when injected context is insufficient.
Use when tasks need 3+ steps, involve architecture/refactor seams, behavior-parity risk, or bug/test/CI failures. Skip for trivial one-liners, pure Q&A, or when the user explicitly asks to skip planning.
Review and shape Pallium features, plans, implementations, and cross-thread work for product alignment, architectural fit, safety, and proportional design. Use when acting as architect/reviewer for this repo, when evaluating a proposed feature or implementation, when coordinating work across threads, or when deciding whether a change is the smallest valuable slice that fits the current roadmap and package boundaries.
| name | agent-redline |
| description | Use when setting up agent governance for a repo, or when working in a repo that contains agent-policy.yaml. Classifies structural risk and routes human attention to red-zone changes. |
You classify changes before editing. Deterministic CI checks (a boundary-rule backend, the reporter) catch what you miss.
| Term | Meaning |
|---|---|
| Red zone | Changes are dangerous: contracts, modeling, architecture, security, persistence, shared behavior. |
| Blue zone | Autonomous work fine: isolated, replaceable, strongly testable, low blast-radius. |
| Gray zone | Unclassified. Cautious by default. |
| Watch | Additive tag (not a zone): paths surfaced in the PR comment regardless of red/blue/gray classification. No checkpoint, no gate — visibility only. |
| Boundary rule | Deterministic dependency rule (X must not import Y). Enforced by a backend (e.g., ArchUnit). |
| Checkpoint | Required human attention; satisfied by a label or CODEOWNER approval. Types: architecture-review, api-review, persistence-review, security-review, ops-review. |
agent-policy.yaml exists in the repo root → read operating-mode.md. Everyday work.bootstrap-mode.md. One-time setup.Read only the file for the mode that applies.
watch paths to surface in the PR.architecture-review, regardless of what the policy says.When ambiguous:
agent-policy.yamlAGENTS.md / CLAUDE.md / GEMINI.mdoperating.md (if present)Do not invent rules the policy doesn't state.
operating-mode.md — read when entering operating modebootstrap-mode.md — read when entering bootstrap modeextensions/<name>/ — profile.md and scaffold.md during bootstrap; operating.md once per session in operating mode if presentdocs/agent/ in the consuming repo — read a per-checkpoint doc only when escalating to that checkpoint