using-spectacular

Enforce spec-anchored development workflows for feature requests using Spectacular.

19|Updated Oct 21, 2025
One-click install
npx skills add https://github.com/arittr/spectacular --skill using-spectacular
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: using-spectacular
Source: https://github.com/arittr/spectacular/tree/main/skills/using-spectacular
Command: npx skills add https://github.com/arittr/spectacular --skill using-spectacular

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates architectural drift and quality issues by enforcing structured development workflows that catch problems before they become technical debt.

Core Features & Use Cases

  • Spec-Driven Development: Generate comprehensive feature specifications before implementation
  • Parallel Execution Planning: Decompose work into parallelizable tasks for faster delivery
  • Constitutional Compliance: Ensure all code follows immutable architectural rules
  • Use Case: When a user requests a new feature like "add user authentication," this Skill ensures proper specification, planning, and execution while validating against architectural constitutions.

Quick Start

Use the using-spectacular skill to handle this feature request by first checking if spectacular workflows apply, then following the spec → plan → execute sequence.

Frequently Asked Questions about using-spectacular

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

FAQPage Schema
How do I enforce spec-anchored development workflows in my project?

Spec-anchored development enforces structured workflows that catch architectural issues before they become technical debt. This Skill applies the spec → plan → execute sequence to feature requests, validating each phase against your project's constitutional rules stored in docs/constitutions/current/.

What's the best way to prevent architectural drift in feature development?

Prevent architectural drift by enforcing constitutional compliance during development. This approach generates comprehensive specifications, decomposes work into parallelizable tasks, and validates quality gates like tests and linting after each phase to ensure code follows immutable architectural rules.

How do I decompose feature requests into parallelizable tasks?

Feature decomposition uses the planning phase to break requests into independent, parallelizable tasks. This Skill orchestrates worktrees and subagents across your project, enabling faster delivery while maintaining architectural consistency and quality validation throughout execution.

Can I apply structured workflows to both feature requests and refactoring work?

Yes, this Skill applies the spec-anchored workflow to both feature and refactor discussions. It guides the sequence of specification, planning, and execution phases for any work in projects maintaining a docs/constitutions/current/ directory.

What happens if my project doesn't have a constitution defined?

Constitutional compliance is a core quality gate. This Skill validates constitution existence before applying the workflow, ensuring your project maintains immutable architectural rules that guide specification, planning, and execution phases.

Why use specification-first development instead of jumping to implementation?

Specification-first development generates comprehensive feature specs before implementation, catching architectural and functional issues early. This approach reduces technical debt, ensures constitutional compliance, and enables parallel task execution for faster, higher-quality delivery.