kh-uaf - SKILL.md Agent Skill

name: kh-uaf description: Use FIRST before non-trivial Antigravity-style workspace work such as memory lookup, target or sibling folder inspection, project file edits, code changes, deliverables, long logs, reviews, QA, verification, subagents, persistent state, or high-risk actions, even when the user did not name KH UAF.

KH UAF

This workspace includes KH UAF, a personal skillbook and Python-first orchestration harness for domain-general agent workflows.

How to Use

Treat the repository root as the packaged UAF source, not as the target project's runtime state folder.
For non-trivial work, run KH front-door auto routing before memory lookup, target/sibling folder scans, source exploration, or edits even when the user did not name KH, UAF, skill, harness, plugin, front door, router, or catalog. Keep simple direct questions cheap after intake classifies them as light.
Prefer the executable front-door command so stale plugin cache paths and passive skill-list mentions do not count as usage:

python -m src.orchestration.kh_front_door --prompt "<user request>" --project "<target project>" --host antigravity --summary

If the command is unavailable, read always-on-front-door, automatic-intake-harness, SKILL.md, plugin-composition-policy, request-complexity-router, or the packaged skill catalog to classify the request and select the minimal skill bundle automatically. Users should not need to name every harness.
If front-door returns execution_gate.can_execute=false, do not continue with global Codex MEMORY.md lookup, .codex/memories/skills/... lookup, cross-chat/subagent memory reuse, sibling-folder reads, implementation, deliverable generation, verification, or browser QA. Satisfy the gate first, especially blocked_until_brainstorming_handoff.
Record selected, considered, skipped, and blocked skills with evidence; then start source reads, edits, role DAG execution, or deliverable generation only when execution_gate.can_execute=true or the gate has explicit handoff evidence.
Before delegating non-trivial work to a subagent, the controller should run front-door intake and pass a bounded task packet. A subagent should also run front-door first for its own non-trivial task before memory lookup or workspace inspection. After the subagent returns, audit whether the selected skills were actually used, skipped with rationale, or missing.
Use README.md for install and host integration instructions.
Validate the skill pack before relying on it:

python -m src.skills.uaf_skill_catalog --check

For large project, SaaS, app, multi-file implementation, role-DAG, or long-running work, create large_work_orchestration_bundle evidence before implementation. Its skill_statuses must account for routing, host orchestration, GoalState, lifecycle, token optimization, memory, parallel strategy, subagent review, role execution audit, Compound, and workflow distillation as applied, considered_not_needed, skipped_with_rationale, or blocked, with application_mode set to runtime, procedural, considered, or blocked.

If a KH-capable session starts non-trivial source/work commands before this front-door evidence exists, treat it as a P1 missing_front_door failure in session-skill-audit, unless the request was classified as light/direct or KH was not selected.

If a host-provided KH skill path points to a missing old plugin cache version, stop using the stale path. Resolve the current repository skills/ folder or latest installed kh-uaf cache, then re-run front-door routing before claiming skill use.

Useful Entry Points

skills/: packaged UAF skill and harness folders.
src/: Python contracts, dispatchers, DAG role orchestrator, role artifacts, evidence gates, retention helpers, goal ledger, memory store, and task runners.
%LOCALAPPDATA%/KH-UAF/: default runtime state for .uaf and snapshot data.
docs/: target-project user-facing deliverables routed by task type, such as standard-template software functional specification, development design, API/data/test artifacts, documentation-grade general orchestration DOCX/XLSX files, conditional revision-managed manuals, investment analysis workbooks, and product-design SVG/DXF handoff artifacts.
deliverable_exports.quality and role_execution_audit: metadata-only harness outputs for template quality, render QA, traceability rows, and role DAG execution audit. Do not write these harness-only reports into docs/ unless the user explicitly asks for them as deliverables.
docs/skillbook/: design notes, plans, and handoff decisions.

UAF Commands

python -m src.skills.uaf_skill_catalog --list
python -m src.skills.uaf_skill_catalog --read always-on-front-door
python -m src.skills.uaf_skill_catalog --read goal-state-harness
python cli.py run --project ./my_app --prompt "Plan and implement the requested work"