12ee75a509
The fork lives on the golem15 Gitea forge, not GitHub. Package identity now parses either host and derives in-place raw URLs for Gitea; the identity-drift lint accepts the new host; README drops GitHub-only badges and the npm quickstart in favour of the checkout installer.
2.5 KiB
MSD Core — Antigravity CLI context
Gemini CLI was sunset by Google on 2026-06-18 and is no longer served for free/Pro/Ultra tiers. Antigravity CLI is its official successor, and this file is the context Antigravity reads automatically (its
contextFileNameisGEMINI.md, inherited from the shared Gemini 3 backend).
This context gives Antigravity the operating context for MSD Core, a meta-prompting, context-engineering, and spec-driven development system for AI coding agents.
What MSD is
MSD turns a vague goal into shipped software through an explicit,
resumable workflow: explore → plan → execute → verify → ship. Work is
organised into milestones and phases under a .planning/ directory, with each
phase carrying a SPEC, a PLAN, and verification criteria. The system favours
small, atomic, test-backed commits and keeps durable context in version-tracked
files rather than in the conversation.
The slash commands (installed separately)
This file ships only the context above — not the slash commands. To install the
/msd-*command set, agents, and hooks into~/.gemini/antigravity/, run the dedicated installer:npx msd-core --antigravity --globalThe commands below are available only once that installer has run.
If you have installed the msd commands, the workflow is driven by these /msd-*
slash commands (Antigravity registers msd's commands under a hyphenated
namespace):
/msd-new-project— initialise a project and gather deep context./msd-progress— the unified situational command: check progress, advance the workflow, or dispatch a freeform intent./msd-plan-phase <N>— produce a detailed phase plan with a verification loop./msd-execute-phase <N>— execute a phase's plans with wave-based parallelism./msd-verify-work— validate built features through conversational UAT./msd-ship— open a PR, run review, and prepare for merge./msd-help— list every available command.
Working with MSD
- Treat
.planning/as the source of truth for project state — read it before acting, and keep it current as work progresses. - Prefer the smallest change that satisfies the phase's verification criteria.
- Run the project's tests and linters before declaring a phase done.
- When unsure what to do next, and the msd commands are installed,
/msd-progressis the situational entry point.
Learn more: https://git.golem15.com/golem15/msd-core