Skip to main content

Universal Business Documentation Generator — System Prompt

Classification: Internal — Reusable Meta-Prompt
Date: 2026-02-13
Artifact: 79 of WO System Series
Purpose: A parameterized system prompt that generates a complete business + technical documentation corpus for any SaaS/platform product in any regulated or general vertical
Origin: Decomposed from CODITECT Bioscience QMS Work Order System (79 artifacts)

How to Use This Prompt​

Step 1: Seed the Generator​

Fill in the {{SEED}} section below with your business/product specifics. This is the ONLY input required — everything else is generated.

Step 2: Execute in Phases​

The generator runs in 7 phases, each producing a defined set of artifacts. Phases must execute in order (each depends on prior outputs). Within a phase, artifacts can be generated in parallel.

Step 3: Checkpoint After Each Phase​

Each phase produces a checkpoint artifact summarizing what was generated. If context compaction occurs, reload the latest checkpoint and resume.

Step 4: Finalize​

Run the cross-reference integrity check (Phase 7) to ensure all artifacts are consistent.

SEED: Business Context (Fill This In)​

# ─── IDENTITY ───
company_name: "{{COMPANY}}"                      # e.g., "AZ1.AI Inc."
product_name: "{{PRODUCT}}"                      # e.g., "CODITECT Bioscience QMS"
product_type: "{{TYPE}}"                         # e.g., "Autonomous AI-powered QMS platform"
one_line_description: "{{DESCRIPTION}}"          # e.g., "AI-native work order management for regulated industries"
founding_year: {{YEAR}}                          # e.g., 2024
stage: "{{STAGE}}"                               # pre-revenue | <$1M ARR | $1-10M | $10M+
funding: "{{FUNDING}}"                           # bootstrapped | seed $X | series A $X

# ─── MARKET ───
primary_verticals:                               # List 1-5 target industries
  - "{{VERTICAL_1}}"                             # e.g., "Pharmaceutical manufacturing"
  - "{{VERTICAL_2}}"                             # e.g., "Medical device companies"
target_company_size: "{{SIZE}}"                  # SMB | Mid-market | Enterprise | All
geographic_focus: "{{GEO}}"                      # e.g., "US primary, EU expansion Y2"
known_competitors:                               # Minimum 3, ideally 5-7
  - "{{COMPETITOR_1}}"
  - "{{COMPETITOR_2}}"
  - "{{COMPETITOR_3}}"

# ─── PRODUCT ───
core_domain: "{{DOMAIN}}"                        # e.g., "Quality management / change control"
primary_workflow: "{{WORKFLOW}}"                  # e.g., "Work order lifecycle from creation to closure"
key_entities:                                    # Core data objects (3-10)
  - "{{ENTITY_1}}"                               # e.g., "Work Order"
  - "{{ENTITY_2}}"                               # e.g., "Approval"
  - "{{ENTITY_3}}"                               # e.g., "Asset"
architecture_style: "{{ARCH}}"                   # monolith | microservices | event-driven | serverless
primary_language: "{{LANG}}"                     # e.g., "TypeScript + Python"
database: "{{DB}}"                               # e.g., "PostgreSQL"
hosting: "{{HOSTING}}"                           # e.g., "GCP (GKE, Cloud SQL)"
ai_capabilities: "{{AI}}"                        # none | basic | advanced | autonomous agents

# ─── COMPLIANCE ───
regulatory_frameworks:                           # Which regulations apply
  - "{{REG_1}}"                                  # e.g., "FDA 21 CFR Part 11"
  - "{{REG_2}}"                                  # e.g., "HIPAA"
  - "{{REG_3}}"                                  # e.g., "SOC 2 Type II"
compliance_critical: {{BOOL}}                    # true if compliance is core differentiator
data_sensitivity: "{{SENSITIVITY}}"              # public | internal | confidential | regulated

# ─── BUSINESS MODEL ───
pricing_model: "{{PRICING}}"                     # subscription | usage-based | hybrid | per-seat
target_acv_range: "{{ACV}}"                      # e.g., "$96K-$500K"
gtm_motion: "{{GTM}}"                            # PLG | sales-led | channel | hybrid
team_size: {{TEAM}}                              # Current headcount

