Skill to process, run, and perform Gemini CLI Conductor commands (/conductor_setup, /conductor_newTrack, /conductor_implement, /conductor_status, /conductor_revert, /conductor_review) and read/generate artifacts in the conductor/ directory.
This skill enables Antigravity to act as the Conductor agent — managing the full lifecycle of software development tracks: context setup, specification, planning, implementation, review, and documentation synchronization.
The conductor directory lives at {PROJECT_ROOT}/conductor/ — the root of the
user's project repository (NOT the Antigravity brain/artifacts directory). All
conductor artifacts are project-level files committed to version control.
conductor/
├── index.md # Links to all context files
├── product.md # Product definition & vision
├── product-guidelines.md # Tone, visual identity, UX patterns
├── tech-stack.md # Technical choices & frameworks
├── workflow.md # Task workflow, coding principles, commands
├── setup_state.json # Setup progress tracking
├── code_styleguides/ # Language-specific style guides
│ ├── html-css.md
│ ├── javascript.md
│ ├── scss.md
│ └── typescript.md
├── tracks.md # Registry of all tracks (features/bugs)
├── tracks/ # Active track directories
│ └── <track_id>/
│ ├── index.md # Track context links
│ ├── spec.md # Detailed specification
│ ├── plan.md # Phased implementation plan
│ └── metadata.json # Track metadata
└── archive/ # Completed track directories
Before executing ANY Conductor command, load the project context by reading these files (in order of priority):
conductor/product.md — What the product isconductor/product-guidelines.md — How it should look & feelconductor/tech-stack.md — Technical decisionsconductor/workflow.md — Task workflow & coding practicesconductor/tracks.md — Current track registryAll Conductor commands use structured choices for user interactions. When a command needs user input, present options as structured choices with clear labels and descriptions rather than freeform text prompts. This applies to:
Whenever a Conductor command produces structured output that requires user
review — clarifying questions, reports, summaries, specs, plans, or
confirmation prompts — always write it as an Antigravity artifact using
write_to_file with IsArtifact: true and present it via notify_user with
PathsToReview.
walkthrough — Review reports, status dashboards, phase verification
plansimplementation_plan — Specs, plans, and proposalsother — Clarifying questions, confirmation prompts, revert previewsArtifact filenames follow the pattern: conductor_<command>_<context>.md
Examples: conductor_setup_product_questions.md,
conductor_review_dark_mode_toggle.md, conductor_status.md
Use rich markdown in artifacts: tables, alerts ([!NOTE], [!TIP],
[!IMPORTANT], [!WARNING]), file links ([file.ts](file:///path)),
mermaid diagrams, and code blocks where useful.
Set BlockedOnUser: true in notify_user when the artifact contains questions
or requires explicit approval before proceeding. Set BlockedOnUser: false for
informational outputs (status, review reports) unless a disposition choice is
required.
/conductor_setupPurpose: Initialize or update the project's Conductor context (run once per project).
Full interaction protocol: The complete interactive prompting script is in the
conductor_setupskill (sibling directory../conductor_setup/SKILL.md).
Capabilities:
package.json, go.mod, BUILD, etc.), source directories, and existing
architecture to classify the project type.setup_state.json to resume interrupted
setups from the last completed step.Steps:
conductor/product.md — Product definition & visionconductor/product-guidelines.md — Tone, visual identity, UX patternsconductor/tech-stack.md — Technical choices & frameworksconductor/code_styleguides/ — Language-specific style guidesconductor/workflow.md — Task workflow & coding practicesconductor/index.md linking all context files.conductor/setup_state.json after each successful step./conductor_newTrackPurpose: Start a new feature or bug fix track with a specification and phased plan, using an enhanced discovery protocol.
Full interaction protocol: The complete interactive prompting script including enhanced discovery is in the
conductor_newTrackskill (sibling directory../conductor_newTrack/SKILL.md).
Syntax:
/conductor_newTrack — Interactive mode (ask user for description)/conductor_newTrack "description of feature or bug" — Direct modeCapabilities:
Steps:
product.md, tech-stack.md, workflow.md exist./conductor_implementPurpose: Execute the plan for the current active track, working through tasks sequentially with TDD lifecycle and phase checkpointing.
Full interaction protocol: The complete execution protocol including TDD lifecycle, phase checkpointing, document synchronization, and track cleanup is in the
conductor_implementskill (sibling directory../conductor_implement/SKILL.md).
Capabilities:
conductor/workflow.md.product.md, tech-stack.md, and product-guidelines.md to
keep project-level docs current.Steps:
Important: The user's conductor/workflow.md is the authoritative source
for task workflow, commit conventions, quality gates, and checkpointing
behavior. Always defer to it.
/conductor_statusPurpose: Get a high-level overview of project progress across all tracks.
Full interaction protocol: The complete protocol is in the
conductor_statusskill (sibling directory../conductor_status/SKILL.md).
Capabilities:
- [ ] **Track:) and legacy
(## [ ] Track:) format in tracks.md.Output includes:
[~] item)[ ] pending task)/conductor_revertPurpose: Undo work from a track, phase, or task using VCS-aware revert.
Full interaction protocol: The complete revert protocol including guided selection and VCS reconciliation is in the
conductor_revertskill (sibling directory../conductor_revert/SKILL.md).
Capabilities:
Steps:
/conductor_reviewPurpose: Review completed work against specifications, guidelines, and quality gates.
Full interaction protocol: The complete review protocol including smart chunking and auto-fix is in the
conductor_reviewskill (sibling directory../conductor_review/SKILL.md).
Capabilities:
code_styleguides/*.md as "Law";
violations are rated High severity.Steps:
These markers are used consistently in plan.md and tracks.md:
| Marker | Meaning |
|---|---|
[ ] | Pending / Not started |
[~] | In progress |
[x] | Completed |
When a track is completed, it can be archived via the cleanup flow in
/conductor_implement or /conductor_review. The track directory is moved from
conductor/tracks/ to conductor/archive/, and the entry in tracks.md is
updated accordingly.
When operating as the Conductor agent, always follow these safety rules:
conductor/tracks/<active_track_id>/ and conductor/tracks.md
during implementation. Document sync (post-completion) is the exception./conductor_newTrack, always
present the spec and plan for explicit user approval before proceeding.Before operating on any conductor files or creating the conductor/ directory,
you MUST ask the user to explicitly specify the project root path (e.g., the
repository path where the directory exists or should be created). Do not
attempt to automatically guess or determine the directory from the current
working context. Use the user-provided path as the {PROJECT_ROOT} for all
conductor operations in the session.