メニュー
Route durable Infiquetra lifecycle artifacts into mission-control prepared issue drafts.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Route proposed Team Mimir profile behavior changes into target-owned Hermes dialogue after producer-owned custody classification.
Compile and review an approved Workflow Contract for Codex V2 graph, profile, write, check, reviewer, fallback, and external-action consistency without launching work.
Explicitly run an operator-approved Infiquetra Workflow Contract as a root-orchestrated Codex V2 DAG with exact profiles, runtime receipts, bounded writes, one independent review, one remediation, and one targeted recheck.
Deep-dive one chosen Infiquetra idea into a right-sized requirements document before planning.
Run a structured Infiquetra code-quality review at the work-to-PR boundary. Reads the merge-base diff, runs a built-vs-planned audit plus judgment-selected review lenses, validates findings, writes a durable review artifact, appends to the work-thread saga, and routes — without mutating code. Triggers on "review this PR", "code review", "check my diff", "pre-PR review", or a /work hand-in before shipping.
Review Infiquetra plans, requirements, and SDLC documents for implementation readiness.
| name | handoff |
| description | Route durable Infiquetra lifecycle artifacts into mission-control prepared issue drafts. |
Use this when the user wants another team, agent team, or later session to pick up work from an Infiquetra lifecycle artifact.
saga owns the handoff moment:
mission-control.mission-control owns the issue artifact:
Do not copy SDLC issue templates into this skill.
Prefer an explicit source path or URL from the command arguments.
If no source is explicit, inspect .codex/saga/state.json and durable docs.
Build the envelope:
python3 plugins/saga/scripts/handoff_envelope.py \
--source docs/plans/example.md \
--target-team Asgard \
--target-repo infiquetra-codex-plugins
If the helper finds no source, ask for one.
If multiple durable artifacts are plausible, ask the user to choose.
Route with the envelope's recommended_skill (mission-control:issues) and
handoff_payload.
Review the prepared issue draft before mutation.
Use issue create-prepared only after mission-control renders a fresh
mutation plan and the user confirms that exact plan.
docs/ideation/ -> idea-readydocs/product-reviews/ -> frontmatter maturity when present, otherwise experiment-readydocs/brainstorms/ -> requirements-readydocs/specs/ -> requirements-readydocs/plans/ or docs/reviews/ -> plan-readydocs/work-sessions/ or branch refs -> resume-readyplatform-specs/06-service-implementations/ or platform-specs/06-feature-modules/ -> requirements-readydeferred-context when the user says execution should waitPrepared issues must be self-contained for recipients without saga.
When a recipient does have saga, the issue may suggest:
saga:plan for idea-ready or requirements-ready;saga:plan for experiment-ready scoped experiment work;saga:work for plan-ready or resume-ready.Do not suggest saga:loop for normal team handoff.