# ─── DIFFERENTIATORS ───
primary_differentiator: "{{DIFF_1}}"             # e.g., "Autonomous agent architecture"
secondary_differentiator: "{{DIFF_2}}"           # e.g., "Compliance-native design"
technical_moat: "{{MOAT}}"                       # e.g., "Multi-agent orchestration with compliance"

Phase 1: Executive & Business Foundation​

Goal: Establish business case, market context, and strategic rationale
Artifacts: 8 documents
Estimated turns: 3–4

Artifact Template 1.1: Executive Summary​

File: 01-executive-summary.md
Sections:
  1. Problem Statement (1 paragraph — quantify the pain)
  2. Solution Overview (1 paragraph — what {{PRODUCT}} does)
  3. Market Opportunity (TAM/SAM/SOM summary table)
  4. Business Model (pricing, unit economics summary)
  5. Competitive Advantage (top 3 differentiators)
  6. Team & Traction (current state)
  7. Investment Ask / Next Milestones
  8. Risks & Mitigations (top 5)
  9. Recommendation (Go / No-Go / Conditional)
Length: 3-5 pages
Audience: Investors, board, advisors

Artifact Template 1.2: Business Case & ROI​

File: 02-business-case.md
Sections:
  1. Current State (customer pain, cost of status quo)
  2. Proposed Solution ({{PRODUCT}} value proposition)
  3. Financial Model (3-year projection: revenue, costs, margin)
  4. ROI Analysis (customer perspective: payback, efficiency gains)
  5. Risk Analysis (technical, market, regulatory, competitive)
  6. Investment Requirements (capital, team, timeline)
  7. Success Criteria (measurable milestones)
Dependency: Seed data → market sizing

Artifact Template 1.3: Market Opportunity​

File: 03-market-opportunity.md
Sections:
  1. Market Definition & Taxonomy
  2. TAM Calculation (top-down + bottom-up, show math)
  3. SAM Calculation (reachable with current capabilities)
  4. SOM Projection (3-year, with assumptions)
  5. Market Growth Dynamics (CAGR, drivers, inhibitors)
  6. Customer Segmentation (4-6 segments with sizing)
  7. Adjacent Market Opportunities
Execute: Use web_search for current market data

Artifact Template 1.4: Investor One-Pager​

File: 04-investor-one-pager.md
Format: Single page, leave-behind for meetings
Sections: Problem | Solution | Market | Traction | Team | Ask
Constraint: Must fit on 1 printed page

Artifact Template 1.5: Competitive Moat Analysis​

File: 05-competitive-moat-analysis.md
Sections:
  1. Moat Classification (8 moat types scored 1-10)
  2. Per-Moat Deep Dive (evidence, build time, competitor replication time)
  3. Competitive Threat Matrix (per competitor)
  4. Disruption Scenarios (3 scenarios with response plans)
  5. Moat Investment Priorities
Execute: Use 76-competitive-market-analysis-prompt.md methodology

Artifact Template 1.6: Go-to-Market Strategy​

File: 06-go-to-market-strategy.md
Sections:
  1. GTM Motion Selection (PLG / sales-led / channel / hybrid)
  2. Pricing Architecture (tiers, value metrics, expansion mechanism)
  3. Channel Strategy (direct, partner, marketplace, PLG)
  4. Sales Process Design (stages, conversion targets, tools)
  5. Marketing Strategy (funnel, content, demand gen, events)
  6. Customer Success Model (onboarding, health score, expansion)
  7. Phased Launch Plan (Lighthouse → Vertical → Scale)
  8. GTM Metrics Framework (KPIs, dashboards, review cadence)
Execute: Use 77-gtm-strategy-prompt.md methodology

Artifact Template 1.7: Product Roadmap​

File: 07-product-roadmap.md
Sections:
  1. Vision Statement (where the product is going in 3 years)
  2. Phase 1: Foundation (months 1-6, features, milestones)
  3. Phase 2: Growth (months 7-18, features, milestones)
  4. Phase 3: Scale (months 19-36, features, milestones)
  5. Feature Prioritization Framework (RICE or ICE scoring)
  6. Dependency Map (what blocks what)
  7. Revenue Feature Mapping (feature → revenue impact)

Artifact Template 1.8: Business Model & Unit Economics​

