diff --git a/.tasks/STATUS.md b/.tasks/STATUS.md
index 5f86051..b9e2339 100644
--- a/.tasks/STATUS.md
+++ b/.tasks/STATUS.md
@@ -93,6 +93,15 @@ _Updated: 2026-04-30_
 **Next action:** when triggered (skill count crosses threshold), evaluate variant B (grouped by family) vs variant C (flat + manifest) from the original brainstorm in `.wiki/concepts/repo-layout.md`
 **Branch:** (not started)
 
+---
+
+## ⚪ [bootstrap-recommend-projects-meta] — Step 5.7 in project-bootstrap: recommend `setup-projects-meta` if MCP tools missing
+**Status:** ready
+**Where I stopped:** (not started) — opened as follow-up to `[bootstrap-projects-meta-trigger]` (commit b120397). The `check across all projects` trigger is now in every CLAUDE.md template, but on a fresh machine without `projects-meta-mcp` registered the trigger is silently no-op until the user verbally asks for cross-project work
+**Next action:** mirror Step 5.6 (superpowers plugin check). Detect missing `mcp__projects-meta__*` tools — possible signals: parse `~/.claude.json` for `mcpServers.projects-meta` key, or check for `~/.local/projects-meta-mcp/dist/server.js`. If absent, print one-shot recommendation block in chat with `setup-projects-meta` invocation hint. Hard rule: never auto-install. Bump project-bootstrap 1.2.0 → 1.3.0
+**Branch:** (not started)
+**Blocker:** waits on observing a real fresh-machine bootstrap that silently misses the dependency — defer until we see the failure mode in practice
+
 ## 🟢 [using-projects-meta-freshness-gate] — добавить Step 0 freshness check в using-projects-meta
 
 **Status:** done