create-team-foundry 2.1.0 → 2.1.2

package/dist/index.js

@@ -2224,9 +2224,16 @@ After the last question, do the following:
 2. **List what's still a gap.** Name each empty or partially-filled file and the specific
    missing piece. Don't apologize for the gaps \u2014 state them neutrally.
 
-3. **Suggest one next action.** The single most valuable thing the team could do to improve
-   their team-foundry right now. Usually: fill the most important gap, or schedule a
-   customer conversation if customers.md is thin.
+3. **Suggest one next action and offer to start it now.** If any files are still empty
+   or gap-only, name the single most valuable one and immediately offer to fill it:
+   > "Want to start with [most valuable gap]? That's usually the highest-leverage first
+   > fill \u2014 everything else references it."
+   Default priority: customers (shapes all other files) \u2192 outcomes (most time-sensitive)
+   \u2192 north star (grounds the coach) \u2192 stack (engineering context).
+   Wait for the user to say yes or choose a different file. If they say yes, proceed
+   directly to the interview questions for that file as defined in the interview section
+   above \u2014 do not re-run the full interview. If they decline, proceed to step 4.
+   If all files are populated, skip this offer and proceed directly to step 4.
 
 4. **Offer the coach.** End with:
    > "Your team-foundry is set up. You can ask me to review it any time by saying

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-team-foundry",
-  "version": "2.1.0",
+  "version": "2.1.2",
   "description": "Scaffold a team-foundry into any repo — structured context files for Claude Code, Gemini CLI, and Cursor",
   "license": "MIT",
   "type": "module",