spec-start

Bootstrap six roles and orchestrate a five-stage Spec-driven development workflow.

140|20|Updated Jan 8, 2026

Search Tags:#workflow #collaboration #agent-teams #stage-gates #spec-start #requirement-alignment #teamlead

Ready to run

npx skills add https://github.com/HHU3637kr/skills --skill spec-start

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-start
Source: https://github.com/HHU3637kr/skills/tree/main/spec-start
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-start

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill starts and coordinates a complete Spec-driven development workflow by bootstrapping six roles under a TeamLead-guided governance to manage new tasks.

Core Features & Use Cases

Bootstraps six specialized roles (spec-explorer, spec-writer, spec-tester, spec-executor, spec-debugger, spec-ender) within a coordinated, stage-gated lifecycle.
Orchestrates the five-stage development process (requirement alignment, spec creation, implementation, testing, and closure) with explicit user-confirmation checkpoints.
Provides a ready-to-use playbook for teams adopting Spec-driven development and Agent Teams collaboration.

Quick Start

Run the spec-start workflow to bootstrap a six-role team and begin Stage One after confirming requirements with the user.

Frequently Asked Questions about spec-start

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

FAQPage Schema

How do I start a spec-driven development workflow with agent teams?▼

To start a spec-driven development workflow, you initiate a multi-role orchestration that bootstraps six specialized roles under TeamLead governance to manage new tasks across five structured stages. This coordination applies when teams need end-to-end product development lifecycle management.

What roles are needed for spec-driven development coordination?▼

Spec-driven development coordination requires six specialized roles: spec-explorer, spec-writer, spec-tester, spec-executor, spec-debugger, and spec-ender. These roles operate under a TeamLead-guided governance throughout the stage-gated lifecycle.

Do I need an initialized project before running spec-start?▼

Yes, you must have an initialized project with spec-init completed before running spec-start. The workflow requires this prerequisite environment setup to properly orchestrate the TeamLead-driven role creation and stage transitions.

Can I use stage gates to control development workflow transitions?▼

Yes, the spec-driven workflow applies stage gates to control transitions across five stages: requirement alignment, spec creation, implementation, testing, and closure. Explicit user-confirmation checkpoints are provided at each transition to ensure proper coordination.

What are the limitations of using a spec-driven workflow for agent teams?▼

The spec-driven workflow requires a TeamLead-driven orchestration model and an initialized project environment. It is specifically designed for structured, end-to-end product development coordination and may not suit teams needing informal or ad-hoc task management without stage gates.