Prodig Suites Setup

# Prodig Suites Memory Index

**Created:** {YYYY-MM-DD}
**Last Updated:** {YYYY-MM-DD}

Welcome to Prodig Suites! This is the shared memory system that maintains context across all your product creation sessions.

## Active Products

No products yet. Start your first product with:
- "I want to create a course about..."
- "Help me build a template pack for..."
- "I have an idea for a SaaS product..."
- "I want to productize my service for..."

## Recent Activity

*No activity yet — this will be populated as you work.*

## Curated Files Status

| File | Status | Description |
|------|--------|-------------|
| product-context.md | Pending | Active product definition |
| market-intelligence.md | Pending | Research synthesis |
| audience-intelligence.md | Pending | Customer insights |
| product-decisions.md | Pending | Decision history |
| output-standards.md | Ready | Quality criteria (has defaults) |

## Product Types

Prodig Suites supports four product families:

1. **Knowledge Products** — Courses, ebooks, guides, memberships
2. **Template Products** — Templates, prompt packs, digital kits
3. **Software Products** — SaaS, apps, AI tools
4. **Service Products** — Productized services, consulting packages

## How Memory Works

- **Daily files** capture session activity (chronological, append-only)
- **Curated files** hold structured knowledge (updated as you progress)
- **Index** (this file) provides quick orientation
- All agents share this memory, so context persists across sessions

## Quick Reference

| Skill | Purpose |
|-------|---------|
| paw-ps-agent-product-builder | Main coordinator — start here |
| paw-ps-discovery | Idea exploration and validation |
| paw-ps-research | Market and competitor research |
| paw-ps-audience | Customer research and personas |
| paw-ps-research-to-brief | Convert research into product brief |
| paw-ps-strategist | Product packaging and positioning |
| paw-ps-concept-to-product-plan | Transform brief into executor-ready plan |
| paw-ps-knowledge-executor | Build courses, ebooks, guides |
| paw-ps-template-executor | Build templates, prompt packs, kits |
| paw-ps-software-executor | Build SaaS, apps, AI tools |
| paw-ps-service-executor | Build productized services |
| paw-ps-product-package-assembler | Bundle into deliverable package |
| paw-ps-publish-ready-check | Evaluate production readiness |

## Getting Started

Tell me what you want to create, and I'll help you through the full journey from idea to production-ready product.

# Product Context

*No active product yet. This file will be populated when you start a product.*

## How to Use This File

This file captures the essential context for your active product:

- **Product Name** — Working title
- **Product Type** — Knowledge, Template, Software, or Service
- **Core Premise** — What it does and why
- **Target Audience** — Who it's for
- **Current Stage** — discovery, research, brief, execution

## Starting a Product

Tell the orchestrator:
- What product you want to create
- What type it might be (if you know)
- Who it's for (if you know)

# Market Intelligence

*Market research will be synthesized here.*

## Purpose

Captures competitive landscape, market positioning, and opportunity signals.

## Sections (populated by research)

- **Competitive Landscape** — Who else serves this market
- **Market Gaps** — Underserved needs and opportunities
- **Positioning Signals** — How to differentiate
- **Validation Points** — Evidence of demand

# Audience Intelligence

*Customer insights will be synthesized here.*

## Purpose

Captures deep understanding of target customers and their needs.

## Sections (populated by research)

- **Primary Persona** — Core customer profile
- **Pain Points** — Problems they're trying to solve
- **Desired Outcomes** — What success looks like
- **Buying Triggers** — What motivates purchase
- **Language Patterns** — How they describe their problems

# Product Decisions

*Key decisions will be logged here.*

## Purpose

Tracks important decisions made during product development with context for future reference.

## Decision Log Format

| Date | Decision | Rationale | Alternatives Considered |
|------|----------|-----------|------------------------|
| | | | |

## Why This Matters

- Provides context for future iterations
- Helps explain "why did we do X?"
- Prevents revisiting settled questions

# Output Standards

Quality criteria for Prodig Suites deliverables.

## Configured Quality Bar

**Current Setting:** {quality_bar from config}

### Quality Bar Definitions

| Level | Definition |
|-------|------------|
| draft | Complete structure with placeholder content |
| production-ready | Complete, no placeholders, usable by intended audience |
| publish-ready | Polished, formatted, ready for publication |
| sellable-ready | Complete, polished, ready to sell |

## Product-Type Standards

### Knowledge Products
- Clear learning objectives
- Logical progression
- Actionable content
- Complete materials

### Template Products
- Working templates
- Clear instructions
- Consistent formatting
- Reusable design

