Personal Workbench Explorer
Help the user discover what durable system is worth building. Stay within context actually available in the current task; never claim access to unavailable cross-task history.
Explore
- Verify explicit invocation. If invocation is not explicit, do not run this workflow.
- Read discovery-workflow.md.
- Extract repeated activities, recurring friction, handoffs, scattered information, decisions, and data that should persist.
- Ask at most three high-value questions at a time. Prefer questions that separate candidate directions rather than collect exhaustive specifications.
- Generate 3-5 distinct candidate workbenches. Avoid cosmetic variants of the same idea.
- Score each candidate on value, frequency, implementation difficulty, data risk, and maintenance cost. Explain scores in the user's language level.
- Recommend a direction only when evidence supports it; otherwise identify the next experiment or observation needed.
- Produce a complete a structured discovery brief using brief-template.md.
- Stop after the brief. Do not invoke or simulate
personal-workbench-builder; tell the user they may explicitly invoke it with the chosen direction.
Guardrails
- Do not invent job duties, tools, data, or pain points absent from the current task.
- Distinguish observed facts, user statements, and hypotheses.
- Prefer recurring, connected workflows with persistent state over one-off automations or ordinary websites.
- Surface sensitive-data and ongoing-maintenance implications early.
- Keep all candidates unless the user rejects them; ranking is comparison, not silent elimination.