File: 08-business-model.md
Sections:
  1. Revenue Model (streams, tiers, pricing mechanics)
  2. Unit Economics (CAC, LTV, payback, NRR, margins)
  3. Customer Segmentation (5 ICP profiles)
  4. Channel Economics (cost structure per channel)
  5. Cost Structure (COGS, R&D, S&M, G&A projections)
  6. Build vs. Buy vs. Partner Analysis
  7. 3-Year Financial Projection

Phase 1 Checkpoint: Save CHECKPOINT-P1.md listing all Phase 1 artifacts with status.

Phase 2: System Architecture & Design​

Goal: Technical architecture at all levels of abstraction
Artifacts: 10 documents
Estimated turns: 4–6

Artifact Template 2.1: System Design Document (SDD)​

File: 10-sdd.md
Sections:
  1. Context Diagram (system in its ecosystem)
  2. Component Breakdown (primary subsystems)
  3. Data & Control Flows
  4. Scaling Model (horizontal/vertical, bottlenecks)
  5. Failure Modes (what breaks, how to recover)
  6. Observability Architecture
  7. Platform Boundary (framework provides vs. custom)
Standard: C4 methodology at all 4 levels

Artifact Template 2.2: Technical Design Document (TDD)​

File: 11-tdd.md
Sections:
  1. API Surface (REST/gRPC/GraphQL endpoints)
  2. Configuration Architecture
  3. Packaging & Deployment
  4. Data Model (entity-relationship summary)
  5. Security Integration Points
  6. Performance Characteristics

Artifact Template 2.3: C4 Architecture Model​

File: 12-c4-architecture.md
Sections:
  C1 — System Context (actors, external systems)
  C2 — Container Diagram (services, databases, message buses)
  C3 — Component Diagram (internal decomposition of key container)
  C4 — Code Diagram (key classes/interfaces at integration boundary)
Each level: Mermaid diagram + narrative + design rationale

Artifact Template 2.4: Data Model​

File: 13-data-model.md
Format: Prisma schema or SQL DDL or equivalent ORM
Include: All entities, relationships, indexes, constraints, RLS policies
Required: Every entity must have audit fields (createdAt, updatedAt, createdBy)
If regulated: Data classification level per field (L0-L4)

Artifact Template 2.5: State Machine Specification​

File: 14-state-machine.md
If primary_workflow involves stateful objects:
  1. State Diagram (all states, transitions)
  2. Transition Table (from → to, guard conditions, side effects)
  3. Guard Implementation (composable guard pattern)
  4. Event Emissions (per transition)
If not applicable: Skip

Artifact Template 2.6: API Endpoint Specification​

File: 15-api-specification.md
Per endpoint:
  - HTTP method + path
  - Auth requirement (which permission)
  - Request schema (with validation rules)
  - Response schema (with examples)
  - Error responses (with error codes)
  - Rate limits
  - Compliance notes

Artifact Template 2.7: Event Catalog​

File: 16-event-catalog.md
If architecture_style includes event-driven:
  1. Event Envelope Schema (standard wrapper)
  2. Per-Event: type, payload schema, producer, consumers, compliance flag
  3. Subject/Topic Hierarchy
  4. Delivery Guarantees
  5. Consumer Matrix
If not event-driven: Skip

Artifact Template 2.8: Data Architecture & Privacy​

File: 17-data-architecture.md
Sections:
  1. Data Classification Taxonomy (5 levels with examples)
  2. Data Lifecycle (creation → storage → archival → deletion)
  3. Data Residency & Sovereignty
  4. Consent Management (if PII/PHI involved)
  5. Data Lineage Architecture
  6. Privacy Impact Assessment Process
  7. Schema Evolution Strategy

Artifact Template 2.9: Security Architecture​

File: 18-security-architecture.md
Sections:
  1. Threat Model (STRIDE methodology)
  2. Authentication Architecture (IdP, SSO, MFA, service-to-service)
  3. Authorization Architecture (RBAC/ABAC model + permission matrix)
  4. Secrets Management
  5. Network Security (zero trust, mTLS, segmentation)
  6. Supply Chain Security (SBOM, image signing, dependency scanning)
  7. Residual Risk Register

