@shahmarasy/prodo 0.1.3 → 0.1.5

package/dist/skills/generate-pipeline-skill.js

@@ -0,0 +1,45 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.generatePipelineSkill = void 0;
+const artifact_registry_1 = require("../core/artifact-registry");
+const artifacts_1 = require("../core/artifacts");
+const normalize_1 = require("../core/normalize");
+const validate_1 = require("../core/validate");
+exports.generatePipelineSkill = {
+    manifest: {
+        name: "generate-pipeline",
+        description: "Run end-to-end pipeline: normalize → generate all artifacts → validate",
+        category: "core",
+        inputs: [
+            { name: "cwd", type: "path", required: true, description: "Project working directory" },
+            { name: "strict", type: "boolean", required: false, description: "Treat warnings as errors" }
+        ],
+        outputs: [
+            { name: "pass", type: "string", description: "Whether validation passed" },
+            { name: "reportPath", type: "path", description: "Path to validation report" },
+            { name: "artifactCount", type: "string", description: "Number of artifacts generated" }
+        ]
+    },
+    async execute(context, inputs) {
+        const cwd = inputs.cwd ?? context.cwd;
+        const normalizedPath = await (0, normalize_1.runNormalize)({ cwd });
+        context.log(`Normalized brief: ${normalizedPath}`);
+        const artifactTypes = await (0, artifact_registry_1.listArtifactTypes)(cwd);
+        for (const type of artifactTypes) {
+            const file = await (0, artifacts_1.generateArtifact)({
+                artifactType: type,
+                cwd,
+                normalizedBriefOverride: normalizedPath,
+                agent: context.agent
+            });
+            context.log(`${type.toUpperCase()} generated: ${file}`);
+        }
+        const result = await (0, validate_1.runValidate)(cwd, { strict: Boolean(inputs.strict) });
+        context.log(`Validation ${result.pass ? "passed" : "failed"}: ${result.reportPath}`);
+        return {
+            pass: result.pass,
+            reportPath: result.reportPath,
+            artifactCount: artifactTypes.length
+        };
+    }
+};

package/dist/skills/normalize-skill.d.ts

@@ -0,0 +1,2 @@
+import type { Skill } from "./types";
+export declare const normalizeSkill: Skill;

package/dist/skills/normalize-skill.js

@@ -0,0 +1,29 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.normalizeSkill = void 0;
+const normalize_1 = require("../core/normalize");
+exports.normalizeSkill = {
+    manifest: {
+        name: "normalize",
+        description: "Normalize a product brief into structured JSON with contracts and confidence scores",
+        category: "core",
+        inputs: [
+            { name: "cwd", type: "path", required: true, description: "Project working directory" },
+            { name: "brief", type: "path", required: false, description: "Override path to brief.md" },
+            { name: "out", type: "path", required: false, description: "Override output path" }
+        ],
+        outputs: [
+            { name: "normalizedBriefPath", type: "path", description: "Path to normalized-brief.json" }
+        ]
+    },
+    async execute(context, inputs) {
+        const cwd = inputs.cwd ?? context.cwd;
+        const outPath = await (0, normalize_1.runNormalize)({
+            cwd,
+            brief: inputs.brief,
+            out: inputs.out
+        });
+        context.log(`Normalized brief written to: ${outPath}`);
+        return { normalizedBriefPath: outPath };
+    }
+};

package/dist/skills/types.d.ts

@@ -0,0 +1,28 @@
+export type SkillInput = {
+    name: string;
+    type: "path" | "string" | "boolean" | "json";
+    required: boolean;
+    description: string;
+};
+export type SkillOutput = {
+    name: string;
+    type: "path" | "string" | "json";
+    description: string;
+};
+export type SkillManifest = {
+    name: string;
+    description: string;
+    category: "core" | "artifact" | "validation" | "custom";
+    inputs: SkillInput[];
+    outputs: SkillOutput[];
+};
+export type SkillContext = {
+    cwd: string;
+    log: (message: string) => void;
+    agent?: string;
+};
+export type SkillFunction = (context: SkillContext, inputs: Record<string, unknown>) => Promise<Record<string, unknown>>;
+export type Skill = {
+    manifest: SkillManifest;
+    execute: SkillFunction;
+};

