메뉴
Codex teams runtime entrypoint for advanced coding models. Use when the operator needs to inspect, diagnose, resume, watch, or manage the supported durable team surface rather than execute a feature workflow.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Advanced post-Review human acceptance workflow. Use after fresh approved Review closeout to restore a contextless human's understanding, guide one real product step at a time, and persist an explicit pass, fail, or blocked verdict.
Read-only cross-artifact consistency analysis for advanced coding models. Use when tasks exist and the specification, plan, and task boundaries need an independent gate before or during execution.
Existing-spec repair workflow for advanced coding models. Use when a specification package has planning-critical ambiguity, weak acceptance, contradictions, or new constraints that should be absorbed without recreating the feature.
Focused pre-plan feasibility research for advanced coding models. Use when a planning-ready specification still lacks a credible implementation chain, external evidence, or a disposable proof.
Lean design-system workflow for advanced coding models. Use for a new product UI, redesign, rebrand, shared visual language, or an audit/update of the root DESIGN.md contract.
Resumable product and technical discussion for advanced coding models. Use when a rough idea needs durable decisions and options before formal specification.
| name | spx-team |
| description | Codex teams runtime entrypoint for advanced coding models. Use when the operator needs to inspect, diagnose, resume, watch, or manage the supported durable team surface rather than execute a feature workflow. |
Read references/project-learning.md and apply its consume-only policy; the owning workflow captures.
Read references/project-cognition.md for its evidence boundary and
references/runtime-boundary.md. Do not run cognition intake for pure runtime
status or lifecycle operations; use it only when the question includes
repository impact or workflow routing.
This skill operates the Codex-only runtime; it does not replace
$spx-implement-teams. Start with {{specify-subcmd:specify-runtime sp-teams status}}. Use
{{specify-subcmd:specify-runtime sp-teams doctor}} for configuration/state diagnostics and
{{specify-subcmd:specify-runtime sp-teams live-probe}} only when install or runtime health
needs an active proof.
Inspection and diagnosis authorize only status and doctor. Never run
live-probe implicitly: it may create transient runtime state and requires
explicit operator authorization.
Perform the explicit runtime action requested by the operator—status, watch, await, resume, sync-back, shutdown, or cleanup—after checking its help and current state. Prefer recovery-preserving actions. Do not dispatch feature work without a validated implementation task packet, do not clean active state, and do not claim this backend exists for an integration where the launcher reports it unavailable.
Report the runtime state and supported next action. Route ready feature
execution to $spx-implement-teams and ordinary bounded parallelism to
$spx-implement as explicit handoffs. This invocation authorizes only this
workflow stage; do not invoke another workflow in this run.
