Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By arittr
Automate spec-anchored development by decomposing feature specs into executable plans with automatic parallel/sequential orchestration using git-spice and isolated worktrees, including TDD workflows and troubleshooting.
npx claudepluginhub joshuarweaver/cascade-code-general-misc-3 --plugin arittr-spectacularSpec-anchored development workflow with automatic sequential/parallel orchestration using superpowers skills and git-spice.
Execute implementation plan with automatic sequential/parallel orchestration using git-spice and worktrees
Initialize spectacular environment - validate dependencies and configuration
Decompose feature spec into executable plan with automatic phase analysis
Generate a lean feature specification using brainstorming and the writing-specs skill
Use when you need to create an execution plan from a feature spec - handles worktree context, dispatches subagent for task decomposition, validates quality, analyzes dependencies, groups into phases, and commits the plan
Use when orchestrating parallel phases in plan execution - creates isolated worktrees for concurrent task execution, installs dependencies, spawns parallel subagents, verifies completion, stacks branches linearly, and cleans up (mandatory for ALL parallel phases including N=1)
Use to execute an implementation plan with automatic sequential/parallel orchestration - handles worktree verification, resume detection, phase dispatch, and quality verification
Use when orchestrating sequential phases in plan execution - executes tasks one-by-one in main worktree using git-spice natural stacking (NO manual upstack commands, NO worktree creation, tasks build on each other)
Shared branch creation and verification logic for sequential and parallel task execution - handles git operations, HEAD verification, and MODE-specific behavior
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Specification-Driven Development with Process Discipline for Claude Code
Spec-driven development using GitHub spec-kit methodology. Constitution-first approach with specify, plan, tasks, and implement phases.
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Unified spec-to-execution workflow system. Combines spec rigor, autonomous execution, and native task orchestration with parallel agent dispatch. Swarms-ready architecture.
GitHub specification integration and verification
Working memory system for Claude Code - integrates with Obsidian via MCP for persistent, cross-session memory management
Spec-anchored development with automatic parallel execution for Claude Code.
Write a spec → generate a plan → execute tasks in parallel → get stacked PRs.
[!NOTE]
/spectacular:executerequires git-spice for PR stacking. Support for Graphite coming soon!
Inspired and powered by Superpowers.
| Problem | Without | With Spectacular |
|---|---|---|
| Context drift | "What was that pattern?" → makes something up | Every task gets a fresh subagent with anchored context |
| Sequential execution | 40 min of serial tasks (even independent ones) | Parallel tasks in isolated worktrees |
| Unmergeable PRs | 47 files, +2,847 lines—nobody reviews this | Stacked PRs, one per task |
| Pattern hallucination | AI invents plausible-sounding patterns | Constitutions define the rules |
Prerequisites:
# Install git-spice (macOS)
brew install git-spice
See git-spice installation instructions for other platforms.
Install plugins:
# In Claude Code, install marketplaces and plugins
/plugin marketplace add obra/superpowers-marketplace
/plugin install superpowers@superpowers-marketplace
/plugin marketplace add arittr/spectacular
/plugin install spectacular@spectacular
Initialize your project:
/spectacular:init
Real example from developing spectacular itself:
/spectacular:spec I can't use my main repo while spectacular is running, it locks everything up. I want each run isolated in its own worktree so I can keep working manually and run multiple features concurrently.
# Feature: Worktree Isolation for Spectacular Runs
## Problem Statement
Spectacular commands operate directly in the main repository:
- Cannot perform manual work during a spectacular run
- Cannot run multiple sessions concurrently
- No isolation between spectacular work and manual work
## Requirements
- FR1: Worktree creation in spec command
- FR2: Plan command operates in worktree
- FR3: Execute command uses worktree as base
...
## Acceptance Criteria
- [ ] Worktree created immediately after RUN_ID generation
- [ ] Spec committed to worktree branch
- [ ] Main repo working directory unchanged
...
/spectacular:plan @specs/dedf14-worktree-isolation/spec.md
## Execution Summary
- **Total Tasks**: 3
- **Total Phases**: 1
- **Sequential Time**: 12h
- **Parallel Time**: 5h
- **Time Savings**: 7h (58%)
## Phase 1: Command Worktree Integration
**Strategy**: parallel
**Reason**: All tasks modify different command files
### Task 1: Spec Command Worktree Integration
Files: commands/spec.md
Complexity: M (4h)
### Task 2: Plan Command Worktree Integration
Files: commands/plan.md
Complexity: M (3h)
### Task 3: Execute Command Worktree Integration
Files: commands/execute.md
Complexity: L (5h)
/spectacular:execute @specs/dedf14-worktree-isolation/plan.md
Time savings: 58% faster—parallel execution runs tasks simultaneously instead of sequentially.
Orchestrator
|
|-- 1. Read plan, identify 3 parallel tasks
|-- 2. Create worktrees
| dedf14-task-1/
| dedf14-task-2/
| dedf14-task-3/
|
|-- 3. Spawn subagents IN PARALLEL
| |
| +-- Subagent 1 (spec.md) +-- Subagent 2 (plan.md) +-- Subagent 3 (execute.md)
| | * Fresh spec context | * Fresh spec context | * Fresh spec context
| | * Implement, test | * Implement, test | * Implement, test
| | * Commit to branch | * Commit to branch | * Commit to branch
| | | |
| +-----------------------------+----------------------------+
| |
|-- 4. Collect results, stack branches: task-1 -> task-2 -> task-3
|-- 5. Code review, cleanup worktrees
gs stack submit
Result: 3 focused PRs instead of one large diff.