create-team-foundry 2.1.1 → 2.1.3

package/dist/index.js

@@ -1685,10 +1685,21 @@ fields. If the user says "looks good," proceed immediately to Step 4.
 
 ### Step 4 \u2014 Write files
 
-Write all team-foundry files using confirmed data. For any field with no signal and
-no user-provided answer, write a \`<!-- GAP: ... -->\` marker. Follow the
-conversation-as-update protocol \u2014 show each file draft and wait for confirmation
-before writing.
+Write **all** team-foundry files that have at least one confirmed signal. Do not skip
+files just because they were not mentioned in the pre-fill summary \u2014 if the repo scan
+gave you data for a file, populate it now.
+
+Signal-to-file mapping (use this to decide what to write):
+- Stack (language, framework, dependencies from manifest file) \u2192 \`team-foundry/engineering/stack.md\`
+- Product name + what it does (README) \u2192 \`team-foundry/product/north-star.md\` (name field)
+- Recent commit messages \u2192 \`team-foundry/product/outcomes.md\` (inferred focus areas \u2014 frame as customer outcomes, not shipped features)
+- Open issues / PRs \u2192 \`team-foundry/product/assumptions.md\` (open bets, if full profile)
+- \`team-foundry/product/customers.md\` \u2014 no repo signal; write gap marker, surface in Step 5
+- Root instruction file \u2014 always write/update with product name and stack summary
+
+For any field with no signal and no user-provided answer, write a \`<!-- GAP: ... -->\`
+marker. Follow the conversation-as-update protocol \u2014 show each file draft and wait
+for confirmation before writing.
 
 **No silent writes.** Even high-confidence pre-filled answers require explicit
 confirmation before being written to disk. "Looks good" or "yes" is confirmation.
@@ -2224,14 +2235,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 and offer to start it now.** Name the single most valuable
-   gap and immediately offer to fill it:
+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, begin the
-   relevant questions immediately without re-running the full interview.
+   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 the "Offer the coach" step below.
+   If all files are populated, skip this offer and proceed directly to the "Offer the coach" step below.
 
 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.1",
+  "version": "2.1.3",
   "description": "Scaffold a team-foundry into any repo — structured context files for Claude Code, Gemini CLI, and Cursor",
   "license": "MIT",
   "type": "module",