Gemini CLI Extension Porting (Beads + Superpowers)

Overview

Turn skills-based workflows into Gemini CLI extensions by mapping each workflow stage to a command, centralizing shared context in GEMINI.md, and backing prompt-only rules with repository guardrails.

When to Use

• When converting Superpowers or beads workflows into Gemini CLI extension commands
• When designing /namespace:command flows with explicit artifacts and verification
• When you need TDD and quality gates enforced beyond prompt instructions
• When wiring MCP tools or shell commands into Gemini CLI workflows

Core Principles

1. Command-first, no hooks: Invoke commands explicitly and document startup steps in GEMINI.md.
2. Soft + hard enforcement: Define the workflow in prompts and enforce it with CI/pre-commit.
3. Small, composable commands: Keep each command focused on one stage or artifact.
4. Single source of truth: Persist specs, plans, and checkpoints in files instead of chat history.