spec-all

Coordinate end-to-end spec writing across project features with subagent analysis.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill spec-all
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-all
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/spec-all
Command: npx skills add https://github.com/i-standard1/yamasaki --skill spec-all

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PM orchestration of full-spectrum spec writing for all features, coordinating multiple subagents to generate, consolidate, and update requirements, designs, and tests with high consistency and traceability.

Core Features & Use Cases

  • Orchestrates parent Opus and spec-writer subagents to analyze, write, review, and commit specs for all features
  • Batch-splits work to prevent context overflow while maintaining traceability with REQ-ID planning
  • Performs unified updates across design, requirements, and documentation, including consistency and coverage reviews

Quick Start

Prompt the system to run spec-all to orchestrate end-to-end spec generation for all features.

Frequently Asked Questions about spec-all

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

FAQPage Schema
How do I coordinate end-to-end spec writing for all features across a project?

End-to-end spec writing is coordinated by orchestrating parallel subagent analysis to consolidate requirements, designs, and tests into comprehensive definitions. This ensures full project coverage and consistency while automatically updating documents with traceable REQ-IDs.

How does multi-agent requirements traceability work when generating project documentation?

Multi-agent requirements traceability works by batch-splitting feature analysis across subagents to prevent context overflow. Results are consolidated and mapped to planned REQ-IDs, ensuring every generated requirement, design, and test remains linked and traceable.

What is the best way to prevent context overflow during large-scale spec generation?

Preventing context overflow during spec generation involves batch-splitting workloads across multiple spec-writer subagents. This parallel processing approach maintains strict traceability through REQ-ID planning while handling comprehensive feature sets without exceeding limits.

Can I enforce spec-writing standards and consistency across multiple parallel requirements definitions?

Spec-writing standards and consistency are enforced by orchestrating a parent agent to review and consolidate subagent outputs. Unified updates across design, requirements, and documentation ensure all parallel feature specs meet project coverage and consistency rules.

When do I need automated requirements consolidation for project management?

Automated requirements consolidation is needed when managing full-spectrum spec writing for all features across a project. It orchestrates parallel subagents to generate, review, and commit unified design and test documents with high traceability and coverage.

Does spec-all handle unified updates across design, requirements, and tests?

Spec-all handles unified updates across design, requirements, and tests by performing consistency and coverage reviews on consolidated subagent outputs. It orchestrates end-to-end spec generation to ensure all project documentation remains synchronized and traceable.