fraim-framework 2.0.36 → 2.0.38

package/registry/workflows/business-development/ideate-business-opportunity.md

@@ -1,55 +0,0 @@
-# Workflow: ideate-business-opportunity
-
-**Path:** `workflows/business-development/ideate-business-opportunity.md`
-
----
-
-# Ideate Business Opportunity Phase
-
-## INTENT
-To help founders and product owners navigate the broad, fuzzy front-end of product development. This workflow guides the transition from a "vague space" to "concrete feature deliverables" through interactive brainstorming and research.
-
-## PRINCIPLES
-- **Interactive Exploration**: This is not a one-shot process. It requires multiple cycles of feedback.
-- **Founder-Led**: The founder's intuition is the compass; the agent provides the map and vehicle.
-- **Outcome-Oriented**: The goal is NOT just a list of ideas, but a prioritized, repo-ready backlog.
-- **Divergent Thinking**:
-    - **Defer Judgment**: Do not criticize or discard ideas in the early stages.
-    - **Go for Volume**: Quantity often leads to quality. Aim for a wide range of options.
-    - **Cross-Pollinate**: Combine unrelated concepts or industries to find unique angles.
-    - **Challenge Constraints**: Ask "What if X wasn't a limitation?"
-    - **Interactive Refinement**: Use feedback to branch into new directions, even if they seem tangential.
-
-## IDEATION WORKFLOW
-
-### Step 1: Broad Mapping (Divergent)
-- Ask the founder for their initial "Spark" or "Space".
-- **Exploration Protocol**: 
-    - When an idea is proposed, respond with 3-5 distinct "What if" scenarios or variations.
-    - Avoid saying "That's not possible" or "That's too expensive" during this stage.
-    - Use tools to describe or visualize the space before narrowing down.
-- Generate 3-5 distinct sub-spaces or "angles" within that spark.
-- **Exit Criteria**: Founder chooses 1-2 directions to explore further.
-
-### Step 2: Interactive Research & Validation
-- For the chosen directions, research:
-    - Existing competitors (even indirect ones).
-    - Potential user personas.
-    - Technical feasibility (high-level).
-- Present findings and ask for "Pivot or Persevere" feedback.
-
-### Step 3: Feature Synthesis (Convergent)
-- Based on the validated direction, brainstorm a set of potential features.
-- Map features against: **Complexity** vs. **Value**.
-- **Exit Criteria**: Founder approves a "Hero" feature and 3-5 supporting features.
-
-### Step 4: Repository Documentation
-- Formalize the findings into a report.
-- **ACTION**: Call `get_fraim_file({ path: "templates/business-development/IDEATION-REPORT-TEMPLATE.md" })`.
-- Create `docs/ideation/{YYYYMMDD}-{project-name}.md`.
-- **Outcome**: A file that a PM agent can use to write `specs`.
-
-## OUTPUT
-- `docs/ideation/[project].md`
-- Prioritized Feature Backlog
-- High-level Vision & Persona Map

package/registry/workflows/business-development/price-product.md

