Spec Suite

Comprehensive documentation automation for modern digital products.

Spec Suite is an intelligent orchestrator skill that generates professional software specifications and legal policy documents with a single interaction. It implements a dual-track documentation framework, ensuring complete alignment between technical architecture and legal governance.

Core Capabilities

Intelligent Dependency Resolution
The system understands document prerequisites and enforces logical sequencing. For example, a Backend Schema automatically verifies that a TRD exists, and Privacy Policy generation confirms the Legal Compliance Annex is in place.

Project-Agnostic Architecture
Completely decoupled from specific implementations. Every document is generated dynamically based on your project context, making Spec Suite adaptable across industries and product types.

Modular Access Patterns
Generate an entire specification suite in one orchestrated session, or invoke individual documents using targeted aliases for rapid document creation.

Centralized Output Management
All documentation is generated to a single designated directory, maintaining consistent organization throughout your project workspace.

Documentation Framework

Track A: Technical Specifications

The engineering blueprint for product development.

| Document | Reference | Purpose | |----------|-----------|---------| | Product Requirements Document | prd.md | Define product vision, objectives, and user stories | | Technical Requirements Document | trd.md | System architecture, technology stack, and design patterns | | Backend Schema | backend-schema.md | Database design, entity relationships, and data models | | Application Flow | app-flow.md | User journeys, system interactions, and event sequences | | Design System Brief | uiux-brief.md | Information architecture and design principles | | Implementation Roadmap | implementation-plan.md | Development phases, milestones, and delivery timeline | | Security Architecture | security-plan.md | Threat modeling, security controls, and defense strategies |

Track B: Legal & Policy Framework

The governance structure for platform operations. All documents require legal review for compliance.

| Document | Reference | Purpose | |----------|-----------|---------| | Legal Compliance Annex | legal-compliance-annex.md | Jurisdictional analysis and regulatory requirements | | Terms of Service | terms-of-service.md | User rights, responsibilities, and service conditions | | Privacy Policy | privacy-policy.md | Personal data handling and user privacy rights | | Data Processing Policy | data-processing-policy.md | Technical data lifecycle and processing procedures | | Acceptable Use Policy | acceptable-use-policy.md | Prohibited activities and content moderation guidelines | | Content & Intellectual Property Policy | content-image-policy.md | User-generated content and copyright management | | AI & Automation Policy | ai-use-policy.md | Machine learning implementation and oversight mechanisms | | Service Warranty & Continuity | disclaimer-continuity.md | Liability limitations and service level commitments |

Installation

Via NPM (Recommended)

Execute the installer directly from NPM. This automatically integrates Spec Suite into your .agents/skills directory:

npx spec-suite-skill

Via GitHub (Manual Installation)

Clone the repository directly into your agent's skills directory:

mkdir -p .agents/skills
cd .agents/skills
git clone https://github.com/abdiel49/spec-suite-skill.git spec-suite

Usage Guide

Full Documentation Suite

For new projects requiring complete specification documentation, use the orchestrated workflow:

"Generate the full spec suite for this project."

The system will:

1. Prompt you for essential project parameters
2. Designate a centralized output directory
3. Sequentially generate all Track A and Track B documents
4. Validate dependencies throughout the generation process

Individual Document Generation

Request specific documents by their natural names or use targeted aliases for rapid access:

| Alias | Document | |-------|----------| | spec-suite:prd | Product Requirements Document | | spec-suite:trd | Technical Requirements Document | | spec-suite:schema | Backend Schema | | spec-suite:flow | Application Flow | | spec-suite:uiux | Design System Brief | | spec-suite:plan | Implementation Roadmap | | spec-suite:security | Security Architecture | | spec-suite:legal | Legal Compliance Annex | | spec-suite:tos | Terms of Service | | spec-suite:privacy | Privacy Policy | | spec-suite:data | Data Processing Policy | | spec-suite:aup | Acceptable Use Policy | | spec-suite:content | Content & IP Policy | | spec-suite:ai | AI & Automation Policy | | spec-suite:disclaimer | Service Warranty & Continuity |

Natural Language Interaction

Communicate with the system naturally:

• "Generate a Privacy Policy for my SaaS platform"
• "Create the technical architecture document based on our requirements"
• "I need a comprehensive compliance framework for my marketplace"

Getting Started

Step 1: Install the Skill

Choose your preferred installation method above and integrate Spec Suite into your agent workspace.

Step 2: Initiate Documentation

Begin with a natural language request to the agent. You can start with either track:

• Begin with technical specifications for engineering teams
• Begin with legal framework for compliance and governance

Step 3: Provide Context

When prompted, supply essential project information:

• Product name and industry vertical
• Target markets and regulatory jurisdictions
• Core features and technical architecture
• User base and data sensitivity level
• Business model and commercialization strategy

Step 4: Review & Customize

Generated documents serve as comprehensive starting points. Review and customize for your specific:

• Industry standards and best practices
• Internal policies and procedures
• Jurisdiction-specific legal requirements
• Technical stack and infrastructure decisions

Design Principles

Comprehensive Coverage — Each document is structured to cover essential components without unnecessary verbosity. All critical sections are included; supplementary details can be added during review.

Professional Quality — Documents follow industry standards and best practices, suitable for investor presentations, regulatory submissions, and team communication.

Interdependent Structure — Documents reference and reinforce each other, creating a coherent specification ecosystem where technical and legal requirements align.

Starting Point, Not Final Product — Generated documents are professional drafts. Legal review is mandatory before publication. Technical documents should be refined with internal teams.

Recommended Workflow

1. Phase 1: Requirements — Generate PRD and Legal Compliance Annex simultaneously
2. Phase 2: Architecture — Create TRD, Backend Schema, and Security Plan
3. Phase 3: Implementation — Develop Application Flow, Design Brief, and Implementation Roadmap
4. Phase 4: Governance — Complete Terms of Service, Privacy Policy, and all policy documents
5. Phase 5: Finalization — Review, customize, and obtain necessary approvals

Output Structure

All documents are generated in Markdown format with:

• Clear hierarchical section organization
• Tables and visual elements for easy scanning
• Reference links between related documents
• Placeholder sections for team customization
• Compliance checkpoints and review guidelines

Version & Support

For issues, feature requests, or contributions, visit the GitHub repository.

Spec Suite — Streamline documentation. Align teams. Ship with confidence.