Private
Public Access
feat(directives): add 15 engagement-specific directives + tags.toml entries
This commit is contained in:
@@ -0,0 +1,9 @@
|
||||
# ideation_leads_with_recommended
|
||||
|
||||
## v1
|
||||
|
||||
**Why this iteration:** New rule, no prior source. Companion to `design_leads_with_recommendation` but scoped to ideation (concept generation) rather than design (architecture selection).
|
||||
**Source:** new rule
|
||||
|
||||
---
|
||||
**Lifted:** 2026-07-05
|
||||
@@ -0,0 +1,14 @@
|
||||
# Ideation sessions lead with a recommended concept + the reasoning, not 3 unranked options
|
||||
|
||||
## What it says
|
||||
|
||||
When an agent helps the user ideate new concepts, tools, or UX, the output MUST lead with a single recommended concept and the reasoning for why it is the best fit. The agent MAY present 2-3 alternatives after the recommendation, but the recommendation comes first with the reasoning.
|
||||
|
||||
## Why
|
||||
|
||||
"Here are 3 options, pick one" offloads the synthesis to the user. The user asked for ideation help, not a multiple-choice quiz. The agent has the context; the agent should make the call. The user can reject the recommendation, but starting from a recommendation is faster than starting from a blank list.
|
||||
|
||||
## See also
|
||||
|
||||
- `conductor/directives/design_leads_with_recommendation` — the brainstorming equivalent
|
||||
- `conductor/directives/exactly_four_completion_options` — completion options are different (they are structured choices, not ideation)
|
||||
Reference in New Issue
Block a user