buildanything 2.0.0 → 2.1.2

package/commands/idea-sweep.md

@@ -102,7 +102,7 @@ organized by theme. Include direct quotes where the user's exact words matter.]
 
 1. **market-intel agent** — Research market size (TAM/SAM/SOM), competitive landscape (5-10 players), timing/macro trends, and market structure for this idea: [paste SCQA]. Founder context: [paste Context Brief]
 
-2. **tech-feasibility agent** — Evaluate technical architecture, hard problems, build-vs-buy decisions, MVP scope, and stack recommendation for this idea: [paste SCQA]. Founder context: [paste Context Brief]
+2. **tech-feasibility agent** — Evaluate technical architecture, hard problems, build-vs-buy decisions, scope, and stack recommendation for this idea: [paste SCQA]. Founder context: [paste Context Brief]
 
 3. **user-research agent** — Analyze target user persona, jobs-to-be-done, current alternatives, behavioral barriers to adoption, and activation metrics for this idea: [paste SCQA]. Founder context: [paste Context Brief]
 
@@ -157,7 +157,7 @@ Write a markdown document titled `# [IDEA NAME] — Decision Brief` with these s
 - **Critical Tensions** — 2-3 contradictions that must be resolved during build
 - **Kill Criteria Status** — Table: Criterion | Status (CLEAR/AMBER/RED) | Evidence
 - **Recommended Action** — One of: GO (proceed to brainstorming), PIVOT (adjacent opportunity), INVESTIGATE (specific questions), KILL (reason)
-- **If GO: MVP Definition** — Core value prop, primary user, MVP scope (under 50 words), revenue model, first 1,000 users channel, tech stack, first milestone
+- **If GO: Product Definition** — Core value prop, primary user, feature scope (under 50 words), revenue model, first 1,000 users channel, tech stack, first milestone
 
 Save this document to `docs/briefs/` with today's date and a slug of the idea name.
 

package/commands/setup.md

@@ -6,7 +6,7 @@ description: "Install buildanything's external dependencies — tsx, companion p
 
 You are installing buildanything's external dependencies. The plugin itself is already installed (that's how this command is running), but the companion plugins, CLI tools, and skills it depends on are not — they need to be installed separately. This command does that in one shot.
 
-**iOS project?** If the user's intent is to build an iOS app, also run Steps 7–9 below. Skip them otherwise.
+**iOS project?** If the user's intent is to build an iOS app, also run Steps 8–10 below. Skip them otherwise.
 
 Run every step below. Each step is idempotent: check first, install only if missing, continue on failure. Collect results as you go and report them all at the end.
 
@@ -50,9 +50,20 @@ Run `npx skills add vercel-labs/agent-browser`. Record `installed` or `failed`.
 
 Run `npx skills add vercel-labs/agent-browser --skill dogfood`. Record `installed` or `failed`.
 
+### Step 7 — Install design.md linter (web/iOS Phase 3 lint gate)
+
+`@google/design.md` is the linter that runs at Phase 3 Step 3.8 to validate `DESIGN.md`. It is pinned as a devDependency in `package.json` so lint behavior is reproducible across runs.
+
+1. Check if installed: `npm ls @google/design.md` from the plugin root. If listed, record `already installed` and continue.
+2. Otherwise run `npm install --save-dev @google/design.md` from the plugin root. Record `installed` or `failed` based on exit status.
+
+A missing linter does NOT block Phase 0/1/2 — it only fails Phase 3.8 with a "linter spawn failed" stderr that names the install command. The plugin keeps working without it.
+
+Note: the lint hook (`hooks/design-md-lint.ts`) auto-installs the pinned version on first use if it's listed in `package.json` devDependencies but missing from `node_modules`. This means setup is technically optional for design.md — the first Phase 3.8 will install on demand (~5-15s, one-time). Setup pre-installs to avoid that delay during a build.
+
 ---
 
-## Step 7: Install iOS MCP servers _(iOS only)_
+## Step 8: Install iOS MCP servers _(iOS only)_
 
 For each MCP server below, run `claude mcp list` first. If the name already appears, record `already configured`. Otherwise run the install command and record `configured` or `failed`.
 
@@ -63,7 +74,7 @@ For each MCP server below, run `claude mcp list` first. If the name already appe
 
 If either fails: record the failure with the exact manual-install command.
 
-## Step 8: Install Maestro _(iOS only)_
+## Step 9: Install Maestro _(iOS only)_
 
 Maestro runs E2E flow YAML tests against a booted iOS simulator.
 
@@ -71,7 +82,7 @@ Maestro runs E2E flow YAML tests against a booted iOS simulator.
 2. Otherwise run `brew install maestro`. Record `installed` or `failed`.
 3. If `brew` is missing, record `skipped — install Homebrew first (brew.sh), then: brew install maestro`.
 
-## Step 9: Verify iOS toolchain _(iOS only)_
+## Step 10: Verify iOS toolchain _(iOS only)_
 
 Run `xcodebuild -version`. Record the version string. If not found, warn: "Xcode 26.3+ required — install from the Mac App Store."
 

package/commands/ux-review.md

@@ -103,8 +103,8 @@ iOS has no `/design-system` component gallery. The reference surface is **Apple
 
 The design board is GENERATED by `/buildanything:build` Phase 3 Step 3.1 — this command only READS it.
 
-- If `docs/plans/ios-design-board.md` does NOT exist: **HALT** and instruct the user to run `/buildanything:build` Phase 3 first. Do not regenerate here.
-- If it exists: use it as-is. Do NOT re-scrape references. **Cache rule:** to refresh the board, the user must delete `docs/plans/ios-design-board.md` and re-run Phase 3.
+- If `DESIGN.md` does NOT exist: **HALT** and instruct the user to run `/buildanything:build` Phase 3 first. Do not regenerate here.
+- If it exists: use it as-is. Do NOT re-scrape references. **Cache rule:** to refresh the board, the user must delete `DESIGN.md` and re-run Phase 3.
 
 ### Step 3: Capture Current State
 
@@ -128,7 +128,7 @@ e. **`skills/ios/writing-for-interfaces`** — microcopy + tone review. Audit bu
 
 ### Step 5: Compare Against Design Board
 
-Diff live simulator screenshots against `docs/plans/ios-design-board.md`:
+Diff live simulator screenshots against `DESIGN.md`:
 - Where does the live app match the board's vibe / patterns?
 - Where does it drift (color, spacing, hierarchy, type, navigation model)?
 - Which board patterns are NOT yet implemented but should be?

package/commands/verify.md

@@ -28,9 +28,12 @@ Check the user's argument:
 | `security` | Check 5 only |
 | `diff` | Check 6 only |
 | `behavioral` | Check 7 only |
+| `static` | Checks 1, 2, 3, 6 (build + types + lint + diff — Phase 6 post-metric-loop) |
 
 Multiple scopes can be combined: `tests security` runs checks 4 and 5.
 
+The `static` macro is used by Phase 6 after the metric loop has already evaluated behavioral quality — see `protocols/verify.md` Step 2 "Scope macros".
+
 ## Step 2: Run the Verification Protocol
 
 Follow `protocols/verify.md` exactly: