Run any Skill in Manus with one click

ssot-feature

Stars5

Forks0

UpdatedJune 1, 2026 at 00:41

Manage feature entities with full CLI coverage, including planning, lifecycle transitions, and dependency/claim/test link management.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

groupsum

groupsum/ssot-registry

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	ssot-feature
description	Manage feature entities with full CLI coverage, including planning, lifecycle transitions, and dependency/claim/test link management.

SSOT Feature

Use this skill for feature-only operations.

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.

Command surface

feature create|get|list|update|delete|link|unlink|plan
feature lifecycle set

Workflow

Inspect feature state and links.
Apply roadmap targeting with feature plan.
Update support state with feature lifecycle set.
Manage claim/test/dependency links with feature link/feature unlink.

Operating rules

Distinguish planning (plan) from support policy (lifecycle).
feature plan --claim-tier sets the target assurance tier; it does not mean the feature should only retain one linked claim tier.
Promotion is additive, not replacement: when a feature moves from T0 to T1 or T1 to T2, keep the lower-tier claims linked and add the higher-tier claim plus its proof.
Do not unlink lower-tier claims just because a higher-tier claim is added. Only unlink claims that are incorrect, obsolete for non-tier reasons, or were linked by mistake.
If the request includes freeze or release progression, escalate to $ssot-e2e-change-orchestrator.

Example

ssot feature get . --id feat:demo.login
ssot feature plan . --ids feat:demo.login --horizon current --claim-tier T1 --target-lifecycle-stage active
ssot feature link . --id feat:demo.login --claim-ids clm:demo.login.t0 --test-ids tst:demo.login.smoke
ssot feature link . --id feat:demo.login --claim-ids clm:demo.login.t1 --test-ids tst:demo.login.integration

More from this repository

same repository

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

SSOT Feature

Use this skill for feature-only operations.

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.

Command surface

feature lifecycle set

Workflow

Inspect feature state and links.

Apply roadmap targeting with feature plan.

Update support state with feature lifecycle set.

Manage claim/test/dependency links with feature link/feature unlink.

Operating rules

Distinguish planning (plan) from support policy (lifecycle).

feature plan --claim-tier sets the target assurance tier; it does not mean the feature should only retain one linked claim tier.

Promotion is additive, not replacement: when a feature moves from T0 to T1 or T1 to T2, keep the lower-tier claims linked and add the higher-tier claim plus its proof.

Do not unlink lower-tier claims just because a higher-tier claim is added. Only unlink claims that are incorrect, obsolete for non-tier reasons, or were linked by mistake.

If the request includes freeze or release progression, escalate to $ssot-e2e-change-orchestrator.

Example

ssot feature get . --id feat:demo.login ssot feature plan . --ids feat:demo.login --horizon current --claim-tier T1 --target-lifecycle-stage active ssot feature link . --id feat:demo.login --claim-ids clm:demo.login.t0 --test-ids tst:demo.login.smoke ssot feature link . --id feat:demo.login --claim-ids clm:demo.login.t1 --test-ids tst:demo.login.integration