### Software Products
- Clear feature definition
- User flow documented
- Technical requirements stated
- MVP scope defined

### Service Products
- Clear offer structure
- Defined deliverables
- Scope boundaries
- Pricing logic

## Output Style

**Current Setting:** {output_style from config}

| Style | Description |
|-------|-------------|
| structured-practical | Clear sections, actionable, ready to use |
| narrative-engaging | Story-driven, conversational, engaging |
| technical-detailed | Comprehensive, thorough, documentation-heavy |

# Knowledge Products

Best practices and structures for courses, ebooks, guides, and memberships.

## Product Types

### Courses
- Define learning outcomes first
- Structure in modules → lessons → topics
- Include practice activities
- Plan assessments

### Ebooks/Guides
- Define reader transformation
- Structure in chapters → sections
- Include examples and templates
- Plan call-to-actions

### Memberships
- Define content pillars
- Plan release cadence
- Structure access levels
- Design community elements

## Output Structure

```text
knowledge-product/
├── curriculum.md        # Course outline or chapter structure
├── modules/
│   ├── module-1.md
│   └── ...
├── materials/           # Supporting materials
└── assets/              # Images, downloads, etc.
```

## Quality Checklist

- [ ] Learning objectives defined
- [ ] Logical progression verified
- [ ] Practice activities included
- [ ] All content complete (no placeholders)

# Template Products

Best practices for templates, prompt packs, and digital kits.

## Product Types

### Templates
- Solve specific problems
- Include clear instructions
- Use placeholder conventions
- Design for reusability

### Prompt Packs
- Group by use case
- Include example outputs
- Document parameters
- Provide variation templates

### Digital Kits
- Combine complementary assets
- Provide assembly guide
- Include source files
- Document dependencies

## Output Structure

```text
template-product/
├── templates/
│   └── template-1.{ext}
├── guide.md            # Usage instructions
├── examples/           # Example outputs
└── assets/             # Supporting files
```

## Quality Checklist

- [ ] Templates are functional
- [ ] Instructions are clear
- [ ] Formatting is consistent
- [ ] Design is reusable

# Software Products

Best practices for SaaS, apps, and AI tools.

## Product Types

### SaaS/Apps
- Define core value proposition
- Map user journeys
- Define MVP features
- Plan technical architecture

### AI Tools
- Define AI capabilities
- Document prompts/flows
- Plan integrations
- Design user interface

## Output Structure

```text
software-product/
├── prd-lite.md         # Product requirements
├── features/
│   └── feature-1.md
├── user-flows/
│   └── flow-1.md
└── technical/
    └── architecture.md
```

## Quality Checklist

- [ ] Value proposition clear
- [ ] MVP scope defined
- [ ] User flows documented
- [ ] Technical requirements stated

# Service Products

Best practices for productized services and consulting packages.

## Product Types

### Productized Services
- Define clear deliverables
- Set scope boundaries
- Standardize process
- Create pricing tiers

### Consulting Packages
- Define outcomes
- Structure engagements
- Create templates
- Document process

## Output Structure

```text
service-product/
├── offer.md            # Offer structure and pricing
├── deliverables/
│   └── deliverable-1.md
├── process.md          # Delivery process
└── templates/          # Service delivery templates
```

## Quality Checklist

- [ ] Deliverables are clear
- [ ] Scope is bounded
- [ ] Pricing is defined
- [ ] Process is documented

python3 ./scripts/merge-config.py \
  --config-path "{project-root}/.pawbytes/config/config.yaml" \
  --user-config-path "{project-root}/.pawbytes/config/config.user.yaml" \
  --module-yaml ./assets/module.yaml \
  --answers {temp-file}

python3 ./scripts/merge-help-csv.py \
  --target "{project-root}/.pawbytes/config/module-help.csv" \
  --source ./assets/module-help.csv \
  --module-code ps

## Setup Complete

### Configuration
- Default product mode: {value}
- Quality bar: {value}
- Output style: {value}
- Research depth: {value}

### Created Directories
- .pawbytes/prodig-suites/memory/paw-ps-sidecar/
- .pawbytes/prodig-suites/products/
- .pawbytes/prodig-suites/artifacts/

### Created Files
- index.md — Orientation file
- product-context.md — Active product context
- market-intelligence.md — Market research synthesis
- audience-intelligence.md — Customer insights
- product-decisions.md — Decision log
- output-standards.md — Quality criteria
- product-types/*.md — Product family guides

### Capability Status
{List available/missing optional capabilities}

### What's Next
Start with `paw-ps-agent-product-builder` to create your first product.