Artifact Template 2.10: Integration & API Strategy​

File: 19-integration-strategy.md
Sections:
  1. Integration Tier Classification (core / strategic / commodity)
  2. API Design Philosophy (REST vs. GraphQL vs. gRPC)
  3. API Versioning & Lifecycle
  4. Webhook / Outbound Event Architecture
  5. Plugin / Extension Architecture (if applicable)
  6. Migration Playbooks (from competitor systems)

Phase 2 Checkpoint: Save CHECKPOINT-P2.md

Phase 3: Compliance & Governance​

Goal: Regulatory mapping, validation, audit readiness
Artifacts: 6 documents
Condition: Generate if compliance_critical: true OR any regulatory_frameworks specified
If no compliance: Skip Phase 3 entirely, generate a single compliance-not-applicable.md stating why

Artifact Template 3.1: Regulatory Compliance Matrix​

File: 20-regulatory-compliance-matrix.md
For EACH regulation in {{regulatory_frameworks}}:
  - Requirement ID (e.g., §11.10(e))
  - Requirement text (summarized)
  - Implementation in {{PRODUCT}}
  - Evidence location (which artifact, which test)
  - Status (implemented / partial / planned)

Artifact Template 3.2: RBAC & Permissions Model​

File: 21-rbac-permissions-matrix.md
  1. Role Definitions (per role: name, description, scope)
  2. Permission Matrix (role × action × entity)
  3. Separation of Duties Rules
  4. Agent Identity Model (if AI capabilities present)

Artifact Template 3.3: Validation Protocol Templates​

File: 22-validation-protocols.md
If regulated (FDA/ISO/GxP):
  1. IQ Protocol Template + Execution Record
  2. OQ Protocol Template + Execution Record
  3. PQ Protocol Template
  4. Traceability Matrix
  5. Deviation Handling
  6. Evidence Package Format
If not regulated: Skip

Artifact Template 3.4: CAPA Workflow​

File: 23-capa-workflow.md
If QMS/quality context:
  1. CAPA Data Model
  2. CAPA State Machine
  3. CAPA-to-Work-Order Integration
  4. Risk Assessment Integration
  5. Root Cause Analysis Methods
  6. Compliance Traceability
If not applicable: Skip

Artifact Template 3.5: Audit Readiness Guide​

File: 24-audit-readiness-guide.md
  1. Pre-Audit Checklist (standing readiness)
  2. Per-Regulation Audit Guide (questions → evidence → extraction)
  3. Evidence Folder Structure
  4. Auditor Access Protocol
  5. Post-Audit Response Procedures

Artifact Template 3.6: E-Signature Architecture​

File: 25-e-signature-architecture.md
If regulated (FDA Part 11 or similar):
  1. Signature Flow (create → bind → verify)
  2. Regulatory Mapping (§11.50, §11.70, §11.100)
  3. Cryptographic Implementation
If not applicable: Skip

Phase 3 Checkpoint: Save CHECKPOINT-P3.md

Phase 4: Agent & Orchestration Architecture​

Goal: Multi-agent design (if AI capabilities present)
Artifacts: 3–4 documents
Condition: Generate if ai_capabilities is "advanced" or "autonomous agents"
If no AI: Skip Phase 4

Artifact Template 4.1: Agent Orchestration Specification​

File: 26-agent-orchestration.md
  1. Agent Node Registry (per node: role, tools, model assignment)
  2. Agent Message Contracts (typed interfaces)
  3. Orchestration Patterns (chain, route, parallel, orch-workers, eval-opt)
  4. Circuit Breaker Configuration
  5. Token Budget Management

Artifact Template 4.2: Agent Message Contracts​

File: 27-agent-message-contracts.md
  Per message type: schema, producer, consumer, routing rules

Artifact Template 4.3: Model Routing Strategy​

File: 28-model-routing.md
  1. Routing Rules (task type × complexity × regulatory → model)
  2. Cost Tracking
  3. Fallback Strategy

Phase 4 Checkpoint: Save CHECKPOINT-P4.md

Phase 5: Operations & Deployment​

Goal: Operational readiness for production
Artifacts: 5 documents
Estimated turns: 2–3

Artifact Template 5.1: Deployment Architecture​

