Repository navigation
Keep the interview's questions and answers in the Brief, and route short build requests - #189
Merged
Merged
Conversation
…ort build requests domain-interview now writes every question it asked, with the user's answer as given, into a new Interview record section at the end of the brief's spec, starting with the routing question. Answers are still folded into the sections, and the sections win; the record is the trail behind them, and shows the build which answers were the user's and which were decided for them. The rule against a separate log now says the same. index.md gains the routing question for short build requests: Just build it, Plan it with me first, or I already have a brief or a design. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Staging Workspace Sync SuccessfulSuccessfully synced changes to staging workspace Sync Details |
lucaslyl
marked this pull request as ready for review
October 8, 2026 07:05
lucaslyl
added a commit
that referenced
this pull request
Oct 8, 2026
…and #189's interview record Brings in main (including #184's sample images), takes #188's versions of layout-vocabulary.md and layout-gravity.md, and #189's interview record in domain-interview, its brief template and glossary entry, and its routing skip sentence in index.md. Conflicts keep #151's fuller text and add the newer lines into it. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
richardhjtan
approved these changes
Oct 8, 2026
lucaslyl
added a commit
that referenced
this pull request
Oct 8, 2026
…ayout token fix Main now carries #188 and #189 and the layered-surface / edge-overlap token fix. The layout files and their glossary and SKILL.md lines take main's wording; index.md and the domain-interview field table keep this branch's fuller text, which names the Look check and motion-authoring. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Linear: ECO-596
Why
A brief keeps what the interview decided, but not the interview itself. Reviewing how an interview went meant scrolling the chat, and the building AI could not tell which parts of the brief were the user's answers and which were decided for them (only skipped questions were listed, under Assumptions).
Main also lacks the routing question that sends a short build request ("create me a landing page", "build a CRM") to the interview at all; it lives only in #151.
What changes
domain-interview: every question asked goes into a new## Interview recordat the end of the brief'sspec, in order, with the answer as the user gave it (the option picked, "(Recommended)" kept when it carried it, or the typed text in full). It starts with the routing question. Skips point to## Assumptionsinstead of repeating the decision.brief-template.mdends with the record table; the glossary'sdomain-interviewentry mentions it.index.md: the routing question from The design pipeline skills — interview, direct, author motion, review #151 (Just build it / Plan it with me first / I already have a brief or a design), without its pointer toboxel-design's Look check, which is not on main yet.Tested
A simulated user typed "create me a landing page", picked "Plan it with me first", typed one answer, skipped one question and then the rest. The routing question appeared, and the brief card's record matched the conversation row for row: the routing answer, the typed text in full,
SkippedandSkipped the rest, each skip's decision under Assumptions. The card indexed with no errors.Not covered
🤖 Generated with Claude Code