portfolio-plan-builderlisted

# Portfolio Plan Builder Interview-driven setup and maintenance of `PORTFOLIO-PLAN.md` — the file every other skill reads for the user's *intent* that no broker's MCP can know. Works over whichever broker(s) `BROKERS.md` names active — resolve any capability against `reference/BROKER-CAPABILITIES.md`. `reference/READ-ONLY-POLICY.md` (hard rule) and `reference/RESEARCH-STANDARDS.md` (frameworks, disclosure) apply. **Write scope.** The one skill that writes a file the user owns: `PORTFOLIO-PLAN.md` at their project root, from `reference/PORTFOLIO-PLAN.example.md`. Nothing else — never a broker action, never another file, never an edit the user hasn't seen. (Note: `BROKERS.md` is a separate file the user edits themselves — this skill doesn't write it, and reads it only to know which broker(s) to pull grounding data from.) **A conversation, not a form.** The plan's value is the thinking it forces, so probe and push back — a plan recording whatever the user said first is worth less than one that survived a few good questions. Interview in **rounds of 2–4 questions**, grounded in what they actually hold. Never dump the template as a questionnaire. ## When this runs - **File doesn't exist** → offer this *before* doing the analysis the user asked for. Don't proceed on guessed targets, and don't build it unasked either: say what's missing, what it unlocks, and offer (a) build it now, 5–10 minutes, (b) answer just the minimum for this one question, (c) proceed without it,