improvements when single branch uses multiple projects

see if gstack can be improved when a single branch host multiple products as we do.

LOGS::::::

when i started plan-eng-review skill i got message "That design doc is for Entropy Chess, not Memory Log. Not relevant here. Let me investigate the two Android issues directly."

why that happened? why it did not find design doc for memorylog?

Find DESIGN.md references
Find DESIGN.md references

Good question. The agent found the root cause.

Short answer: The /plan-eng-review skill doesn't know which product you're in. It only knows the monorepo name and the git branch. So when it looked for a cached design doc, it grabbed the most recent one for production branch across the entire monorepo, which happened to be an Entropy Chess design doc from a previous session.

The mechanism:

The skill locates design docs like this:

SLUG=moblizeit-code-repo # monorepo-level, not product-level
BRANCH=production
ls -t ~/.gstack/projects/$SLUG/*-$BRANCH-design-*.md | head -1

It found ~/.gstack/projects/moblizeit-code-repo/moblizeit-production-design-20260328-085239.md, which was an Entropy Chess admin dashboard design doc from a previous session. Since all your products share the same repo and the same production branch, the skill can't tell them apart.

What it should have done: Read the local products/memorylog/DESIGN.md that's right there in the product directory. But the skill only checks ~/.gstack/projects/ for design docs generated by /office-hours, not the product's own DESIGN.md file.

Why it didn't break anything: The skill correctly detected the mismatch ("That design doc is for Entropy Chess, not Memory Log") and ignored it. So it recovered gracefully, but the initial confusion is real.

The fix would be in gstack itself... the slug system needs to be product-aware in monorepos. Either index design docs by {slug}-{product} instead of just {slug}, or fall back to reading the local DESIGN.md from the current working directory. That's a gstack bug, not a project bug.

Start with the /plan-eng-review skill and the slug-based lookup under ~/.gstack/projects. Compare that lookup with the local products/memorylog/DESIGN.md path described in the issue. Done means a branch containing multiple products selects the relevant product design rather than an unrelated document such as Entropy Chess.

Written by the indexing model from the issue text.