Problem
If a user does three similar scaffolding handoffs per week, they re-answer the same 9 guided questions each time. No memory across invocations.
Why it matters
Even after G7 compresses guided mode, repeated handoffs still have boilerplate. A named profile removes that boilerplate entirely.
Approach
- Profiles stored at `~/.gstack/ghcp-profiles/.json` — contains default streams, boundaries, NOT-in-scope, forbidden deps, PR sections
- `/ghcp-handoff --profile scaffold "project X for use-case Y"` — loads profile, only asks for the task-specific bits
- `/ghcp-handoff --save-profile ` — after a successful handoff, save the current inputs as a reusable profile
- `/ghcp-handoff profiles list | delete ` — management
Review reference
Adversarial review G16 (and T7 — they were the same item)
Problem
If a user does three similar scaffolding handoffs per week, they re-answer the same 9 guided questions each time. No memory across invocations.
Why it matters
Even after G7 compresses guided mode, repeated handoffs still have boilerplate. A named profile removes that boilerplate entirely.
Approach
Review reference
Adversarial review G16 (and T7 — they were the same item)