# HyperTwist - SKILLS.md

## Purpose

This file is the HyperTwist-facing discovery surface for skill families and
skill governance.

It is not a claim that HyperTwist already ships a broad live skill layer.

Use the governing doctrine for rollout, command-surface rules, and off-state
requirements:

- `C:\HyperTwist\docs\ops\HYPERTWIST_SKILLIZATION_AND_COMMAND_SURFACE_DOCTRINE_2026-05-21.md`

Companion doctrines:

- `C:\HyperTwist\docs\ops\HYPERTWIST_OPTIONAL_ASSISTIVE_FEATURE_DEACTIVATION_AND_REMOVABILITY_DOCTRINE_2026-05-21.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_MEMORY_LANE_AUTHORITY_AND_PHASE_IMPLEMENTATION_DOCTRINE_2026-05-21.md`
- `C:\HyperTwist\docs\ops\HYPERTWIST_PROVIDER_NEUTRALITY_AND_BYOK_DOCTRINE_2026-05-21.md`
- `FEATURE_REGISTRY.md`

## Product rule

Skills are optional assistive layers.

They must:

- sit on top of first-party commands/services
- remain user-deactivatable
- remain removable
- never become the primary truth of a feature

## Current status tiers

Use the feature-registry confidence split here too:

- `Implemented now`
- `Deep-source grounded retained`
- `Shallow placeholder`

Do not present a planned skill family as a shipped skill layer.

## Highest-priority retained skill families

These are retained doctrine-level families, not live implementation claims.

### First-party skill substrate and governance

Status:

- Deep-source grounded retained

Includes:

- skill registry/manifest
- enable/disable controls
- provenance/invocation ledger
- validation harness

### Analyzer and review skills

Status:

- Deep-source grounded retained

Includes:

- architecture/repo analysis wrappers
- review/diff/plan helpers
- bounded workflow wrappers

### Memory and continuity skills

Status:

- Deep-source grounded retained

Includes:

- resume/session skills
- recall/search skills
- compact-view skills

### Provider and operations skills

Status:

- Deep-source grounded retained

Includes:

- provider-profile inspection
- BYOK setup
- routing/usage diagnostics

### Domain skill packs

Status:

- Shallow placeholder

Includes:

- replay/training packs
- curriculum packs
- media/export packs

## Core competencies for HyperTwist work

A coding model working on HyperTwist should still be able to:

- inspect simulation engines
- understand move/state notation
- inspect replay and trainer code
- inspect recognition stacks
- reason about progression/coaching systems
- distinguish educational UX from simulation correctness
- propose Unreal-native implementation paths

## Immediate next move

The next correct skillization sequence is:

1. skill registry/manifest contract
2. settings/menu/off-state controls
3. permissive analyzer wrappers
4. clean-room command-contract specs for restrictive lanes

Broader memory, provider, and domain skill widening should wait until that
base exists.