File: 30-deployment-architecture.md
  1. Environment Strategy (local / dev / staging / prod / DR)
  2. Infrastructure as Code (Terraform structure)
  3. Container Strategy (images, security, Kubernetes manifests)
  4. CI/CD Pipeline (stages, gates, timing)
  5. Release Process (types, checklists, canary strategy)
  6. Secrets Management in Deployment

Artifact Template 5.2: Testing Strategy​

File: 31-testing-strategy.md
  1. Test Pyramid (unit/integration/e2e/contract/compliance ratios)
  2. Test Data Management (synthetic data for regulated environments)
  3. Performance Testing (load profiles, SLA targets)
  4. Chaos Engineering (failure injection experiments)
  5. Compliance Validation Automation (IQ/OQ/PQ)
  6. CI/CD Test Gates

Artifact Template 5.3: Operational Readiness​

File: 32-operational-readiness.md
  1. Team Topology (Conway's Law alignment)
  2. Skills Gap Analysis
  3. Operational Runbooks (per critical component)
  4. Cost of Ownership Model (3-year TCO)
  5. Vendor Risk Assessment
  6. Disaster Recovery (RPO/RTO per data tier)
  7. Business Continuity
  8. SLA Framework
  9. On-Call Design
  10. Localization & Multi-Market Readiness

Artifact Template 5.4: User Experience Journeys​

File: 33-user-experience-journeys.md
  1. Persona-Journey Matrix
  2. Information Architecture
  3. Onboarding Architecture (time-to-value design)
  4. Accessibility Requirements (WCAG 2.1 AA)
  5. Error Experience Design
  6. Notification Architecture

Artifact Template 5.5: Versioning & Evolution Strategy​

File: 34-versioning-evolution.md
  1. API Versioning Strategy
  2. Feature Flag Architecture
  3. Schema Evolution Strategy
  4. Deprecation Policy
  5. Architecture Fitness Functions
  6. Release Management in Regulated Environments

Phase 5 Checkpoint: Save CHECKPOINT-P5.md

Phase 6: Reference & Navigation​

Goal: Cross-cutting reference documents
Artifacts: 5 documents
Estimated turns: 2

Artifact Template 6.1: Quick Start Guide​

File: 40-quick-start-guide.md
  Step 1: Local Setup (hello-world in < 10 minutes)
  Step 2: Realistic Workflow (connect to real use case)
  Step 3: Deploy (production-like environment)
  All code blocks: copy-paste runnable

Artifact Template 6.2: Architecture Decision Records​

File: 41-architecture-decision-records.md
  3–7 ADRs using: Status, Context, Decision, Consequences, Alternatives
  Minimum topics: technology selection, architecture pattern, data store, compliance strategy

Artifact Template 6.3: Glossary​

File: 42-glossary.md
  Format: | Term | Definition | {{PRODUCT}} Equivalent | Ecosystem Analogs |
  Organized: A→Z
  Coverage: Every acronym and domain term from all artifacts

Artifact Template 6.4: Document Inventory​

File: 43-document-inventory.md
  1. Reading Guide (paths by reader persona)
  2. Category-organized artifact table (ID, file, title, format, description)
  3. Cross-reference metrics table

Artifact Template 6.5: Cross-Artifact Impact Register​

File: 44-impact-register.md
  1. Artifact Dependency Graph
  2. Impact Matrix (new → existing)
  3. Gap Closure Status
  4. Finalization Checklist

Phase 6 Checkpoint: Save CHECKPOINT-P6.md

Phase 7: Visualization & Meta-Prompts​

Goal: Interactive dashboards + future generation prompts
Artifacts: Variable (dashboards + prompts)
Estimated turns: 3–6

Dashboard Generation Template​

For each dashboard, generate a standalone .jsx file following these rules:

  • Single file, all data inline
  • Tailwind core utilities only
  • React useState + useCallback/useMemo
  • Default export, no required props
  • No localStorage
  • Light theme only (white backgrounds, dark text)
  • Horizontal tab navigation
  • Status indicators: Green (#059669), Yellow (#D97706), Red (#DC2626)

Required Dashboards (Minimum 4)​

DashboardContentSource Artifacts
Technology Architecture AnalyzerComponents, integration surface, runtime, gaps10–19
Strategic Fit DashboardCompetitive landscape, build/buy/integrate, trajectory05–08
Integration PlaybookMigration path, compliance mapping, ADR summary20–25, 30–34
Executive Decision BriefSummary, investment, readiness, recommendation01–08

Meta-Prompts to Generate​

PromptPurposeOutput
Competitive Market AnalysisDeep competitive intelligence76-style
GTM StrategyGo-to-market operational plan77-style
Gap Closure SeriesSystematic gap identification and closureNumbered prompt list
Website Build SeriesDocumentation website generationPage-by-page prompts

Phase 7 Checkpoint: Save CHECKPOINT-P7.md (final checkpoint)

Execution Summary​

PhaseArtifactsConditionEst. TurnsDependencies
1. Business Foundation8Always3–4Seed only
2. System Architecture10Always4–6Phase 1
3. Compliance6If regulated2–3Phase 2
4. Agent/AI3–4If AI capabilities1–2Phase 2
5. Operations5Always2–3Phases 2–4
6. Reference5Always2All prior
7. Visualization4–8+Always3–6All prior
Total41–46 core17–26 turns

Artifact Count by Business Type​

Business TypePhasesTotal Artifacts
Simple SaaS (no compliance, no AI)1, 2, 5, 6, 7~32
Regulated SaaS (compliance, no AI)1, 2, 3, 5, 6, 7~38
AI platform (no compliance)1, 2, 4, 5, 6, 7~36
Regulated AI platform (CODITECT)All phases~46+

Adaptation Guide​

Vertical-Specific Customization Points​

VerticalPhase 3 RegulationsPhase 2 EntitiesPhase 1 Market Data
Life Sciences / PharmaFDA 21 CFR Part 11, ISO 13485, GxPWork Orders, Assets, Calibrations, CAPAsQMS market ($3.5B)
Healthcare ITHIPAA, HITECH, ONCPatients, Encounters, Orders, ResultsHealth IT market ($250B)
Fintech / BankingSOC 2, PCI-DSS, SOX, GLBATransactions, Accounts, KYC, AMLFintech market ($300B)
Government / DefenseFedRAMP, ITAR, CMMCCases, Personnel, ClearancesGovTech market ($30B)
EdTechFERPA, COPPAStudents, Courses, AssessmentsEdTech market ($400B)
InsuranceSOC 2, state regulationsPolicies, Claims, UnderwritingInsurTech market ($10B)
General B2B SaaSSOC 2 (optional)[Domain-specific][Industry-specific]

Scaling Down for Simpler Products​

If your product is NOT regulated and NOT AI-powered:

  1. Skip Phase 3 entirely
  2. Skip Phase 4 entirely
  3. Simplify Phase 2: Drop event catalog, CAPA, e-signature, agent specs
  4. Simplify Phase 5: Drop validation protocols, chaos engineering
  5. Result: ~25–30 artifacts covering business + architecture + operations

Scaling Up for Complex Products​

If your product has MORE complexity:

  1. Add per-integration specification documents
  2. Add per-market regulatory analysis
  3. Add customer-facing documentation (user guides, admin guides, API docs)
  4. Add training curriculum specification
  5. Add partner integration specifications
  6. Result: 60–100+ artifacts

Quality Gates​

Before considering the corpus complete, verify:

GateCheckTool
ConsistencyAll numbers match across artifacts (TAM, pricing, team size)Manual cross-reference
CompletenessEvery entity in data model has API endpoints and eventsAutomated: grep entity names across files
Cross-referenceEvery artifact's "Cross-Reference" section is accurateManual or scripted
Glossary coverageEvery acronym in every artifact is in the glossaryAutomated: extract and diff
Reading pathsDocument inventory reading paths are navigableManual walkthrough
Dashboard dataJSX dashboards match current artifact dataManual comparison

This generator produces a documentation corpus equivalent to what took the CODITECT WO system 79 artifacts and dozens of sessions to build — but structured so any team can reproduce it for their product in 17–26 focused prompt turns. The key insight: start from business context (Phase 1), build architecture on top (Phase 2), layer compliance where required (Phase 3), add AI orchestration if applicable (Phase 4), operationalize (Phase 5), cross-reference (Phase 6), and visualize (Phase 7).