propose-customizationslisted

# Propose customizations Give a user who doesn't yet know exactly what to ask for a short, concrete, justified list of dashboards/skills/agents worth adding to *this* project — instead of an empty text box. ## When to use Whenever the Customize page's "Auto" button is used (for any of the three kinds), or the user asks directly ("what dashboards should I have?", "what skills am I missing?", "suggest an agent"). Always scoped to exactly **one kind** per run — dashboard, skill, or agent — never all three mixed into one list; if the trigger doesn't say which, ask (one question, per the usual clarify discipline). ## Method 1. **Read the project as evidence, not as a checklist to fill.** Depending on the kind: - *Dashboards*: read `specs/*.md`, `plans/*.md`, and skim the codebase's shape (what kind of project — app/infra/data/study, per `.spectoflow/capabilities.md`'s project-type table) for things worth a dedicated view — an architecture doc with no visual summary, a security review skill producing findings nobody dashboards, a spec whose acceptance criteria aren't tracked anywhere visible. - *Skills*: read `.spectoflow/agents/*.md` and `.spectoflow/skills/*` for capability gaps — a capability the project type implies (per `.spectoflow/capabilities.md`) but has no matching skill, or a recurring need visible in `plans/*.md`'s task titles/comments that no current skill covers. - *Agents*: read the current roster for capabilities with