Argonavis Labs
- 4 repo stars
- Updated May 26, 2026
- kent/spectacula
Spectacula is a spec-first Claude Code and Codex plugin that expands short prompts into implementation-ready specifications with lifecycle manifests for developers who need planned, verifiable feature work across specs,
About
Spectacula is a Claude Code marketplace plugin (v1.2.2 by Argonavis Labs) that implements a spec-first workflow shared with Codex via a root SKILL.md. Short prompts expand into full engineering specs stored under `docs/spectacula/specs`, then move through `ready`, `inprogress`, and `done` manifests with resume context, verification state, and history. The plugin ships 4 Claude subagents—spectacula-architect, spectacula-implementer, spectacula-reviewer, and spectacula-status—and a lifecycle CLI via `scripts/spectacula` for bootstrap, validate, move, report, and final-vetting verdicts. The stricter `$spectacula++` alias requires `review_policy.final_vetting` before marking work done. Install with `/plugin marketplace add argonavis-labs/spectacula` and `/plugin install spectacula@argonavis-labs`. Developers reach for Spectacula when chat-only coding lacks approval gates, spec audits, or interrupt-safe resume metadata.
- Tracks specs across 4 lifecycle folders: specs, ready, inprogress, done
- Ships 4 Claude plugin subagents for architect, implementer, reviewer, status
- Expands short prompts into full implementation-ready engineering specs
- Provides lifecycle CLI for bootstrap, validate, move, report, and verdicts
- Supports strict $spectacula++ final-vetting gate before done status
Argonavis Labs by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add kent/spectaculaAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| repo stars | ★ 4 |
|---|---|
| Last updated | May 26, 2026 |
| Repository | kent/spectacula ↗ |
How do you run spec-first feature workflows in Claude Code?
Bootstrap docs/spectacula, write an implementation-ready spec, and track it across ready, inprogress, and done with verification gates.
Who is it for?
Developers using Claude Code or Codex who want RFC-depth specs, lifecycle manifests, spec audits, and optional final-vetting before marking features done.
Skip if: Quick one-file edits without planning overhead, or teams that do not want to maintain a docs/spectacula directory contract in each repository.
What you get
docs/spectacula specs, stage manifests, verification records, resume context, and implemented features vetted against the approved spec.
- implementation-ready spec markdown
- lifecycle stage manifests
- verification and resume metadata
By the numbers
- Plugin version 1.2.2 in .claude-plugin/plugin.json
- Ships 4 Claude plugin subagents for lifecycle roles
- Uses 4 lifecycle stage directories under docs/spectacula
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Pick Spectacula when features need manifest-tracked specs and verification gates—not ad-hoc agent coding without docs/spectacula state.
FAQ
Where does Spectacula store live specifications?
Spectacula stores canonical specs and stage manifests in the user’s project repo under `docs/spectacula`, with folders for `specs`, `ready`, `inprogress`, and `done` created by the bootstrap CLI.
How do you install Spectacula in Claude Code?
Spectacula installs via `/plugin marketplace add Argonavis Labs/spectacula` followed by `/plugin install spectacula@Argonavis Labs`, then invoke `/spectacula:spectacula` or `$spectacula` prompts from the shared skill.
What is the difference between spectacula and spectacula++?
Spectacula++ uses the same implementation loop but requires `review_policy.final_vetting = required` and a recorded `verification.final_vetting` verdict via the review CLI before a manifest can move to `done`.