القائمة
Deprecated alias — use /meeting --cross instead. Cross-project meeting: scan all registered projects' TODO.md files, surface the highest-priority item globally, and dispatch.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | meeting-cross |
| description | Deprecated alias — use /meeting --cross instead. Cross-project meeting: scan all registered projects' TODO.md files, surface the highest-priority item globally, and dispatch. |
Use /meeting --cross instead. This alias exists only during the transition period.
Removal trigger: delete this skill (dir + symlink) after /meeting --cross has been used successfully twice. See docs/meeting-notes/2026-06-11-0950-meeting-cross-as-cross-switch.md.
/meeting setup: run steps 1–7 in ~/.claude/skills/meeting/SKILL.md (find root → metadata → git hygiene check → format spec → personas → discoveries → profile → broker). Skip the --cross conditional at step 2 — this alias handles the cross path directly.~/.claude/skills/meeting/cross-mode.md and follow it for all project discovery, classification, dispatch, and routing-trail steps.Relay workflow that spends a strong reviewer-model turn (Opus apex; Fable optional bonus) preparing repos for cheaper executor sessions (Sonnet), then verifying their work. Two modes — handoff (write docs, roadmap, failing-test specs, BDD) and review (verify executor work isn't gamed, re-derive roadmap); plus `executor` to load the lean executor contract and `next` to auto-route the current repo. Trigger on "relay", "relay handoff", "relay review", "relay next", "relay executor", "hand off repos to executors", "review executor work". Keywords: relay, handoff, review, next, executor, checkpoint, ROADMAP, RELAY_LOG.
Hold a structured design meeting with multi-persona scrutiny on a non-trivial decision. Trigger when a TODO item has ambiguous scope, a design has non-obvious trade-offs, or two plausible approaches exist and the wrong choice is hard to reverse. Skip for bug fixes, one-liners, or already-decided features. With no subject, audits TODO.md and recent meeting notes to recommend a session.
Auto-commit, push, and write diary entry after every substantive prompt. Trigger on ANY code change — this is a mandatory post-work step, not optional.
Update TODO.md after substantive work. Trigger after every prompt where code was changed or tasks were completed. Mandatory alongside git-diary-workflow.
Show the personal project dashboard — recent activity, open task counts, prioritization. Trigger when asked about project status, what to work on next, or which projects have open tasks. Keywords: projects, dashboard, proj, overview, TODO, prioritize, what should I work on.