buildpartner 0.3.9 → 0.3.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "buildpartner",
-  "version": "0.3.9",
+  "version": "0.3.10",
   "type": "module",
   "description": "Your AI build partner. Expert guidance inside Claude Code.",
   "bin": {

package/skills/bp-interview/SKILL.md

@@ -1,6 +1,6 @@
 # /bp-interview
 
-Get to know how I work. Quick Q&A that teaches BuildPartner your role, stack, and preferences. Every skill gets better after this.
+Build your profile so every skill knows who you are. Quick conversation, not a form. 2-3 minutes.
 
 ## MCP Tools
 
@@ -8,31 +8,36 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
 
 ## Instructions
 
-1. Call `get_personal_context` with `{ "include_sessions": true }` to get context on how the user works.
+1. Call `get_personal_context` with `{ "include_sessions": true }` to see how the user actually works.
 
-2. Use the session data to personalize your questions. Conduct a conversational interview, asking one question at a time. Cover:
+2. Use their session data to skip obvious questions. If you can see they code in TypeScript with Next.js, don't ask "what's your tech stack?" If they have 300 sessions, don't ask if they're new to Claude Code.
 
-### About you
-- "What's your role? What do you do day to day?"
-- "What are you building right now?"
-- "What's your tech stack?"
+3. Run a conversational interview. One question at a time. Make it feel like a real conversation, not a survey. The goal is to understand who this person is, what they care about, and where they're headed.
 
-### How you work
-- "How do you typically start a coding session? Plan first or dive in?"
-- "Do you prefer Claude to be concise or detailed?"
-- "How do you like feedback? Direct or gentle?"
+### Who they are
+- "What are you building right now, and why does it matter to you?"
+- "Is this a solo thing or do you have a team?" (only if not obvious from context)
+- "What got you into building? What's the origin story?"
 
-### Your goals
-- "What's the one thing you wish Claude Code did better for you?"
-- "What takes too long in your workflow right now?"
+### Where they're going
+- "Where do you want to be in 5 years? What does the ideal version of your work life look like?"
+- "What's the biggest thing standing between you and that?"
+- "If you could mass-produce one skill or ability in yourself, what would it be?"
 
-3. Rules:
+### How they like to work
+- "When Claude responds, do you want it concise or detailed?"
+- "If something in your code is wrong, do you want me to call it out directly or be diplomatic?"
+- "What do you wish Claude did differently?"
+
+4. Rules:
    - Ask ONE question at a time
-   - Read the room. Short answers = keep it tighter. Sharing a lot = go deeper
-   - Aim for 8-12 questions total
-   - If the user says "done" or wants to stop, respect that immediately and save what you have
+   - Read the room. Short answers = keep it tighter. Long answers = follow up and go deeper
+   - Skip questions you can already answer from their data
+   - 6-10 questions total. Quality over quantity
+   - If the user says "done" or wants to stop, save immediately with what you have
+   - Don't be robotic. React to what they say. Be a person, not a form
 
-4. After the interview, save EVERYTHING in ONE single `save_profile` call. ONE call, ALL sections:
+5. After the interview, save EVERYTHING in ONE single `save_profile` call. ONE call, ALL sections:
 
 ```json
 {
@@ -41,14 +46,15 @@ Only call tools that are registered on the `buildpartner` MCP server. If a tool
     "preferences": { "response_style": "...", "code_style": "...", "decision_making": "...", "feedback_style": "..." },
     "tech_identity": { "role": "...", "primary_languages": ["..."], "frameworks": ["..."], "current_project": "..." },
     "work_patterns": { "session_style": "...", "planning_style": "...", "peak_hours": "from context", "peak_day": "from context" },
-    "personality": { "builder_type": "...", "learning_style": "...", "pain_points": ["..."], "goals": ["..."] }
+    "personality": { "builder_type": "...", "learning_style": "...", "pain_points": ["..."], "goals": ["..."] },
+    "vision": { "five_year": "...", "biggest_bottleneck": "...", "origin_story": "...", "superpower_wish": "..." }
   },
-  "signals": ["Summary of key insights"]
+  "signals": ["Summary of key insights about who this person is and what drives them"]
 }
 ```
 
-5. Show the completed profile, then ask: "Anything look wrong? I can update any section."
+6. Show the completed profile, then ask: "Anything look wrong? I can update any section."
 
-6. End with: "Your profile is saved. Every BuildPartner skill now personalizes to you."
+7. End with: "Your profile is saved. Every BuildPartner.ai skill now personalizes to you."
 
-7. Call `check_status` with `{ "skill_name": "bp-interview" }`.
+8. Call `check_status` with `{ "skill_name": "bp-interview" }`.