spec-orchestrator

Orchestrate an 11-phase TDD feature development lifecycle from a specification document.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/acastillo9/budget --skill spec-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-orchestrator
Source: https://github.com/acastillo9/budget/tree/main/.agents/skills/spec-orchestrator
Command: npx skills add https://github.com/acastillo9/budget --skill spec-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex, multi-phase process of developing a new software feature from a specification document, ensuring a test-driven development (TDD) approach is followed rigorously.

Core Features & Use Cases

  • End-to-End Orchestration: Manages an 11-phase lifecycle from spec retrieval to skills analysis.
  • Subagent Coordination: Dispatches and tracks specialized subagents for each development phase (e.g., spec refinement, design, implementation, testing).
  • TDD Enforcement: Strictly enforces a test-first methodology, ensuring tests are written before implementation and used to drive development.
  • Use Case: When you have a new feature requirement in a Confluence page, use this Skill to automatically drive the entire development process, including generating tests, writing code, and reviewing it, ensuring quality and adherence to TDD principles.

Quick Start

Use the spec-orchestrator skill to orchestrate spec-driven TDD feature development from the specification document located at '/path/to/your/feature-spec.md'.

Frequently Asked Questions about spec-orchestrator

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

FAQPage Schema
How do I automate test-driven feature development from a specification document?

Test-driven feature development can be automated from a specification document by orchestrating an 11-phase lifecycle that coordinates specialized subagents for spec refinement, design, testing, and implementation. This ensures strict adherence to test-first methodology.

What is the best way to coordinate subagents for TDD feature development?

Subagent coordination for TDD feature development is managed through file-based message passing, dispatching specialized agents for each phase including API test writing, backend implementation, and code review to maintain efficient context management.

Can I use spec-driven development to generate both API and UI tests automatically?

Spec-driven development can automatically generate both API and UI tests by passing the specification through dedicated phases that write tests before implementation, driving the backend and frontend development through a test-first approach.

Does spec-orchestrator require any specific dependencies or frameworks to run?

Spec-orchestrator requires no external dependencies or frameworks to run. It operates independently to manage the technical design, documentation generation, and implementation phases using its internal subagent coordination mechanism.

How does a test-first methodology handle code review and final skills analysis?

A test-first methodology handles code review and final skills analysis by executing dedicated phases after test execution and fixing. This ensures the implementation meets the specification requirements and evaluates the generated code quality.

When should I use an orchestrated TDD lifecycle instead of manual feature implementation?

An orchestrated TDD lifecycle should be used instead of manual implementation when you have a new feature requirement in a specification document and need to rigorously enforce test-first development while automatically managing context across design, coding, and review.