skills.rest
FlavioCFOliveira
FlavioCFOliveiraCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

spec-orchestrator

Automate creation, update, and review of SPEC/ project specifications.

1|Updated Mar 16, 2026
Search Tags:#architecture#documentation#specification#requirements#qa#go#spec-management
One-click install
npx skills add https://github.com/FlavioCFOliveira/Groadmap --skill spec-orchestrator-flaviocfoliveira
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-orchestrator
Source: https://github.com/FlavioCFOliveira/Groadmap/tree/main/.claude/skills/spec-orchestrator
Command: npx skills add https://github.com/FlavioCFOliveira/Groadmap --skill spec-orchestrator-flaviocfoliveira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures that every feature starts from a single, authoritative SPEC/ specification, preventing scope drift and miscommunication by enforcing a centralized, policy-driven workflow.

Core Features & Use Cases

  • Create, update, and review SPEC/ files organized by functional areas (ARCHITECTURE.md, BUILD.md, DEPLOY.md, COMMANDS.md, DATABASE.md, etc.).
  • Coordinate with specialized agents (go-elite-developer, go-gitflow, red-team-hacker, go-performance-advisor, exhaustive-qa-engineer) to gather requirements and validate implementations.
  • Maintain a single source of truth with versioning, change history, and traceability across feature specifications.

Quick Start

Ask the orchestrator to create or update SPEC/ entries following the Specification First Policy.

Frequently Asked Questions about spec-orchestrator

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

FAQPage Schema
How do I maintain a single source of truth for project specifications and prevent scope drift?▼

You can maintain a single source of truth for project specifications by automating the creation and review of SPEC/ files across functional areas, enforcing a centralized, policy-driven workflow to prevent scope drift and miscommunication.

What is specification-first governance for feature development?▼

Specification-first governance is a centralized, policy-driven workflow ensuring every feature starts from an authoritative SPEC/ specification, enforcing clear objectives, interfaces, and documented change history to prevent miscommunication.

How do I document architecture and requirements validation across specialized agents?▼

To document architecture and validate implementations, you coordinate with specialized agents like go-elite-developer, red-team-hacker, and exhaustive-qa-engineer to gather requirements and validate implementations within organized SPEC/ files.

Does the spec-orchestrator workflow require specific directory structures for documentation?▼

Yes, the spec-orchestrator workflow requires a SPEC/ directory structure to organize functional specification files such as ARCHITECTURE.md, BUILD.md, DEPLOY.md, COMMANDS.md, and DATABASE.md for centralized governance.

What is the best way to track change history and traceability in feature specifications?▼

The best way to track change history and traceability in feature specifications is to maintain SPEC/ files with built-in versioning and documented change history, ensuring traceability across all functional areas.

Related Skills

Explore More Software Engineering Skills→
unipds-engenharia-de-ia-aplicadaunipds-engenharia-de-ia-aplicada
1.0k

speckit-clarify

Identify underspecified areas in feature specifications and record clarifications.

Official
Advanced
cassioalexandrecassioalexandre
2

bmad-document-project

Document brownfield repositories with scan levels and incremental state-file updates.

Community
Intermediate
Euraika-LabsEuraika-Labs
14

team-ui

Orchestrate multi-role UI workflows for game projects from specification to polish.

Official
Advanced
kimen-devkimen-dev

gherkin-use-cases

Standardize Gherkin feature files as executable behavior contracts for UI components.

Official
Advanced