spectacula

Convert rough prompts into implementation-ready specs with lifecycle tracking.

4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/kent/spectacula --skill spectacula
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spectacula
Source: https://github.com/kent/spectacula/tree/main
Command: npx skills add https://github.com/kent/spectacula --skill spectacula

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bootstrap_repo, render_review_prompt, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Spectacula provides a structured workflow to turn rough prompts into implementation-ready specifications and manage them through a lifecycle, enabling audit, upgrade, and implementation tracks for both Codex and Claude Code contexts.

Core Features & Use Cases

  • Frame rough prompts into detailed, implementation-ready specs using repo context and reference examples.
  • Audit and upgrade existing specs against a defined quality bar, preserving intent.
  • Move specs through lifecycle (specs -> ready -> inprogress -> done) with verification gates and optional final vetting.
  • Bootstrap user repos with a living docs/spectacula structure and a plugin/agent ecosystem to support Codex and Claude Code integrations.

Quick Start

bootstrap the docs/spectacula scaffold in a target repo, then create and steer a spec through the lifecycle using the provided scripts and manifests.

Frequently Asked Questions about spectacula

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn rough prompts into implementation-ready specifications?

Turning rough prompts into implementation-ready specifications involves using repo context and reference examples to frame detailed specs. The workflow scaffolds a living docs directory and tracks the spec lifecycle from drafting to done.

How do I manage the specification lifecycle from drafting to done?

You manage the specification lifecycle by moving specs through stages like ready, inprogress, and done using dedicated lifecycle commands. The workflow applies verification gates and an optional final vetting path to ensure implementation quality.

Can I audit and upgrade existing specifications against a quality bar?

Yes, you can audit and upgrade existing specifications against a defined quality bar. The workflow evaluates current specs, upgrades them to meet standards, and preserves the original intent throughout the refinement process.

Does this specification workflow support both Codex and Claude Code environments?

Yes, the specification workflow supports both Codex and Claude Code environments. It uses a plugin and agent ecosystem to integrate with both platforms, tracking spec lifecycles and maintaining resume context across environments.

What is the best way to scaffold a repository for specification tracking?

The best way to scaffold a repository for specification tracking is using a bootstrap workflow. This creates a living docs structure with default templates, manifests, and scripts to support ongoing spec creation and lifecycle management.

Why do I need verification gates in a specification workflow?

Verification gates in a specification workflow enforce quality and completeness before a spec progresses to the next stage. They ensure specs meet defined standards and provide an optional final vetting path before implementation begins.