package/dist/skills/types.js

@@ -0,0 +1,2 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });

package/dist/skills/validate-skill.d.ts

@@ -0,0 +1,2 @@
+import type { Skill } from "./types";
+export declare const validateSkill: Skill;

package/dist/skills/validate-skill.js

@@ -0,0 +1,29 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.validateSkill = void 0;
+const validate_1 = require("../core/validate");
+exports.validateSkill = {
+    manifest: {
+        name: "validate",
+        description: "Run cross-artifact validation and generate a report",
+        category: "validation",
+        inputs: [
+            { name: "cwd", type: "path", required: true, description: "Project working directory" },
+            { name: "strict", type: "boolean", required: false, description: "Treat warnings as errors" },
+            { name: "report", type: "path", required: false, description: "Override report output path" }
+        ],
+        outputs: [
+            { name: "pass", type: "string", description: "Whether validation passed" },
+            { name: "reportPath", type: "path", description: "Path to validation report" }
+        ]
+    },
+    async execute(context, inputs) {
+        const cwd = inputs.cwd ?? context.cwd;
+        const result = await (0, validate_1.runValidate)(cwd, {
+            strict: Boolean(inputs.strict),
+            report: inputs.report
+        });
+        context.log(`Validation ${result.pass ? "passed" : "failed"}: ${result.reportPath}`);
+        return { pass: result.pass, reportPath: result.reportPath, issueCount: result.issues.length };
+    }
+};

package/dist/templates.d.ts

@@ -28,6 +28,6 @@ export declare const NORMALIZED_BRIEF_TEMPLATE: {
         }[];
     };
 };
-export declare const NORMALIZE_PROMPT_TEMPLATE = "Normalize start-brief content into JSON.\n\nReturn JSON object with keys:\n- schema_version (string)\n- product_name (string)\n- problem (string)\n- audience (string[])\n- goals (string[])\n- core_features (string[])\n- constraints (string[])\n- assumptions (string[])\n- contracts.goals[] ({id,text})\n- contracts.core_features[] ({id,text})\n- contracts.constraints[] ({id,text})\n- confidence.product_name (0..1)\n- confidence.problem (0..1)\n- confidence.audience (0..1)\n- confidence.goals (0..1)\n- confidence.core_features (0..1)\n\nRules:\n- do NOT invent missing critical content\n- keep wording concise and concrete\n- if critical field is missing, return empty and low confidence (<0.7)\n- assign deterministic IDs: goals => G1..Gn, features => F1..Fn, constraints => C1..Cn\n- input files are read-only; never modify, summarize, or rewrite `brief.md` in-place\n- write normalized output as a new JSON object only";
+export declare const NORMALIZE_PROMPT_TEMPLATE = "Normalize start-brief content into JSON.\n\nReturn JSON object with keys:\n- schema_version (string)\n- product_name (string)\n- problem (string)\n- audience (string[])\n- goals (string[])\n- core_features (string[])\n- constraints (string[])\n- assumptions (string[])\n- contracts.goals[] ({id,text})\n- contracts.core_features[] ({id,text})\n- contracts.constraints[] ({id,text})\n- confidence.product_name (0..1)\n- confidence.problem (0..1)\n- confidence.audience (0..1)\n- confidence.goals (0..1)\n- confidence.core_features (0..1)\n\nRules:\n- do NOT invent missing critical content\n- keep wording concise and concrete\n- preserve original language and Unicode characters exactly from brief\n- never transliterate Turkish letters (\u00E7, \u011F, \u0131, \u0130, \u00F6, \u015F, \u00FC) into ASCII\n- if critical field is missing, return empty and low confidence (<0.7)\n- assign deterministic IDs: goals => G1..Gn, features => F1..Fn, constraints => C1..Cn\n- input files are read-only; never modify, summarize, or rewrite `brief.md` in-place\n- write normalized output as a new JSON object only";
 export declare function commandTemplate(command: WorkflowCommand): string;
 export declare const HOOKS_TEMPLATE = "# Hook item fields:\n# - command: string (required)\n# - optional: boolean (default false)\n# - enabled: boolean (default true)\n# - condition: shell command; run hook only if condition exits 0\n# - timeout_ms: per-attempt timeout in milliseconds (default 30000)\n# - retry: extra retry count after first attempt (default 0)\n# - retry_delay_ms: delay between retries (default 500)\n#\n# Example:\n# hooks:\n#   before_prd:\n#     - command: \"node -e \\\"console.log('lint ok')\\\"\"\n#       optional: false\n#       enabled: true\n#       condition: \"node -e \\\"process.exit(0)\\\"\"\n#       timeout_ms: 15000\n#       retry: 1\n#       retry_delay_ms: 300\n\nhooks:\n  before_normalize: []\n  after_normalize: []\n  before_prd: []\n  after_prd: []\n  before_workflow: []\n  after_workflow: []\n  before_wireframe: []\n  after_wireframe: []\n  before_stories: []\n  after_stories: []\n  before_techspec: []\n  after_techspec: []\n  before_validate: []\n  after_validate: []\n";