@@ -1,325 +0,0 @@
-## INTENT
-
-To create a comprehensive **pricing + packaging strategy** for any product that:
-
-* clarifies who the product is for and what outcomes it delivers,
-* defines SKUs, tiers, add-ons, and the pricing metric,
-* ties pricing to unit economics and scalability,
-* and positions the product clearly against competitors and substitutes.
-
----
-
-## PRINCIPLES
-
-* **Outcome-first**: Price and packaging must map to customer outcomes, not features
-* **Simple packaging**: Fewer SKUs, clearer upgrade path, lower decision friction
-* **Credible claims**: Use evidence, ranges, and benchmarks; avoid brittle promises
-* **Economic grounding**: Every SKU must connect to COGS, margin targets, and scalability limits
-* **Competitive honesty**: Don’t invent competitor pricing; cite sources or state “not public”
-* **Procurement-friendly**: Prefer predictable add-ons/tiers over opaque metered token pricing
-* **Reusable framework**: The same structure should work for B2B, B2C, SaaS, services, and hybrid models
-* **Citations required**: All competitive facts should be sourced with dates
-
----
-
-## WORKFLOW OVERVIEW
-
-This workflow produces a single comprehensive document (`docs/business-development/pricing-strategy.md`) that follows the template in `templates/business-development/PRICING-STRATEGY-TEMPLATE.md`.
-
----
-
-## STEP-BY-STEP WORKFLOW
-
-### Step 1: Product Context Gathering
-
-**Objective:** Understand the product, buyer, and constraints.
-
-**Actions:**
-
-1. Capture product one-liner and primary outcomes
-2. Identify who pays vs who uses (buyer vs end user)
-3. Define product type: SaaS, usage-based, services, hybrid
-4. Capture current stage: MVP/beta/GA and current pricing (if any)
-5. Capture business constraints:
-
-   * margin targets
-   * delivery capacity (if services/hybrid)
-   * sales motion (self-serve vs sales-led)
-   * contract constraints (annual, PO, procurement)
-
-**Output:** Product context section (10–20 bullets)
-
----
-
-### Step 2: Customer Segmentation (ICP + willingness-to-pay)
-
-**Objective:** Identify 3–7 segments with different value and pricing sensitivity.
-
-**Process:**
-
-1. Brainstorm segments by pain intensity and frequency
-2. Score each segment:
-
-   * Pain intensity
-   * Frequency of use
-   * Budget owner clarity
-   * Willingness to pay
-   * Ease of reach (distribution)
-   * Competitive alternatives
-3. Select 2–4 priority segments (tip-of-the-spear)
-4. For each segment document:
-
-   * Customer profile
-   * Job-to-be-done
-   * Core pains
-   * Current alternatives
-   * Buying process and budget source
-   * Success metrics they care about
-
-**Output:** Segment cards + segment comparison table
-
----
-
-### Step 3: Outcome Narrative (the “why” before pricing)
-
-**Objective:** Build an exec-readable narrative that sets up the pricing table.
-
-**Actions:**
-
-1. Write a headline framing value (speed, cost, quality, risk reduction, revenue)
-2. Explain why outcomes vary with usage maturity (if applicable)
-3. Describe the customer journey in 3 “paths” or “maturity levels” (optional but powerful):
-
-   * Self-serve power user
-   * Guided/coached adopter
-   * Managed delivery / done-for-you (if offered)
-4. Add a clear CTA (“If you’re here and want to be there…”)
-
-**Output:** One-page narrative suitable for a brochure
-
----
-
-### Step 4: Define Packaging (SKUs, tiers, and boundaries)
-
-**Objective:** Create a SKU/tier map that is simple and scalable.
-
-**Actions:**
-
-1. Define 3–6 SKUs by **customer need** (e.g., role-based, module-based, team-based, use-case-based)
-2. Define tiers (Good/Better/Best) or maturity tiers (Self-serve / Guided / Managed)
-3. For each SKU/tier define:
-
-   * Outcomes delivered
-   * Included capabilities
-   * Exclusions/limits (what’s not included)
-   * Primary success metrics
-   * Who it’s for (buyer/user)
-4. Ensure upgrade path is explicit:
-
-   * When to move up a tier
-   * What triggers expansion (more users, more volume, more scope)
-
-**Output:** SKU catalog + tier comparison table
-
----
-
-### Step 5: Choose a Pricing Metric (what you charge “per”)
-
-**Objective:** Pick a pricing unit that scales with value and is hard to game.
-
-**Common metrics (choose 1 primary):**
-
-* Per user / seat
-* Per team / workspace
-* Per project
-* Per workflow/run
-* Per asset (e.g., report, doc, build, analysis)
-* Per integration
-* % of spend / % of savings (rare; needs strong proof)
-* Tiered capacity bundles (recommended for predictability)
-
-**Selection criteria:**
-
-* Aligns with value
-* Understandable to buyers
-* Predictable billing
-* Resistant to abuse
-* Matches cost-to-serve drivers
-
-**Output:** Pricing metric decision + rationale + alternatives rejected
-
----
-
-### Step 6: Build the Price List (tables first, numbers second)
-
-**Objective:** Produce clean pricing tables and packaging rules.
-
-**Actions:**
-
-1. Start with a single “hero” table (e.g., 3 columns × 3 rows):
-
-   * Columns = tiers/maturity levels
-   * Rows = what you get (outcomes), what you save/earn, what you pay
-2. Expand into:
-
-   * SKU × tier grid (if needed)
-   * Add-on list
-3. Define discounting:
-
-   * annual prepay discount
-   * volume discount principles
-   * partner/channel margins (if relevant)
-
-**Output:** Pricing tables + add-ons + discount rules
-
----
-
-### Step 7: Unit Economics + Scalability Model
-
-**Objective:** Ensure pricing is profitable, defensible, and scalable.
-
-**Actions:**
-
-1. Identify COGS drivers:
-
-   * compute/infrastructure
-   * support burden
-   * onboarding/training
-   * professional services / delivery labor
-   * third-party fees
-2. For each SKU/tier estimate:
-
-   * expected usage / volume
-   * expected support hours
-   * expected compute cost
-   * gross margin target
-3. Model edge cases:
-
-   * power users
-   * low-usage churners
-   * heavy-support customers
-4. Define guardrails:
-
-   * caps
-   * fair-use limits
-   * paid add-on packs for overflow
-   * staffing ratios (if managed services)
-
-**Output:** Unit economics assumptions table + margin estimates by SKU/tier
-
----
-
-### Step 8: Competitive Landscape & Positioning (research required)
-
-**Objective:** Build a credible pricing/positioning story vs alternatives.
-
-**Actions:**
-
-1. Identify 10–20 competitors/substitutes across:
-
-   * direct competitors
-   * adjacent tools
-   * “do nothing/manual”
-   * agencies/contractors (if relevant)
-2. For each competitor:
-
-   * what they sell
-   * who buys
-   * pricing model (cite sources, include dates)
-   * strengths/weaknesses vs your product
-3. Synthesize:
-
-   * differentiation pillars (3–5)
-   * win/loss reasons
-   * objection handling talk tracks
-
-**Output:** Competitive matrix + positioning section (with citations)
-
----
-
-### Step 9: Risks, Objections, and Mitigations
-
-**Objective:** Preempt the hardest questions and reduce churn risk.
-
-**Actions:**
-
-* Identify 5–10 risks:
-
-  * credibility of claims
-  * adoption friction
-  * pricing confusion
-  * margin erosion
-  * scaling services
-  * procurement/security concerns
-  * competitor response
-* For each:
-
-  * impact
-  * mitigation
-  * owner
-  * measurable leading indicator
-
-**Output:** Risk table
-
----
-
-### Step 10: Validation Plan (pricing experiments + rollout)
-
-**Objective:** Test assumptions quickly before locking prices.
-
-**Actions:**
-
-1. Define experiments:
-
-   * price sensitivity interviews (Van Westendorp / Gabor-Granger style)
-   * landing page A/B price anchoring
-   * pilot offers with 2–3 packaging variants
-   * sales-led quote testing
-2. Define metrics:
-
-   * conversion
-   * activation/time-to-value
-   * expansion
-   * churn
-   * support burden
-   * gross margin
-3. Create 30/60/90 day plan
-
-**Output:** Validation plan + timeline + decision points
-
----
-
-## References
-- All citations with date + URL
-```
-
----
-
-## QUALITY CHECKLIST
-
-### Content
-
-* [ ] Pricing is outcome-first, not feature-first
-* [ ] SKUs/tiers are simple with a clear upgrade path
-* [ ] Pricing metric is understandable and predictable
-* [ ] Add-ons reduce edge-case margin risk
-* [ ] Sales motion is supported (self-serve vs sales-led)
-
-### Economics
-
-* [ ] COGS drivers identified and bounded
-* [ ] Gross margin targets by tier are explicit
-* [ ] Guardrails (caps/add-ons) prevent abuse and margin collapse
-
-### Competitive
-
-* [ ] No invented competitor pricing
-* [ ] Citations + dates included for competitive facts
-* [ ] Win/loss reasons are honest and actionable
-
-### Validation
-
-* [ ] At least 3 pricing experiments defined
-* [ ] Metrics are clear and decision points are scheduled
-
----

package/registry/workflows/convert-to-pdf.md

@@ -1,235 +0,0 @@
-# Convert to PDF Workflow
-
-## INTENT
-To provide agents with a reliable workflow for converting markdown files to professional PDF documents, enabling seamless document sharing and archival while maintaining formatting integrity and visual appeal.
-
-## PRINCIPLES
-- **Format Preservation**: Maintain all markdown formatting including tables, code blocks, and images
-- **Professional Output**: Generate clean, readable PDFs suitable for business use
-- **Flexible Configuration**: Support various paper formats, margins, and styling options
-- **Error Resilience**: Handle common conversion issues gracefully with clear error messages
-- **Cross-Platform Compatibility**: Work consistently across Windows, macOS, and Linux
-
-## Overview
-This workflow guides agents through converting markdown files to PDF format using the markdown-to-pdf script. The conversion maintains formatting, supports code highlighting, tables, and images while producing professional-looking PDF documents.
-
-## When to Use
-- User requests converting markdown documentation to PDF
-- Need to generate PDF reports from markdown content
-- Creating printable versions of specifications or documentation
-- Sharing formatted documents with stakeholders who prefer PDF format
-- Archiving documentation in a portable format
-
-## Prerequisites
-Before using this workflow, ensure the following dependencies are installed:
-
-```bash
-npm install puppeteer markdown-it markdown-it-highlightjs
-```
-
-## Script Location
-The conversion script is synced to: `~/.fraim/scripts/markdown-to-pdf.js`
-
-## Workflow Steps
-
-### Phase 1: Validate Environment
-
-1. **Check Dependencies**
-   ```bash
-   node -e "console.log('puppeteer:', require.resolve('puppeteer')); console.log('markdown-it:', require.resolve('markdown-it')); console.log('markdown-it-highlightjs:', require.resolve('markdown-it-highlightjs'));"
-   ```
-
-2. **Verify Script Availability**
-   - Confirm `~/.fraim/scripts/markdown-to-pdf.js` exists
-   - Check script permissions (executable on Unix systems)
-
-3. **Test Basic Functionality**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js --help
-   ```
-
-### Phase 2: Prepare Input
-
-1. **Validate Input File**
-   - Confirm markdown file exists and is readable
-   - Check for any syntax issues in markdown
-   - Verify image paths are correct and accessible
-
-2. **Determine Output Requirements**
-   - Ask user about desired output location
-   - Confirm paper format preferences (A4, Letter, etc.)
-   - Check if custom styling is needed
-   - Determine header/footer requirements
-
-3. **Prepare Output Directory**
-   - Ensure output directory exists
-   - Verify write permissions
-
-### Phase 3: Execute Conversion
-
-1. **Basic Conversion**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js <input.md>
-   ```
-
-2. **Advanced Conversion with Options**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js <input.md> [output.pdf] [options]
-   ```
-
-3. **Monitor Progress**
-   - Watch for error messages
-   - Verify successful completion
-   - Check output file size and accessibility
-
-### Phase 4: Validate Output
-
-1. **Verify PDF Generation**
-   - Confirm PDF file was created
-   - Check file size is reasonable
-   - Verify file is not corrupted
-
-2. **Quality Check**
-   - Review formatting preservation
-   - Check image rendering
-   - Verify code block highlighting
-   - Confirm table alignment
-
-3. **User Acceptance**
-   - Share output location with user
-   - Confirm output meets requirements
-   - Offer to regenerate with different options if needed
-
-### Available Options
-
-| Option | Description | Example |
-|--------|-------------|---------|
-| `--format <format>` | Paper format (A4, Letter, Legal, etc.) | `--format Letter` |
-| `--margin <margin>` | Page margins in inches | `--margin 1` |
-| `--css <file>` | Custom CSS file for styling | `--css custom.css` |
-| `--header <text>` | Header text | `--header "Company Report"` |
-| `--footer <text>` | Footer text | `--footer "Page <span class='pageNumber'></span>"` |
-| `--landscape` | Use landscape orientation | `--landscape` |
-| `--no-background` | Disable background graphics | `--no-background` |
-
-### Common Examples
-
-1. **Basic conversion:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js README.md
-   ```
-
-2. **Specify output location:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js docs/spec.md output/specification.pdf
-   ```
-
-3. **Letter format with custom margins:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js report.md --format Letter --margin 0.75
-   ```
-
-4. **With custom styling:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js document.md --css styles/custom.css --header "Project Documentation"
-   ```
-
-5. **Landscape orientation:**
-   ```bash
-   node ~/.fraim/scripts/markdown-to-pdf.js wide-table.md --landscape --format A3
-   ```
-
-## Agent Instructions
-
-When a user requests markdown to PDF conversion:
-
-1. **Identify the source file(s)**: Confirm which markdown file(s) need to be converted
-2. **Check dependencies**: Verify that required npm packages are installed
-3. **Determine output requirements**: Ask about:
-   - Desired output location
-   - Paper format preferences
-   - Custom styling needs
-   - Header/footer requirements
-4. **Execute conversion**: Run the appropriate command with the specified options
-5. **Verify output**: Confirm the PDF was generated successfully and meets requirements
-
-### Error Handling
-
-If the script fails:
-- Check that all dependencies are installed
-- Verify the input file exists and is readable
-- Ensure the output directory is writable
-- Check for any syntax errors in the markdown file
-
-### Troubleshooting Common Issues
-
-1. **Missing dependencies**: Install required packages with npm
-2. **Permission errors**: Ensure write permissions for output directory
-3. **Large files**: Consider breaking large markdown files into smaller sections
-4. **Image issues**: Verify image paths are correct and accessible
-5. **Font rendering**: Use web-safe fonts or include custom font CSS
-
-## Customization
-
-### Custom CSS Styling
-Create a CSS file to customize the PDF appearance:
-
-```css
-/* custom-style.css */
-body {
-  font-family: 'Times New Roman', serif;
-  font-size: 12pt;
-}
-
-h1 {
-  color: #2c3e50;
-  border-bottom: 3px solid #3498db;
-}
-
-code {
-  background-color: #f0f0f0;
-  border: 1px solid #ccc;
-}
-
-@page {
-  margin: 1in;
-  @top-center {
-    content: "Confidential Document";
-  }
-}
-```
-
-### Batch Processing
-For converting multiple files, create a simple loop:
-
-```bash
-for file in docs/*.md; do
-  node ~/.fraim/scripts/markdown-to-pdf.js "$file" "output/$(basename "$file" .md).pdf"
-done
-```
-
-## Quality Assurance
-
-After conversion, verify:
-- All content is present and properly formatted
-- Images are displayed correctly
-- Code blocks maintain syntax highlighting
-- Tables are properly aligned
-- Page breaks occur at appropriate locations
-- Headers and footers appear as expected
-
-## Best Practices
-
-1. **Test with sample content** before processing important documents
-2. **Use consistent styling** across related documents
-3. **Optimize images** for better PDF file size
-4. **Consider accessibility** when choosing fonts and colors
-5. **Version control** both source markdown and generated PDFs when appropriate
-
-## Integration with Other Workflows
-
-This workflow can be combined with:
-- Documentation generation workflows
-- Report automation processes
-- CI/CD pipelines for document publishing
-- Content review and approval workflows