ワンクリックで
applying-staging-candidate
Use internally when /refactor-mart dispatches one approved Type: stg candidate
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Use internally when /refactor-mart dispatches one approved Type: stg candidate
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
Use automatically before any completion, successful, passing, PR-ready, merged, or stage-complete statement to verify fresh evidence and choose accurate claim wording.
Use internally when /refactor-mart dispatches one approved Type: int or Type: mart candidate
Use when a monolith warehouse or lakehouse has a whole-warehouse `warehouse-ddl/` snapshot and needs tables or views grouped into business data domains with data owners for data mesh decentralization, setup-source selection, migration planning, or scope and migrate-mart inputs.
Use when generating or revising one dbt model for a single profiled table or view after refactor and approved test-spec work are complete.
Use when the generate-model workflow needs a read-only review of generated dbt model artifacts before accepting the result or sending it back for fixes.
Use when a migrated table, view, or materialized view needs a new or merge-safe `test-specs/<schema.object>.json`, especially after SQL changes or reviewer feedback.
SOC 職業分類に基づく
| name | applying-staging-candidate |
| description | Use internally when /refactor-mart dispatches one approved Type: stg candidate |
Apply one approved staging candidate and update only that candidate section.
Parse exactly two positional arguments:
<plan-file> <candidate-id>
Read references only when needed:
references/staging-validation-contract.md before deciding scope, rewrites, validation, or status writeback.references/status-writeback.md before updating plan status.PLAN_NOT_FOUND.CANDIDATE_NOT_FOUND.Targets plus the candidate Output: and Validation: model names, then scan matching catalog table and view entries for unresolved diagnostics with severity: "error". If any exist, stop with CATALOG_ERRORS_UNRESOLVED, report the catalog object and error code, and do not apply, validate, or update the candidate.- [x] Approve: yes: stop with CANDIDATE_NOT_APPROVED.Type: is not stg: stop with NON_STAGING_CANDIDATE; do not change execution status.Output: for a stg_* model: mark this candidate blocked.blocked.## Candidate: <candidate-id>.Output: and Validation:.references/staging-validation-contract.md.stg_* model.stg_* model with ref().Validation:.references/status-writeback.md.Report:
applying-staging-candidate complete -- <candidate-id>
status: applied|failed|blocked
validation: <command or reason>
plan: <plan-file>