repo-layout

# ult-repo-layout **Status: implemented — all 8 phases complete.** This skill implements `context-engineering/CONTEXT-ENGINEERING-DESIGN.md` §15 ("Project Layout and Path-Dependency Configuration") and §16 ("Workspace Root Consolidation" — `layout.workspace_root`, scaffold-not-copy, and the `layout-slots-registry.yaml` superset registry), covering **eight** 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, and the only slot whose D21 default re-roots to a different bucket (`inputs` → `cache`). - `plans_output`, `brainstorm_output`, `user_stories_output`, `security_docs`, `security_report`, `project_plan_docs` — six further slots that prove the same registry/marker mechanism scales past one owner. Their producer/ consumer skills (`example-plan-writer`, `example-brainstorm-writer`, `example-consumer`, `example-threat-modeler`, `example-report-writer`, `example-project-planner`, etc.) are **illustrative — not shipped in this repo**; see the slot registry table below. ...plus **5 starter-kit drop-zones** — not `project_layout` path-slots (no marker, no resolution algorithm), just regenerated `.pointer.md` scaffold files. Read `references/s...