メニュー
Standardizes how `remotion-builder` runs Stage C (implementation) after tech CRO approval — remotion CLI, browser ensure, Skia smoke, ffmpeg from approved recipes, group checkpoints.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Track agent decisions, metrics, token costs, and generate reports. Use when logging task execution, tracking agent performance, or generating observability reports.
Unified ai-brain skill combining memory operations and KB query operations with promotion flow.
Bootstraps a Jira hierarchy snapshot before any multi-issue create / edit session. Disambiguates the parent input (issue key, spec URL, Confluence page URL, or `greenfield`), walks parents up (depth-cap 4), walks children down via JQL recursion (depth-cap 4, max 50 children per node), and returns a structured tree alongside the issue-type scheme and link-type metadata the caller needs to render a draft. Used primarily by `atlassian-pm`; secondary consumers (after the G2.5 retrofit) are the upstream Atlassian plugin skills `spec-to-backlog` and `capture-tasks-from-meeting-notes`. The skill **does not render**; rendering belongs to the caller (typically `atlassian-pm` rendering a markdown tree to chat).
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full, ultra. Defaults: main chat = lite, subagents = ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Generate → execute → fail → analyze → fix → repeat cycle with failure pattern recognition. Use when implementing changes that need verification and automatic recovery.
Heuristic context budget checks using file-size and count proxies — integrates with context-cache-discipline; no tokenizer introspection claims.
| name | remotion-builder-execution-gate |
| description | Standardizes how `remotion-builder` runs Stage C (implementation) after tech CRO approval — remotion CLI, browser ensure, Skia smoke, ffmpeg from approved recipes, group checkpoints. |
| version | 1 |
Stage C for remotion-builder. Invoked only after tech CRO approved (v2 on disk) or recorded degraded_skip under ## Open Risks.
phase-by-phase or all-phases-approved with explicit authorization.remotion-builder-mode-policy.yml.assets/) have named approvals per governance.npx remotion browser ensure (or documented non-interactive equivalent) when the plan requires; CI=true where vendor docs recommend.LoadSkia() before registerRoot in entry — verify ordering matches plan.--gl / env per plan and target host.npx remotion / npm run targets exactly as declared in the phase.ffmpeg -version smoke when first used in episode.-filter_complex from user chat unless governance approval recorded.phase-by-phase: stop after each parallel group; wait proceed.all-phases-approved: continue groups; destructive still needs per-action named approval.remotion-builder-governance.md.agent-observability metrics (render duration, bytes out, outcome).subagent-response-protocol incident path.blocked_invalid_entry — no dispatch.