Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

ssot-scope-to-frozen-boundary

Étoiles5

Forks0

Mis à jour1 juin 2026 à 00:41

Drive SSOT target-setting from planned features to a frozen delivery boundary, including profile inclusion, boundary creation, pre-freeze validation, and freeze. Use when Codex needs to take already-defined scope and turn it into an immutable delivery boundary.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

groupsum

groupsum/ssot-registry

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

Explorateur de fichiers

4 fichiers

SKILL.md

readonly

name	ssot-scope-to-frozen-boundary
description	Drive SSOT target-setting from planned features to a frozen delivery boundary, including profile inclusion, boundary creation, pre-freeze validation, and freeze. Use when Codex needs to take already-defined scope and turn it into an immutable delivery boundary.

SSOT Scope To Frozen Boundary

Use this skill after ADRs, SPECs, and features already exist and the task is to turn scope into a frozen boundary.

Command discipline

Do not spend turns rediscovering syntax with --help during normal SSOT work. Use the command surface and examples in this skill directly.
Pick one verified CLI rail for the repo (ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.
Only inspect parser or help text when the user explicitly asks about the CLI surface or when observed runtime behavior contradicts the command patterns documented here.

Workflow

Inspect the target features and any profiles that should expand boundary scope.
Ensure planned features are current or explicitly allowed.
Create or update the boundary with feature IDs and optional profile IDs.
Validate repo state if scope coherence is uncertain.
Freeze the boundary and confirm the snapshot-producing step succeeded.

Operating rules

Treat freeze as the point where scope stops changing.
Treat freeze as a scope lock only; runtime implementation, migration work, required tests, evidence collection, and verification usually still need to happen after this skill finishes.
Require all in-scope features to be current or explicit before freeze.
Prefer a single authoritative boundary row over ad hoc feature lists in later commands.
If the request still needs ADR, SPEC, or feature creation, hand off to $ssot-decision-to-scope.
If the request includes implementation, tests, verification, migration, or release work, escalate to $ssot-e2e-change-orchestrator.

Common commands

ssot feature get . --id feat:demo.change
ssot boundary list .
ssot boundary create . --id bnd:demo.change --title "Demo change boundary" --feature-ids feat:demo.change
ssot boundary add-profile . --boundary-id bnd:demo.change --profile-ids prf:demo.bundle
ssot validate .
ssot boundary freeze . --boundary-id bnd:demo.change

References

references/freeze-readiness.md
references/profile-boundary-notes.md

Plus depuis ce dépôt

même dépôt

ssot-mcp

groupsum/ssot-registry

Route Codex work onto the SSOT MCP control plane instead of direct SSOT registry edits. Use when a task involves SSOT MCP worker campaigns, maturation slices, leases, conflicts, worker events, campaign state, or MCP-governed registry CRUD and CLI delegation. Choose this skill when the user wants pull-only worker execution, honest claim-tier advancement, or lease-aware implementation and evidence flow.

2026-06-265

ssot-mcp-t1-worker-campaign

groupsum/ssot-registry

Execute SSOT MCP pull-worker maturation work targeting T1. Use when Codex should claim leases through SSOT MCP, implement direct runtime behavior, add repeatable project-controlled tests, produce evidence in leased paths, and complete slices honestly without hand-editing the SSOT registry.

2026-06-265

ssot-mcp-t2-worker-campaign

groupsum/ssot-registry

Execute SSOT MCP pull-worker maturation work targeting T2 robustness verification. Use when Codex should claim leases through SSOT MCP, harden existing behavior with negative, edge, concurrency, failure, idempotency, compatibility, security, or recovery coverage, and complete slices honestly with distinct T2 evidence.

2026-06-265

ssot-mcp-t3-worker-campaign

groupsum/ssot-registry

Execute SSOT MCP pull-worker maturation work targeting T3 certification closure. Use when Codex should claim leases through SSOT MCP, deliver runtime, tests, evidence, and certification-closure work within leased paths, satisfy release, boundary, or profile gates where applicable, and complete slices honestly without direct SSOT registry edits.

2026-06-265

ssot-cli

groupsum/ssot-registry

Use the latest available `ssot-registry` CLI, either from a current global install or from a repo-local `uv` environment with a repo-local cache, to inspect, validate, and mutate SSOT registries. Use when Codex should operate through the CLI instead of editing `.ssot/registry.json` by hand.

2026-06-265

ssot-claim-evidence-linking

groupsum/ssot-registry

Create, inspect, update, delete, evaluate, verify, link, and unlink claims and evidence, including their feature and test relationships. Use when Codex needs to connect claims to features, tests, and evidence, set claim status, check claim tier, create additive higher-tier claim promotion, or verify whether proof chains are strong enough for release and certification workflows.

2026-06-185

name	ssot-scope-to-frozen-boundary
description	Drive SSOT target-setting from planned features to a frozen delivery boundary, including profile inclusion, boundary creation, pre-freeze validation, and freeze. Use when Codex needs to take already-defined scope and turn it into an immutable delivery boundary.

SSOT Scope To Frozen Boundary

Use this skill after ADRs, SPECs, and features already exist and the task is to turn scope into a frozen boundary.

Command discipline

Do not spend turns rediscovering syntax with --help during normal SSOT work. Use the command surface and examples in this skill directly.
Pick one verified CLI rail for the repo (ssot, ssot-registry, ssot-cli, or uv run ssot) and reuse it consistently by substituting that rail into the examples below.
Only inspect parser or help text when the user explicitly asks about the CLI surface or when observed runtime behavior contradicts the command patterns documented here.

Workflow

Inspect the target features and any profiles that should expand boundary scope.
Ensure planned features are current or explicitly allowed.
Create or update the boundary with feature IDs and optional profile IDs.
Validate repo state if scope coherence is uncertain.
Freeze the boundary and confirm the snapshot-producing step succeeded.

Operating rules

Treat freeze as the point where scope stops changing.
Treat freeze as a scope lock only; runtime implementation, migration work, required tests, evidence collection, and verification usually still need to happen after this skill finishes.
Require all in-scope features to be current or explicit before freeze.
Prefer a single authoritative boundary row over ad hoc feature lists in later commands.
If the request still needs ADR, SPEC, or feature creation, hand off to $ssot-decision-to-scope.
If the request includes implementation, tests, verification, migration, or release work, escalate to $ssot-e2e-change-orchestrator.

Common commands

ssot feature get . --id feat:demo.change
ssot boundary list .
ssot boundary create . --id bnd:demo.change --title "Demo change boundary" --feature-ids feat:demo.change
ssot boundary add-profile . --boundary-id bnd:demo.change --profile-ids prf:demo.bundle
ssot validate .
ssot boundary freeze . --boundary-id bnd:demo.change

References

references/freeze-readiness.md
references/profile-boundary-notes.md