spec-architect

Coordinate multi-agent software development across PLAN, BUILD, and ITERATE workflows.

Updated Nov 4, 2025

Search Tags:#workflow #specification #multi-agent #PLAN #BUILD #ITERATE

Ready to run

npx skills add https://github.com/codethread/claude-code-plugins --skill spec-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: spec-architect
Source: https://github.com/codethread/claude-code-plugins/tree/main/plugins/spec-dev/skills/spec-architect
Command: npx skills add https://github.com/codethread/claude-code-plugins --skill spec-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It orchestrates multi-agent software development from requirements through verified implementation using plan/build/iterate workflows. It enforces patterns, type safety, and disciplined handoffs across PLAN, BUILD, ITERATE phases.

Core Features & Use Cases

Structured agent coordination via CORE SPEC-DRIVEN workflows (PLAN/BUILD/ITERATE)
Explicit, resume-able handoffs using COMMUNICATION_PROTOCOL
Enforcement of type safety, test quality, and code review before QA
Repository- and project-specific templates to accelerate spec creation

Quick Start

Create a new specs/ directory, draft feature.md with FR/NFR requirements, then create tech.md with high-level implementation tasks. Follow COMMUNICATION_PROTOCOL to brief the appropriate agents and manage handoffs. Use the PLAN, BUILD, ITERATE workflows to guide execution.

Frequently Asked Questions about spec-architect

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

FAQPage Schema

How do I coordinate multi-agent software development workflows?▼

Multi-agent coordination uses PLAN/BUILD/ITERATE phases with explicit handoffs via a communication protocol. Create feature and tech specifications in a specs/ directory, then route tasks to specialized agents while enforcing type safety, test quality, and code review before QA.

What's the best way to structure technical specifications for implementation?▼

Structure specs with functional and non-functional requirements (FR/NFR) in feature.md, then break high-level implementation tasks into tech.md. Use COMMUNICATION_PROTOCOL to brief agents and manage resume-able handoffs across planning, building, and iteration phases.

How do I enforce pattern consistency and type safety across agent handoffs?▼

Spec-driven workflows enforce patterns and type safety by requiring structured agent communication, test quality gates, and code review prior to QA. Repository and project-specific templates accelerate spec creation while maintaining disciplined handoffs.

Can I use multi-agent workflows for complex feature development?▼

Yes. Multi-agent workflows apply to planning features, crafting technical specifications, implementing complex tasks via specialized agents, and managing spec-dev workflows across codebases with explicit communication protocols and lifecycle guidance.

What's required before starting a multi-agent specification workflow?▼

Create a specs/ directory in your repository, draft feature.md with requirements, and prepare tech.md with implementation tasks. The COMMUNICATION_PROTOCOL provides the template for briefing agents and managing handoffs through each phase.