specops-orchestrate-spec-create

You can generate implementation specs for multiple analysis files by orchestrating sequential subagents that process each file individually, creating per-file specs at deterministic output paths like docs/specops/specs/<basename>.md.

Coordinating spec creation across a repository is best handled by an orchestrator that delegates to sequential subagents, applying a consistent workflow to each analysis document while ensuring repeatable output without writing product code manually.

Verifying generated implementation specs involves post-generation checks that confirm outputs exist and meet required sections, with up to two automated fix-up attempts per file to ensure completeness and explicit failure reporting for blockers.

You need a repository containing analysis documents and a deterministic output path structure where generated specs are written to docs/specops/specs/<analysis-basename>.md, ensuring the orchestrator can locate inputs and route outputs consistently.

If an analysis artifact fails to generate a complete implementation spec, the orchestrator performs up to two fix-up attempts per file and then reports the specific failure as a blocker, ensuring incomplete specs do not silently pass.

Routing project standards and conventions into the spec generation workflow is supported when those standards are present in the repository, allowing the subagents to align the per-file implementation specs with existing project conventions.