Some checks failed
Tests / PR mergeability (push) Successful in 1m37s
Tests / Base branch health (push) Successful in 11s
Tests / Detect test scope (push) Successful in 17s
Tests / lint-tests (push) Failing after 2m16s
Tests / plugin-validate (push) Successful in 1m6s
Tests / test (ubuntu-latest, 24, shard 1/3) (push) Failing after 25s
Tests / test (ubuntu-latest, 24, shard 2/3) (push) Failing after 20s
Tests / test (ubuntu-latest, 24, shard 3/3) (push) Failing after 20s
Tests / test (ubuntu-latest, 24) (push) Failing after 19s
Tests / test (inert CI) (push) Has been skipped
Tests / QA loop walk (smell ratchet) (push) Failing after 19s
Tests / Coverage gate (merged shards) (push) Has been skipped
Tests / Publish emitted-baseline artifact (push) Has been skipped
Dismiss Unauthorized PR Approvals / dismiss-unauthorized-approval (push) Successful in 9s
Close Draft PRs (sweep) / Sweep open draft PRs (push) Successful in 8s
Tests / conformance test (macos-latest, 24) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 1/3) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 2/3) (push) Has been cancelled
Tests / conformance test (windows-latest, 24, shard 3/3) (push) Has been cancelled
Tests / Required tests (push) Has been cancelled
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.
56 lines
2.5 KiB
Markdown
56 lines
2.5 KiB
Markdown
# 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 `contextFileName` is
|
|
> `GEMINI.md`, inherited from the shared Gemini 3 backend).
|
|
|
|
This context gives Antigravity the operating context for
|
|
[MSD Core](https://git.golem15.com/golem15/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:
|
|
>
|
|
> ```bash
|
|
> npx msd-core --antigravity --global
|
|
> ```
|
|
>
|
|
> The 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-progress`
|
|
is the situational entry point.
|
|
|
|
Learn more: <https://git.golem15.com/golem15/msd-core>
|