adrianpuiu/specification-document-generator

Overview

This skill is a traceability-first architecture engine that produces five interconnected specification documents: blueprint.md, requirements.md, design.md, tasks.md, and validation.md. It enforces evidence-based technology selection, strict templates, approval gates, and a final automated validation that guarantees requirements-to-implementation traceability. Use it to create professional, auditable technical specifications and implementation plans with zero research slop.

How this skill works

The system follows a six-phase workflow: verifiable research, blueprint, requirements, design, tasks, and validation. Phase 0 requires verified source evidence for technology choices; subsequent phases generate structured markdown documents using strict templates and consistent component names. The final validation step runs an automated traceability check that ensures every acceptance criterion maps to at least one implementation task and that no invalid references exist.

When to use it

• Creating system architecture and high-level component maps for new or refactor projects
• Producing requirements documents with testable acceptance criteria and component ownership
• Generating detailed designs tied to specific requirements and code locations
• Breaking designs into actionable implementation tasks with explicit requirement tags
• Ensuring 100% traceability for regulated, safety-critical, or audit-sensitive projects

Best practices

• Start with a clear problem statement, success metrics, and explicit in-scope/out-of-scope items
• Provide technology preferences, performance targets, compliance constraints, and existing integrations up front
• Complete Phase 0 research with verified sources before approving any downstream phase
• Use the exact component names from the blueprint in all subsequent documents to preserve consistency
• Require approval at each gate and run the validation step before execution to guarantee coverage

Example use cases

• Architecting a GDPR-compliant customer support backend with documented integration points and validation
• Producing an auditable specification for a fintech service where every requirement must trace to implementation
• Rewriting a monolith into services while maintaining acceptance criteria traceability across tasks
• Onboarding a new engineering team with design, tasks, and validation that map directly to product requirements
• Preparing deliverables for clients or regulators that require source-verified technology decisions