package/dist/templates.js

@@ -338,6 +338,8 @@ Return JSON object with keys:
 Rules:
 - do NOT invent missing critical content
 - keep wording concise and concrete
+- preserve original language and Unicode characters exactly from brief
+- never transliterate Turkish letters (ç, ğ, ı, İ, ö, ş, ü) into ASCII
 - if critical field is missing, return empty and low confidence (<0.7)
 - assign deterministic IDs: goals => G1..Gn, features => F1..Fn, constraints => C1..Cn
 - input files are read-only; never modify, summarize, or rewrite \`brief.md\` in-place

package/dist/utils.d.ts

@@ -2,5 +2,6 @@ export declare function ensureDir(dirPath: string): Promise<void>;
 export declare function fileExists(filePath: string): Promise<boolean>;
 export declare function readJsonFile<T>(filePath: string): Promise<T>;
 export declare function timestampSlug(date?: Date): string;
+export declare function artifactFileStamp(date?: Date): string;
 export declare function listFilesSortedByMtime(dirPath: string): Promise<string[]>;
 export declare function isPathInside(parentDir: string, candidatePath: string): boolean;

package/dist/utils.js

@@ -7,6 +7,7 @@ exports.ensureDir = ensureDir;
 exports.fileExists = fileExists;
 exports.readJsonFile = readJsonFile;
 exports.timestampSlug = timestampSlug;
+exports.artifactFileStamp = artifactFileStamp;
 exports.listFilesSortedByMtime = listFilesSortedByMtime;
 exports.isPathInside = isPathInside;
 const promises_1 = __importDefault(require("node:fs/promises"));
@@ -30,6 +31,18 @@ async function readJsonFile(filePath) {
 function timestampSlug(date = new Date()) {
     return date.toISOString().replace(/[:.]/g, "-");
 }
+function pad2(value) {
+    return String(value).padStart(2, "0");
+}
+function artifactFileStamp(date = new Date()) {
+    const year = date.getFullYear();
+    const month = pad2(date.getMonth() + 1);
+    const day = pad2(date.getDate());
+    const hour = pad2(date.getHours());
+    const minute = pad2(date.getMinutes());
+    const second = pad2(date.getSeconds());
+    return `${year}${month}${day}-${hour}${minute}${second}`;
+}
 async function listFilesSortedByMtime(dirPath) {
     const exists = await fileExists(dirPath);
     if (!exists)

package/dist/validator.js

@@ -45,10 +45,6 @@ async function validateSchema(cwd, artifactType, doc, requiredHeadingsOverride)
         }
     }
     const sections = (0, markdown_1.sectionTextMap)(doc.body);
-    const trMode = String(doc.frontmatter.language ?? "").toLowerCase().startsWith("tr");
-    if (trMode) {
-        return { issues, requiredHeadings: [] };
-    }
     for (const heading of requiredHeadings) {
         if (!doc.body.includes(heading)) {
             issues.push({

package/dist/workflow-commands.js

@@ -9,7 +9,8 @@ const BASE_WORKFLOW_COMMANDS = [
     { name: "prodo-wireframe", cliSubcommand: "wireframe", description: "Generate wireframe artifact." },
     { name: "prodo-stories", cliSubcommand: "stories", description: "Generate stories artifact." },
     { name: "prodo-techspec", cliSubcommand: "techspec", description: "Generate technical specification artifact." },
-    { name: "prodo-validate", cliSubcommand: "validate", description: "Run schema and cross-artifact consistency validation." }
+    { name: "prodo-validate", cliSubcommand: "validate", description: "Run schema and cross-artifact consistency validation." },
+    { name: "prodo-fix", cliSubcommand: "fix", description: "Auto-fix artifacts based on validation report and brief." }
 ];
 exports.WORKFLOW_COMMANDS = BASE_WORKFLOW_COMMANDS;
 function buildWorkflowCommands(artifactTypes) {

package/package.json

@@ -1,45 +1,74 @@
-{
-  "name": "@shahmarasy/prodo",
-  "version": "0.1.3",
-  "description": "CLI-first, prompt-powered product artifact kit",
-  "main": "dist/cli.js",
-  "types": "dist/cli.d.ts",
-  "bin": {
-    "prodo": "bin/prodo.cjs"
-  },
-  "files": [
-    "bin/",
-    "dist/",
-    "templates/",
-    "presets/",
-    "src/",
-    "README.md"
-  ],
-  "publishConfig": {
-    "access": "public"
-  },
-  "engines": {
-    "node": ">=20"
-  },
-  "scripts": {
-    "build": "tsc -p tsconfig.json",
-    "test": "npm run build && node --test tests/*.test.cjs",
-    "verify:release": "npm run build && node scripts/verify-release-build.cjs"
-  },
-  "keywords": [],
-  "author": "",
-  "license": "ISC",
-  "dependencies": {
-    "@clack/prompts": "^1.1.0",
-    "ajv": "^8.18.0",
-    "ajv-formats": "^3.0.1",
-    "commander": "^14.0.3",
-    "gray-matter": "^4.0.3",
-    "js-yaml": "^4.1.1"
-  },
-  "devDependencies": {
-    "@types/js-yaml": "^4.0.9",
-    "@types/node": "^25.5.0",
-    "typescript": "^5.9.3"
-  }
-}
+{
+  "name": "@shahmarasy/prodo",
+  "version": "0.1.5",
+  "description": "CLI-first, prompt-powered product artifact kit",
+  "main": "dist/cli/index.js",
+  "types": "dist/cli/index.d.ts",
+  "bin": {
+    "prodo": "bin/prodo.cjs"
+  },
+  "files": [
+    "bin/",
+    "dist/",
+    "templates/",
+    "presets/",
+    "src/",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "engines": {
+    "node": ">=20"
+  },
+  "scripts": {
+    "build:ts": "tsc -p tsconfig.json",
+    "build:i18n": "node -e \"const fs=require('fs');const p=require('path');['en','tr'].forEach(l=>{const s=p.join('src','i18n',l+'.json');const d=p.join('dist','i18n',l+'.json');fs.copyFileSync(s,d)})\"",
+    "build": "npm run build:ts && npm run build:i18n",
+    "test": "npm run build && node --test tests/*.test.cjs",
+    "verify:release": "npm run build && node scripts/verify-release-build.cjs"
+  },
+  "keywords": [
+    "product-management",
+    "prd",
+    "ai-agents",
+    "codex",
+    "claude",
+    "gemini",
+    "document-generation",
+    "cli"
+  ],
+  "author": "Shahmarasy",
+  "license": "MIT",
+  "dependencies": {
+    "@clack/prompts": "^1.1.0",
+    "ajv": "^8.18.0",
+    "ajv-formats": "^3.0.1",
+    "commander": "^14.0.3",
+    "gray-matter": "^4.0.3",
+    "js-yaml": "^4.1.1",
+    "nunjucks": "^3.2.4"
+  },
+  "peerDependencies": {
+    "openai": ">=4.0.0",
+    "@anthropic-ai/sdk": ">=0.20.0",
+    "@google/generative-ai": ">=0.1.0"
+  },
+  "peerDependenciesMeta": {
+    "openai": {
+      "optional": true
+    },
+    "@anthropic-ai/sdk": {
+      "optional": true
+    },
+    "@google/generative-ai": {
+      "optional": true
+    }
+  },
+  "devDependencies": {
+    "@types/js-yaml": "^4.0.9",
+    "@types/node": "^25.5.0",
+    "@types/nunjucks": "^3.2.6",
+    "typescript": "^5.9.3"
+  }
+}

package/presets/fintech/preset.json

@@ -1 +1,48 @@
-{"name":"fintech","priority":1,"min_prodo_version":"0.1.0","version":"1.0.0"}
+{
+  "name": "fintech",
+  "display_name": "Financial Technology (FinTech)",
+  "description": "Comprehensive preset for fintech and financial services products with regulatory compliance, security, and transaction-focused features",
+  "category": "domain-specific",
+  "priority": 1,
+  "min_prodo_version": "0.1.0",
+  "version": "1.0.0",
+  "metadata": {
+    "domain": "Financial Technology",
+    "industry_focus": ["Banking", "Payment Processing", "Investment Management", "Lending", "Crypto/Blockchain"],
+    "compliance_required": ["KYC/AML", "PCI DSS", "SOC 2", "GDPR", "Regulatory Standards"],
+    "security_level": "critical",
+    "data_sensitivity": "highly-sensitive"
+  },
+  "preset_features": {
+    "domain_expertise": [
+      "Regulatory compliance (KYC, AML, SCA)",
+      "Security & encryption standards",
+      "Payment gateway integration",
+      "Transaction management & reconciliation",
+      "Risk management & fraud detection",
+      "Audit trails & compliance reporting"
+    ],
+    "templates_included": ["prd"],
+    "context_enrichment": {
+      "user_personas": ["Compliance Officer", "Risk Manager", "Treasury Manager", "Customer Service", "Auditor"],
+      "success_metrics": ["Compliance rate", "Transaction volume", "Fraud detection rate", "Settlement time", "System uptime"],
+      "constraints": ["Regulatory deadlines", "Security mandates", "Data residency", "Transaction limits", "Audit requirements"]
+    }
+  },
+  "agent_requirements": {
+    "required_expertise": [
+      "Financial services domain knowledge",
+      "Regulatory compliance understanding",
+      "Security-first mindset",
+      "Risk assessment capability"
+    ],
+    "recommended_agents": ["Product Manager (Finance)", "Compliance Specialist", "Security Architect"],
+    "critical_validation": ["Compliance checklist", "Security review", "Risk assessment"]
+  },
+  "prompt_configuration": {
+    "tone": "Professional, compliance-focused, security-conscious",
+    "terminology_style": "industry-standard (fintech, KYC, AML, SCA, PCI DSS)",
+    "risk_tolerance": "zero-tolerance for security/compliance violations",
+    "documentation_level": "comprehensive (audit trail required)"
+  }
+}

package/presets/fintech/prompts/prd.md

@@ -1,3 +1,100 @@
-Preset: fintech
+# Fintech Preset - PRD Generation Context
 
-Use domain-specific terminology and constraints for fintech products.
+## Preset Overview
+**Domain**: Financial Technology (FinTech)
+**Focus**: Regulatory compliance, security, transaction integrity, fraud prevention
+**Target Industries**: Banking, Payment Processing, Investment Management, Lending, Blockchain
+
+## Critical Requirements for FinTech Products
+
+### 1. Regulatory Compliance
+- **KYC/AML**: Know Your Customer, Anti-Money Laundering regulations
+- **PCI DSS**: Payment Card Industry Data Security Standard (Level 1-4)
+- **SOC 2**: System and Organization Controls compliance
+- **GDPR/Regional**: Data privacy and regional financial regulations
+- **Audit Trail**: Complete transaction and action audit logs required
+
+### 2. Security Requirements
+- **Encryption**: End-to-end encryption for sensitive data (at-rest & in-transit)
+- **Authentication**: Multi-factor authentication (MFA) mandatory
+- **Authorization**: Role-based access control (RBAC) with least privilege
+- **Fraud Detection**: Real-time anomaly detection and transaction monitoring
+- **Penetration Testing**: Regular security audits and penetration tests
+
+### 3. Transaction Management
+- **Settlement**: Fast settlement with reconciliation (T+0, T+1, etc.)
+- **Atomicity**: All-or-nothing transaction guarantees
+- **Idempotency**: Prevent duplicate transactions
+- **Error Handling**: Graceful failures with clear audit trails
+- **Dispute Resolution**: Clear process for chargebacks and disputes
+
+### 4. Risk Management
+- **Fraud Detection**: ML-based anomaly detection and rule engines
+- **Risk Assessment**: Transaction risk scoring and limits
+- **Compliance Monitoring**: Continuous regulatory compliance monitoring
+- **Incident Response**: Clear escalation and response procedures
+- **Business Continuity**: Disaster recovery and failover strategies
+
+### 5. User Personas (FinTech Specific)
+- **Compliance Officer**: Regulatory requirements, audit trails, risk reporting
+- **Risk Manager**: Fraud patterns, transaction limits, risk scoring
+- **Treasury Manager**: Settlement timing, liquidity management, cash flow
+- **Customer Service**: Transaction history, dispute handling, user support
+- **Auditor**: Complete audit trails, compliance reports, system integrity
+
+### 6. Success Metrics (FinTech Specific)
+- **Compliance Rate**: 100% regulatory adherence (zero violations target)
+- **Transaction Volume**: Daily/monthly transaction throughput
+- **Fraud Detection Rate**: % of fraudulent transactions caught pre-settlement
+- **Settlement Speed**: Average time to settlement completion
+- **System Uptime**: 99.99%+ availability (critical infrastructure)
+- **Customer Trust**: Chargeback rate, dispute resolution time
+
+### 7. Key Constraints
+- **Regulatory Deadlines**: Compliance cutoffs, reporting deadlines
+- **Data Residency**: Geographic restrictions on data storage
+- **Transaction Limits**: Daily/monthly limits per user/transaction type
+- **Integration Requirements**: Payment gateways, banking APIs, clearing houses
+- **Audit Requirements**: Immutable logs, compliance reports, regulatory filings
+
+## PRD Generation Guidelines
+
+### Domain-Specific Terminology
+Use fintech-standard terminology:
+- KYC (Know Your Customer) vs. identity verification
+- AML (Anti-Money Laundering) vs. fraud prevention
+- SCA (Strong Customer Authentication) vs. verification
+- PCI DSS (Payment Card Industry Standard) vs. security
+- Settlement vs. transaction completion
+- Reconciliation vs. balance verification
+
+### Feature Prioritization
+1. **Compliance first**: All features must meet regulatory requirements
+2. **Security second**: Security cannot be compromised for features
+3. **User experience**: Within compliance and security boundaries
+4. **Performance**: Transaction speed critical for user satisfaction
+
+### Risk Assessment
+Flag high-risk features:
+- ⚠️ Features involving cross-border transactions
+- ⚠️ Features with regulatory uncertainty
+- ⚠️ Features with no clear audit trail mechanism
+- ⚠️ Features involving sensitive financial data
+
+### Documentation Standards
+- **Compliance Mapping**: Each feature → applicable regulations
+- **Security Justification**: Why security approach chosen
+- **Audit Trail**: How feature activities are logged
+- **Error Scenarios**: Failure modes and recovery
+- **Rollback Strategy**: How to undo transactions if needed
+
+## Validation Checklist
+Before finalizing PRD, verify:
+- ✅ All features have compliance mapping
+- ✅ Security requirements explicitly stated
+- ✅ Audit trail mechanisms defined
+- ✅ Risk assessment completed
+- ✅ Regulatory deadlines documented
+- ✅ User personas fintech-specific
+- ✅ Success metrics measurable
+- ✅ Escalation procedures clear

package/presets/marketplace/preset.json

@@ -1 +1,51 @@
-{"name":"marketplace","priority":1,"min_prodo_version":"0.1.0","version":"1.0.0"}
+{
+  "name": "marketplace",
+  "display_name": "Multi-Sided Marketplace",
+  "description": "Comprehensive preset for marketplace platforms with multi-stakeholder support, trust mechanisms, commission systems, and community features",
+  "category": "domain-specific",
+  "priority": 1,
+  "min_prodo_version": "0.1.0",
+  "version": "1.0.0",
+  "metadata": {
+    "domain": "E-Commerce & Marketplace",
+    "industry_focus": ["B2C Marketplace", "C2C Marketplace", "Gig Economy", "Subscription Services", "SaaS Marketplace"],
+    "marketplace_model": ["commission-based", "subscription-based", "freemium", "hybrid"],
+    "key_complexity": "multi-stakeholder coordination",
+    "trust_requirement": "critical"
+  },
+  "preset_features": {
+    "domain_expertise": [
+      "Multi-stakeholder coordination (buyers, sellers, platform)",
+      "Trust & safety mechanisms (verification, reviews, ratings)",
+      "Commission & payment systems",
+      "Dispute resolution & conflict management",
+      "Community moderation & content policies",
+      "Recommendation algorithms & discovery",
+      "Supply & demand balancing",
+      "Seller onboarding & quality assurance"
+    ],
+    "templates_included": ["prd"],
+    "context_enrichment": {
+      "user_personas": ["Buyer", "Seller", "Platform Operator", "Support Agent", "Community Moderator"],
+      "success_metrics": ["Gross merchandise volume (GMV)", "Seller growth rate", "Customer retention", "Review authenticity", "Dispute rate"],
+      "constraints": ["Trust & safety standards", "Commission structure", "Seller quality", "Fraud prevention", "Community guidelines"]
+    }
+  },
+  "agent_requirements": {
+    "required_expertise": [
+      "Multi-sided marketplace dynamics",
+      "Trust and safety framework design",
+      "Seller quality management",
+      "Community management",
+      "Conflict resolution strategies"
+    ],
+    "recommended_agents": ["Platform PM", "Trust & Safety Lead", "Seller Success Manager", "Community Manager"],
+    "critical_validation": ["Trust scoring mechanism", "Dispute resolution process", "Seller quality criteria"]
+  },
+  "prompt_configuration": {
+    "tone": "Community-focused, trust-centered, multi-perspective",
+    "stakeholder_focus": ["buyer-experience", "seller-success", "platform-sustainability"],
+    "conflict_resolution": "fair-for-all-parties",
+    "documentation_level": "detailed (policies and procedures required)"
+  }
+}