architect

Type /architect, optionally with the path to a precon scope doc. The skill locates the scope doc by globbing docs/scope/ and ~/Documents, then runs a short interview covering the walkthrough target, candidate structures, and one-way doors before writing the architecture doc.

A walkthrough target names one real person, a date, and the short list of things that person must be able to do in the first session. Every v0 component must point at a walkthrough requirement or it is cut, keeping the initial build minimal.

No. The skill only writes a markdown doc and a private HTML artifact. Provisioning belongs to /sunrise, which reads the poured-concrete list the architecture doc records; banked decisions are documented, never executed.

The skill opens a gate discussion about why it is running docless and proceeds only when that discussion lands on a reason, which is recorded in the doc header. A docless run skips the blind review offer since there is no brief to send.

On your explicit word, the skill sends only the precon scope doc to readers roster rows such as GPT, Gemini, or Claude with a fixed instruction to produce their own architecture take. Each disagreement is walked through one at a time and the doc changes only where you rule.

Skip it when there is no system at all, such as a single static page with no server or stored data. The exit-ramp question ends the interview immediately in that case, leaving only a tiny doc noting nothing needs provisioning.