The Atlas doc.haus documentation, bound to its code
180 documents
dochaus/skill/firm-profile/references/interview.md

Cold-start interview

The interview populates a new .dochaus/profile.md (or fills the gaps in an existing one). It is a short guided conversation, not a questionnaire: ask one section's batch per turn, in the order below, and never re-ask anything already answered or pre-filled.

Before asking anything, mine what the matter already holds:
  1. Read matter.json for the matter's jurisdiction packs — these are the starting candidates for Jurisdiction Defaults.
  2. search-document across the uploaded documents for governing-law and venue clauses, dispute-resolution clauses, limitation-of-liability figures, and signature blocks — these reveal the firm's actual positions and who signs.
  3. Skim one or two documents (read-document) for style: plain English or traditional drafting, "shall" vs "must", how defined terms are introduced, date and numbering formats.

Turn every solid finding into a confirmable default rather than an open question — "Your engagement letter is governed by the law of England and Wales; use that as the default for new documents?" — and cite where it came from as [<Document> § <section>]. Ask cold only where the documents are silent. Pre-filled answers are still answers the lawyer must confirm; nothing enters the profile unconfirmed.

1. Confirm a compact summary: every section, every answer, in the words that will go into the file. An unanswered question is recorded as `Not specified`, never guessed. 2. Write the confirmed profile to `.dochaus/profile.md` in the matter directory, using the skeleton in SKILL.md, creating `.dochaus/` if needed. If you cannot write files, output the complete file in one fenced block labeled with that path for the lawyer to save. 3. Report: name the path, list anything left `Not specified`, and remind the lawyer the profile is plain markdown they can edit directly at any time.