repo-layout

ult-repo-layout

(Frontmatter name: is the bare repo-layout — ult is this skill's namespace:, composed into the folder name and every invocation below. Same pattern elsewhere in this repo, e.g. sec-threat-model's name: is threat-model.)

This skill implements the project layout and path-dependency configuration model (§15) and workspace-root consolidation (§16 — layout.workspace_root, scaffold-not-copy, and the layout-slots-registry.yaml superset registry), covering eleven path-slots:

• context_packages — read/written by ult-context-generate and every CONSUMING-CONTEXT-PACKAGE.md consumer. The only slot a real, shipped skill in this repo both produces and consumes.
• compiled_guidelines — written by compiling-project-guidelines, read by its own CONSUMING-COMPILED-GUIDELINES.md consumers. The registry's only kind: file slot until D21 §16.8/D24 Phase B added three more (below), and the first slot whose D21 default re-roots to a different bucket (inputs → cache).
• decision_ledger — written by ult-institutional-memory-distill's decision_ledger.py, read by ult-context-generate. A kind: file slot, same bucket re-root as compiled_guidelines.
• autoscaffold_content_state, autoscaffold_content_index — written by ult-autoscaffold-content's scaffold_state.py. Two more kind: file slots, same bucket re-root.
• plans_output, brainstorm_output, user_stories_output, security_docs, security_report, project_plan_docs — six further slots, all illustrative — not shipped in this repo (see the slot registry table below; rationale in references/phase-history.md).

...plus the project_guidelines starter-kit drop-zone — not a project_layout path-slot (no marker, no resolution algorithm), just a regenerated .pointer.md scaffold file. Read references/starter-kit-dropzones.md now and follow it if you're touching that mechanism.

Read references/phase-history.md for the full D20/D21 phase-by-phase build history and exit criteria — not needed to operate this skill day to day.

This file and others in this repo cite D<N>/§<N> labels (e.g. D21 §16.2) — see ../../../references/design-scratchpad-glossary.md for what each one means.

Alternative front-end: you can also view and (partly) drive this skill's state through a local browser wizard instead of re-reading context-config.yaml and the markers by hand — see ult-cep-wizard (D24). It's mostly a read-only status view, but it can trigger discover in place (its own freshness-hash-guarded POST /api/discover) and the mechanical half of init — slot scaffolding and the layout.workspace_root opt-in this section describes, via POST /api/init — before D20 has been initialized at all. It never asks for project_name/description, offers a rename-before-scaffold prompt, or runs confirm-layers/reconcile — those, and the fully conversational init, still happen here.