mina

astronaut-ai

A Claude Code plugin marketplace and opencode-compatible skill bundle for spec-driven development. Wires together Jira → OpenSpec → GSD/Superpowers → code → Jira into a single pipeline.

Install

Path A — Claude Code (via marketplace)

/plugin marketplace add astronaut1712/astronaut-ai
/plugin install mina@mina

Restart Claude Code. Verify with /help — you should see /mina:jira-pick and the other three commands.

Path B — opencode (via install script)

git clone https://github.com/astronaut1712/astronaut-ai.git
cd astronaut-ai
chmod +x install.sh
./install.sh opencode           # project scope
./install.sh opencode --user    # user scope (~/.config/opencode/)

Path C — Claude Code (manual, no marketplace)

If you want to edit the skills/commands directly in your project (e.g. customize for your team's stack), skip the marketplace and use the install script:

./install.sh claude-code           # project scope, into .claude/
./install.sh claude-code --user    # user scope, into ~/.claude/
./install.sh both                  # both Claude Code and opencode

The trade-off: manual install gives flat command names (/jira-pick), marketplace gives namespaced (/mina:jira-pick).

Repo layout

astronaut-ai/
├── .claude-plugin/
│   └── marketplace.json              ← marketplace catalog
├── plugins/
│   └── mina/                         ← the plugin
│       ├── .claude-plugin/
│       │   └── plugin.json
│       ├── skills/
│       │   ├── spec-driven-workflow/
│       │   ├── openspec-aware/
│       │   ├── jira-via-acli/
│       │   ├── token-tracking/
│       │   ├── model-fallback/
│       │   ├── progress-tracking/
│       │   └── process-resume/
│       ├── commands/
│       │   ├── jira-pick.md
│       │   ├── jira-to-spec.md
│       │   ├── spec-to-plan.md
│       │   ├── jira-update.md
│       │   ├── token-report.md
│       │   ├── model-route.md
│       │   ├── model-switch.md
│       │   ├── status.md
│       │   ├── resume.md
│       │   ├── processes.md
│       │   └── checkpoint.md
│       ├── hooks/
│       │   └── statusline.sh         ← progress + cost + routing warnings
│       └── README.md
├── templates/
│   ├── CLAUDE.md.snippet
│   ├── mcp.json.example              ← Atlassian MCP config
│   ├── settings.json.example         ← Claude Code statusline wiring
│   ├── model-routing.json.example    ← model tiers + fallback chains
│   ├── opencode.json.example         ← opencode multi-provider config
│   └── proposal-template.md          ← OpenSpec proposal with Jira frontmatter
├── install.sh                        ← opencode + manual installer
├── setup-and-push.sh                 ← personalize + git init
├── README.md                         ← you are here
├── LICENSE
├── CHANGELOG.md
└── .gitignore

The project also expects .mina/ to be created at runtime in your working project:

<your-project>/.mina/
├── state.json                        ← active change/phase/plan/sessions/processes/checkpoints/history
├── tokens/<change>.jsonl             ← per-change cost logs
└── checkpoints/<name>.json           ← named state snapshots

Post-install

Required regardless of install path:

1. Add project rules — append templates/CLAUDE.md.snippet to your project's CLAUDE.md (Claude Code) or AGENTS.md (opencode)

2. Set up Atlassian credentials

   # Create API token at https://id.atlassian.com/manage-profile/security/api-tokens
   export ATLASSIAN_AUTH=$(echo -n "[email protected]:your-api-token" | base64)
   # Add to ~/.zshrc or ~/.bashrc to persist
   

   Then copy templates/mcp.json.example to .mcp.json at your project root.

3. Install the runtime tools (the plugin is glue, not the engine):

   npm install -g @fission-ai/openspec     # required
   npx get-shit-done-cc@latest             # if using GSD execution
   # Superpowers via /plugin in Claude Code
   brew install --cask acli                # optional Jira fallback
   

4. Initialize OpenSpec in your project:

   openspec init
   

5. (Optional) Enable cost tracking statusline — see the next section.

Token / cost tracking

The plugin logs token usage per OpenSpec change so you can attribute spend to specific work, not just sessions. This is opt-in and requires a one-time statusline setup.

Enable

Copy templates/settings.json.example to ~/.claude/settings.json (user-wide) or <project>/.claude/settings.json (per-project). The example wires:

{
  "statusLine": {
    "type": "command",
    "command": "${CLAUDE_PLUGIN_ROOT}/hooks/statusline.sh",
    "padding": 0
  }
}

Restart Claude Code. You'll see a statusline like:

🤖 opus | 💰 $0.23 | 🧠 45% | 📝 ENG-1234 feat-add-dashboard-ssr

Reports