Overview

Specification-generation turns requirements from PM interviews into structured technical specs. It defines technology stacks, system architecture, data models, API contracts, and ADRs to guide implementation.

How This Skill Works

The workflow uses Read to examine requirements and existing specs, Grep/Glob to spot architectural patterns, Write to produce the technical spec, and Edit to refine with Architect feedback. It aligns with Maestro phases and supports PM and Architect roles throughout the iteration.

When to Use It

• When starting a project after PM interviews and requirements gathering.
• When selecting technology stacks and architectural patterns for a system.
• When defining API contracts and data models for a new service.
• When documenting Architecture Decision Records (ADRs) for traceability.
• When iterating specs based on Architect feedback until formal approval.

Quick Start

1. Step 1: Use Read to review the requirements and any existing specs.
2. Step 2: Use Write to generate the technical specification including ADRs and data models.
3. Step 3: Use Edit to refine with Architect feedback and finalize for approval.

Best Practices

• Start from a clean requirements document and map to high-level objectives.
• Capture ADRs for every architectural decision with clear rationale.
• Include data models, API contracts, non-functional requirements, and migration notes.
• Reference existing specs and patterns in the codebase using Grep/Glob.
• Iterate with the Architect and Product Manager until formal approval.

Example Use Cases

• Tech spec for a microservices-based checkout system with ADR-backed decisions.
• API contract and data model for a user profile service.
• ADR-driven architecture for a payments integration workflow.
• Tech spec for analytics event collection and processing pipeline.
• End-to-end architecture spec for a customer onboarding flow.

Frequently Asked Questions