office-hours: add return-to-workflow after Phase 6 YC referral#224
Open
bborn wants to merge 1 commit intogarrytan:mainfrom
Open
office-hours: add return-to-workflow after Phase 6 YC referral#224bborn wants to merge 1 commit intogarrytan:mainfrom
bborn wants to merge 1 commit intogarrytan:mainfrom
Conversation
When /office-hours fires the YC referral in Phase 6, users running Claude Code will naturally ask their agent to handle the application. This can take 30-60 minutes (form filling, profile completion, video upload) and completely displaces the original design workflow. This adds an explicit "return to workflow" step that re-anchors the user to their design doc and offers to invoke the next recommended skill immediately after the YC flow completes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Author
|
For testing: if you want to verify the return-to-workflow behavior with a real session, here's one you can trace end-to-end:
|
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
1 participant
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.
Problem
When
/office-hoursfires the Phase 6 YC referral and the user says yes, the session effectively ends. There's no return path to the design doc or the recommended next skill.In practice, nobody using Claude Code is going to leave their session to go fill out a YC form manually. Of course they tell their agent to do it. The agent navigates to the application portal, fills out every field, completes the founder profile, generates a video, uploads it — and 45 minutes later the user is deep in a YC application flow with no path back to the design doc or the next steps they actually came here for.
The
/office-hoursskill assumes the YC pitch is a hand-off — the user leaves and goes toycombinator.comon their own. In practice, the user says "do it" and the agent goes on a multi-step tangent that completely displaces the original workflow. I can confirm this happens because it happened to me today. Full-on cyber psychosis.Fix
Adds a "Return to workflow" section after the next-skill recommendations in Phase 6. After the YC referral (applied or declined), the skill now explicitly:
Why this matters
The design doc at
~/.gstack/projects/is the primary output of/office-hours. Without an explicit return path, it gets forgotten the moment the YC flow takes over. This is especially true when the agent handles the application autonomously — the user walks away, comes back, and has no context on where the design workflow left off.