Files
claude-skills/.tasks/bootstrap-projects-meta-trigger.md
vitya b12039720d feat(project-bootstrap): v1.2.0 — auto-load using-projects-meta in bootstrapped projects
CLAUDE.md template gains a fifth trigger line, `check across all projects`
(verbatim phrase from `using-projects-meta` description). Every new or
upgraded project now auto-loads cross-project task aggregation and shared
projects-wiki access without an explicit verbal trigger.

No Step 5.7 mirror of Step 5.6 (superpowers plugin recommendation):
`using-projects-meta` Prerequisites already self-corrects to
`setup-projects-meta` when MCP tools are missing.

Synced: assets/CLAUDE.md.template, inline copy in SKILL.md (Step 5),
README.md + README.ru.md trigger lists, this repo's local CLAUDE.md,
dist/project-bootstrap.skill, .wiki/concepts/projects-meta-skills.md
(Bootstrap trigger section), .wiki/log.md.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-30 01:02:06 +03:00

31 lines
2.7 KiB
Markdown

# bootstrap-projects-meta-trigger
## Goal
Add `check across all projects` to the CLAUDE.md template that `project-bootstrap` writes to every project, so the `using-projects-meta` skill auto-loads in every bootstrapped repo (current set already had four triggers — `talk like a caveman`, `use superpowers`, `use project wiki`, `use task management system`, plus `we're on Windows`). Bumps `project-bootstrap` 1.1.0 → 1.2.0 (additive default-artifact change).
## Key files
- `skills/project-bootstrap/assets/CLAUDE.md.template` — the file actually copied into bootstrapped projects
- `skills/project-bootstrap/SKILL.md` — inline copy of the same template (must stay in sync) + version frontmatter
- `README.md` / `README.ru.md` — the "Using skills in projects" section enumerates the trigger list
- `CLAUDE.md` (this repo) — local instance must also gain the line so the trigger fires here too
- `dist/project-bootstrap.skill` — packaged artifact, rebuilt from the source tree
## Decisions log
- 2026-04-30: trigger phrase = `check across all projects` — buffer-direct quote from `using-projects-meta` description, matches existing imperative style of other lines (`use X`, `talk like X`).
- 2026-04-30: not adding a Step 5.7 mirror of Step 5.6 (recommend `setup-projects-meta`) — out of scope for this task. Trigger fires `using-projects-meta` whose Prerequisites already point at `setup-projects-meta` if MCP tools are missing. Open question for follow-up.
## Open questions
- [ ] Should `project-bootstrap` also detect missing `mcp__projects-meta__*` tools and recommend `setup-projects-meta` (analogous to Step 5.6 for superpowers)? Defer until we see a fresh-machine bootstrap miss the dependency.
## Completed steps
- [x] task entry created
- [x] `skills/project-bootstrap/assets/CLAUDE.md.template` — added `check across all projects` between `use task management system` and `we're on Windows`
- [x] `skills/project-bootstrap/SKILL.md` — inline template at Step 5 synced; explanatory paragraph added; `version: 1.1.0 → 1.2.0`
- [x] `README.md` + `README.ru.md` — trigger list in "Using skills in projects" / "Использование в проектах" updated
- [x] `CLAUDE.md` (this repo) — local instance gained the new line so the trigger fires here
- [x] `bash scripts/install.sh project-bootstrap` — reinstalled to `~/.claude/skills/project-bootstrap/`
- [x] `bash scripts/build.sh project-bootstrap``dist/project-bootstrap.skill` rebuilt
- [x] verified: installed `version: 1.2.0`, template content matches
- [x] `.wiki/concepts/projects-meta-skills.md` — appended "Bootstrap trigger (project-bootstrap@1.2.0)" section explaining choice of phrase + non-decision on Step 5.7
- [x] `.wiki/log.md``decision` entry added