scaffold

Using this skill: announce "Using scaffold", make a todo per numbered step in ## Steps, and do not skip the gates. This skill's worth is its process, not a hand-reproduced outcome. If you were told to "run scaffold", run it, do not improvise its result. (Suite standard: https://github.com/horizon-foundry/foundry/blob/main/reference/skill-authoring.md)

Overview

A project starts in the shape it will need at the end of its life. That shape depends on what the project is. This skill first declares the project's profile. Then it stands up the doc set, posture, and deploy or publish path that profile needs, filled from a few setup answers the builder supplies. User-invoked. The doc set is defined by the suite's doc-set spec, reference/doc-set-spec.md in the repo; an install ships only this skill's directory, so from anywhere else read it at https://raw.githubusercontent.com/horizon-foundry/foundry/main/reference/doc-set-spec.md. The skill is self-contained: no external template repo is required (the skeletons below are the normative fallback).

An existing project is also in a "scaffold needed" state if its docs still contain {placeholder} markers. The same flow applies.

When NOT to use

• The doc set exists and has drifted: that is document reconcile. scaffold re-runs only for graduation (a profile change) or leftover {placeholder} markers.
• The question is whether to build it or who it serves: frame audits declared intent; scaffold assumes a confirmed frame.
• The project is approaching a release decision: foundry and production-audit own that moment.
• The next unit of work needs a plan: phase-plan; scaffold only seeds the chain's first block.

Profiles