fraim-framework 2.0.27 → 2.0.30

package/registry/templates/marketing/HBR-ARTICLE-TEMPLATE.md

@@ -0,0 +1,66 @@
+# Template: HBR Article
+
+Use this template to capture the key checkpoints for every Harvard Business Review (or similar) thought leadership submission so any product team can execute the workflow without re-reading the original issue.
+
+## 1. Story Fit & Intent
+- **Working Title**:  
+- **Thesis/Angle**: Why this matters to HBR readers and how it advances the product strategy.  
+- **Target Section**: (Strategy / Leadership / Technology / etc.)  
+- **Why Now**: Timeliness, data trend, or customer insight.  
+- **Assigned Reviewers**: Marketing lead, product lead, exec reviewer.
+- **Central Message**:  
+- **Importance / Usefulness / Counterintuitive Angle**:  
+- **New Contribution**:  
+- **Why Leaders Must Know & How to Apply Today**:
+- **Source of Authority** (previous work, credentials, experience):
+
+## 2. HBR Guideline Checklist
+- [ ] Exclusive submission (no simultaneous submissions).  
+- [ ] Word count within HBR limits (note specific count).  
+- [ ] Proper byline and contributor list.  
+- [ ] Conflicts of interest disclosed (partners, competitors, etc.).  
+- [ ] Tone matches HBR's voice (professional, evidence-based).  
+- [ ] All supporting data, quotes, and frameworks cite originals.
+
+## 3. Research & References
+- **Customer Evidence**: List customer stories, interviews, or experiments.  
+- **Metrics/Data**: Include telemetry or KPIs.  
+- **Internal Experiments**: Describe what was learned.  
+- **External Sources**: Link to relevant HBR articles or academic references.  
+- **Attachments Needed**: Charts, tables, framework diagrams.
+- **Research & Examples That Back the Idea**:
+- **Academic / Professional / Personal Experience to Draw On**:
+
+## 4. Outline Structure
+- Hook + symptom/problem framing.  
+- Diagnostic + evidence blocks.  
+- Recommendations/practical steps for leaders.  
+- Closing call to action aligning to the product roadmap.  
+- Note attachments/reference for each section.
+
+## 5. Draft & Versions
+- **Draft Link/Location**:  
+- **Word Count**:  
+- **Key edits/versions**: (Version 1, 2, etc.)  
+- **Peer Review Notes**:  
+- **Exec Review Notes**:  
+- **Headline Variants**:
+
+## 6. Submission Plan
+- **Email Synopsis**: Subject line + elevator pitch.  
+- **Attachments**: Outline, draft, data, disclosure matrix.  
+- **Target Submission Window**: Date/time.  
+- **Submission Log**: Who submitted, when, portal used.  
+- **Follow-up Plan**: Reminder to track publication status and audience engagement.
+
+## 7. Launch Collateral
+- **Blog Post**: Angle, owner, status.  
+- **Newsletter Mention**: Message, owner.  
+- **Exec Update**: Key points.  
+- **Social/LinkedIn**: Thread plan, owner.  
+- **Measurement**: Metrics to track (clicks, reads, references).
+
+## 8. Post-Publication Notes
+- Feedback from reviewers or editors.  
+- Audience reactions.  
+- Learnings for the next HBR submission.

package/registry/workflows/bootstrap/create-architecture.md

@@ -11,7 +11,7 @@ To analyze the codebase and author a comprehensive `docs/architecture/architectu
    - Identify main entry points and architectural patterns.
 
 2. **Author Architecture Document**
-   - Locate the `ARCHITECTURE-TEMPLATE.md` in the FRAIM registry templates.
+   - Locate the template: `get_fraim_file({ path: "templates/bootstrap/ARCHITECTURE-TEMPLATE.md" })`
    - Analyze your findings from Step 1.
    - Create a new file at `docs/architecture/architecture.md`.
    - Use your intelligence to synthesize the findings into the template:
@@ -21,7 +21,7 @@ To analyze the codebase and author a comprehensive `docs/architecture/architectu
      - **Data Flow**: Explain the lifecycle of a typical request or action.
 
 3. **Update FRAIM Configuration**
-   - Read `.fraim/config.json`.
+   - Read the project configuration file at `.fraim/config.json`.
    - Update it to include a reference to the architecture document:
      ```json
      {

package/registry/workflows/bootstrap/evaluate-code-quality.md

@@ -7,15 +7,15 @@ To perform a deep analysis of the codebase's quality, evaluating it against FRAI
 
 1. **Environment Check**
    - Ensure `npm install` and `npm run build` have been attempted.
-   - Verify that `.fraim/config.json` is present.
+   - Verify that `.fraim` directory (or equivalent config) is present.
 
 2. **Run Quality Analysis**
     - Find the `evaluate-code-quality.ts` script in the FRAIM registry.
-    - Execute it using `npx tsx <registry_path>/scripts/evaluate-code-quality.ts`.
+    - Execute it using `scripts/evaluate-code-quality.ts` (fetch via `get_fraim_file` first).
 
 3. **Author Report**
     - Read the terminal output from Step 2.
-    - Locate the `CODE-QUALITY-REPORT-TEMPLATE.md` in the registry templates.
+    - Locate the template: `get_fraim_file({ path: "templates/bootstrap/CODE-QUALITY-REPORT-TEMPLATE.md" })`
     - Create a new file at `docs/bootstrap/code-quality-report.md`.
     - Use your intelligence to synthesize the findings into the template:
         - Assign a fair grade (A-F) based on build success and diagnostic results.

package/registry/workflows/bootstrap/verify-test-coverage.md

@@ -15,11 +15,11 @@ To verify the depth and effectiveness of the test suite by comparing actual test
 
 3. **Analyze Coverage Gaps**
     - Find the `verify-test-coverage.ts` script in the FRAIM registry.
-    - Execute it using `npx tsx <registry_path>/scripts/verify-test-coverage.ts`.
+    - Execute it using `scripts/verify-test-coverage.ts` (fetch via `get_fraim_file` first).
 
 4. **Author Report**
     - Read the terminal output from Step 3.
-    - Locate the `TEST-COVERAGE-REPORT-TEMPLATE.md` in the registry templates.
+    - Locate the template: `get_fraim_file({ path: "templates/bootstrap/TEST-COVERAGE-REPORT-TEMPLATE.md" })`
     - Create a new file at `docs/bootstrap/test-coverage-report.md`.
     - Use your intelligence to synthesize the findings into the template:
         - Highlight mission-critical scenarios that lack automated test evidence.

package/registry/workflows/customer-development/insight-analysis.md

@@ -1,156 +1,156 @@
-# Insight Analysis Workflow
-
-## INTENT
-To help Product Managers extract, structure, and analyze customer insights from interview notes, enabling data-driven product decisions and systematic customer relationship management.
-
-## PRINCIPLES
-- **Comprehensive Extraction**: Capture all insights from raw notes
-- **Structured Analysis**: Organize insights into actionable categories
-- **Customer Scoring**: Evaluate customer fit and prioritization
-- **Follow-up Generation**: Create personalized follow-up communications
-
-## WORKFLOW TRIGGER
-**PM explicitly starts this workflow**:
-- "Starting Insight Analysis for [Customer Name]"
-- "I want to analyze the interview with [Customer Name]"
-- "Following the insight analysis workflow"
-
-## INPUT REQUIREMENTS
-**PM provides**:
-- The `[customer-name]-interview-prep.md` file that needs to be updated
-- Raw interview notes in any format (bullet points, paragraphs, voice-to-text, etc.)
-- Brief unstructured thoughts about the interview (optional but helpful)
-
-## AI AGENT PROCESS
-
-### Step 1: Insight Extraction & Template Update
-**AI Agent Analysis Process**:
-1. **Read Existing Prep File**
-   - Load the `[customer-name]-interview-prep.md` file
-   - Understand the customer context and research from preparation phase
-   - Review the pre-filled template structure
-
-2. **Parse Raw Notes**
-   - Extract customer quotes and key statements
-   - Identify pain points and challenges
-   - Capture success and failure criteria
-   - Note feature requests and preferences
-   - **Date Handling**: If user provides relative time references (e.g., "yesterday", "today", "last Friday"), run `new Date()` to determine the actual date and use that in the analysis file
-
-3. **Create Analysis File**
-   - Create new file: `[customer-name]-interview-analysis.md`
-   - Include comprehensive analysis with customer scoring and insights
-   - Reference the prep file for context but keep files separate
-   - Include follow-up actions and next steps
-
-### Step 2: Customer Scoring & Prioritization
-**AI Agent Scoring Process**:
-1. **Customer Fit Scoring (1-10)**
-   - Target customer segment alignment
-   - Pain point severity and frequency
-   - Budget and decision-making authority
-   - Influence and referral potential
-
-2. **Urgency Assessment**
-   - Active seeking of solutions
-   - Budget allocation and timeline
-   - Competitive pressure
-   - Implementation readiness
-
-3. **Willingness to Pay**
-   - Budget authority and constraints
-   - Current spending on similar solutions
-   - Value perception and ROI understanding
-
-### Step 3: Follow-up Generation
-**AI Agent Communication Process**:
-1. **Generate Follow-up Email**
-   - Use follow-up email templates as reference
-   - Create personalized email based on interview content
-   - Include key takeaways confirmation
-   - Add specific next steps and timeline
-   - Reference customer quotes and insights
-
-2. **Follow-up Questions**
-   - Clarify any gaps in understanding
-   - Deepen insights on key topics
-   - Validate assumptions and priorities
-   - Explore referral opportunities
-
-3. **Next Steps Planning**
-   - Demo scheduling if appropriate
-   - Additional stakeholder meetings
-   - Resource sharing and education
-   - Timeline and milestone setting
-
-### Step 4: File Creation & Finalization
-**AI Agent File Management**:
-1. **Create Analysis File**
-   - Create `[customer-name]-interview-analysis.md` with comprehensive analysis
-   - Include customer scoring, insights, and follow-up actions
-   - Reference the prep file for context but keep files separate
-
-2. **Preserve Prep File**
-   - Keep `[customer-name]-interview-prep.md` unchanged
-   - Maintains clean separation between preparation and analysis
-   - Both files can be referenced independently
-
-## OUTPUT TEMPLATE
-
-### Analysis File Template
-**Template**: `.ai-agents/templates/customer-development/insight-analysis-template.md`
-**File Location**: `docs/customer-development/[customer-name]-interview-analysis.md`
-
-**Process**:
-1. Use the insight analysis template
-2. Extract insights from raw interview notes
-3. Score customer based on fit, urgency, willingness to pay, and likelihood to buy
-4. Include direct customer quotes for authenticity
-5. Create next steps and follow-up questions
-6. Reference the original prep file for context
-7. **Generate personalized follow-up email** using follow-up email templates as reference `.ai-agents/templates/customer-development/follow-up-email-templates.md` ... add this to the end of the analysis file.
-
-## EXAMPLES
-
-### Good: Insight Analysis
-```
-Input: 
-- File: ronil-dhruva-interview-prep.md
-- Raw notes: "Ronil mentioned calendar conflicts, uses Outlook, frustrated with rescheduling, would pay $50/month, concerned about AI decisions. He was really engaged and seemed to understand the problem well."
-
-AI Agent Process:
-1. Reads existing prep file with LinkedIn research
-2. Extracts insights from raw notes
-3. Creates separate analysis file: ronil-dhruva-interview-analysis.md
-4. Preserves original prep file unchanged
-5. **Generates personalized follow-up email** using follow-up email templates
-6. Creates next steps and follow-up questions
-
-Output:
-- New analysis file: ronil-dhruva-interview-analysis.md
-- Original prep file: ronil-dhruva-interview-prep.md (unchanged)
-- Customer score: 8/10 (high fit, clear pain points, enterprise budget)
-- **Personalized follow-up email** using template structure with customer-specific content
-- Next questions: "What specific hierarchy rules should AI respect?"
-```
-
-### Bad: Surface-Level Analysis
-```
-Input: 
-- File: ronil-dhruva-interview-prep.md
-- Raw notes: "Ronil interview went well"
-
-AI Agent Output:
-- Generic analysis with no specific insights
-- No customer scoring or prioritization
-- No follow-up recommendations
-- No actionable next steps
-
-Result: Lost insights, no clear next steps, wasted prep work
-```
-
-## SUCCESS METRICS
-- **Insight Extraction**: 95% of key insights captured from raw notes
-- **Customer Scoring**: Consistent scoring across all customers
-- **Follow-up Quality**: 80% of follow-up emails result in positive responses
-- **Action Clarity**: Clear next steps for every customer
+# Insight Analysis Workflow
+
+## INTENT
+To help Product Managers extract, structure, and analyze customer insights from interview notes, enabling data-driven product decisions and systematic customer relationship management.
+
+## PRINCIPLES
+- **Comprehensive Extraction**: Capture all insights from raw notes
+- **Structured Analysis**: Organize insights into actionable categories
+- **Customer Scoring**: Evaluate customer fit and prioritization
+- **Follow-up Generation**: Create personalized follow-up communications
+
+## WORKFLOW TRIGGER
+**PM explicitly starts this workflow**:
+- "Starting Insight Analysis for [Customer Name]"
+- "I want to analyze the interview with [Customer Name]"
+- "Following the insight analysis workflow"
+
+## INPUT REQUIREMENTS
+**PM provides**:
+- The `[customer-name]-interview-prep.md` file that needs to be updated
+- Raw interview notes in any format (bullet points, paragraphs, voice-to-text, etc.)
+- Brief unstructured thoughts about the interview (optional but helpful)
+
+## AI AGENT PROCESS
+
+### Step 1: Insight Extraction & Template Update
+**AI Agent Analysis Process**:
+1. **Read Existing Prep File**
+   - Load the `[customer-name]-interview-prep.md` file
+   - Understand the customer context and research from preparation phase
+   - Review the pre-filled template structure
+
+2. **Parse Raw Notes**
+   - Extract customer quotes and key statements
+   - Identify pain points and challenges
+   - Capture success and failure criteria
+   - Note feature requests and preferences
+   - **Date Handling**: If user provides relative time references (e.g., "yesterday", "today", "last Friday"), run `new Date()` to determine the actual date and use that in the analysis file
+
+3. **Create Analysis File**
+   - Create new file: `[customer-name]-interview-analysis.md`
+   - Include comprehensive analysis with customer scoring and insights
+   - Reference the prep file for context but keep files separate
+   - Include follow-up actions and next steps
+
+### Step 2: Customer Scoring & Prioritization
+**AI Agent Scoring Process**:
+1. **Customer Fit Scoring (1-10)**
+   - Target customer segment alignment
+   - Pain point severity and frequency
+   - Budget and decision-making authority
+   - Influence and referral potential
+
+2. **Urgency Assessment**
+   - Active seeking of solutions
+   - Budget allocation and timeline
+   - Competitive pressure
+   - Implementation readiness
+
+3. **Willingness to Pay**
+   - Budget authority and constraints
+   - Current spending on similar solutions
+   - Value perception and ROI understanding
+
+### Step 3: Follow-up Generation
+**AI Agent Communication Process**:
+1. **Generate Follow-up Email**
+   - Use follow-up email templates as reference
+   - Create personalized email based on interview content
+   - Include key takeaways confirmation
+   - Add specific next steps and timeline
+   - Reference customer quotes and insights
+
+2. **Follow-up Questions**
+   - Clarify any gaps in understanding
+   - Deepen insights on key topics
+   - Validate assumptions and priorities
+   - Explore referral opportunities
+
+3. **Next Steps Planning**
+   - Demo scheduling if appropriate
+   - Additional stakeholder meetings
+   - Resource sharing and education
+   - Timeline and milestone setting
+
+### Step 4: File Creation & Finalization
+**AI Agent File Management**:
+1. **Create Analysis File**
+   - Create `[customer-name]-interview-analysis.md` with comprehensive analysis
+   - Include customer scoring, insights, and follow-up actions
+   - Reference the prep file for context but keep files separate
+
+2. **Preserve Prep File**
+   - Keep `[customer-name]-interview-prep.md` unchanged
+   - Maintains clean separation between preparation and analysis
+   - Both files can be referenced independently
+
+## OUTPUT TEMPLATE
+
+### Analysis File Template
+**Template**: Retrieve via `get_fraim_file({ path: "templates/customer-development/insight-analysis-template.md" })`
+**File Location**: `docs/customer-development/[customer-name]-interview-analysis.md`
+
+**Process**:
+1. Use the insight analysis template
+2. Extract insights from raw interview notes
+3. Score customer based on fit, urgency, willingness to pay, and likelihood to buy
+4. Include direct customer quotes for authenticity
+5. Create next steps and follow-up questions
+6. Reference the original prep file for context
+7. **Generate personalized follow-up email** using follow-up email templates as reference `get_fraim_file({ path: "templates/customer-development/follow-up-email-templates.md" })` ... add this to the end of the analysis file.
+
+## EXAMPLES
+
+### Good: Insight Analysis
+```
+Input: 
+- File: ronil-dhruva-interview-prep.md
+- Raw notes: "Ronil mentioned calendar conflicts, uses Outlook, frustrated with rescheduling, would pay $50/month, concerned about AI decisions. He was really engaged and seemed to understand the problem well."
+
+AI Agent Process:
+1. Reads existing prep file with LinkedIn research
+2. Extracts insights from raw notes
+3. Creates separate analysis file: ronil-dhruva-interview-analysis.md
+4. Preserves original prep file unchanged
+5. **Generates personalized follow-up email** using follow-up email templates
+6. Creates next steps and follow-up questions
+
+Output:
+- New analysis file: ronil-dhruva-interview-analysis.md
+- Original prep file: ronil-dhruva-interview-prep.md (unchanged)
+- Customer score: 8/10 (high fit, clear pain points, enterprise budget)
+- **Personalized follow-up email** using template structure with customer-specific content
+- Next questions: "What specific hierarchy rules should AI respect?"
+```
+
+### Bad: Surface-Level Analysis
+```
+Input: 
+- File: ronil-dhruva-interview-prep.md
+- Raw notes: "Ronil interview went well"
+
+AI Agent Output:
+- Generic analysis with no specific insights
+- No customer scoring or prioritization
+- No follow-up recommendations
+- No actionable next steps
+
+Result: Lost insights, no clear next steps, wasted prep work
+```
+
+## SUCCESS METRICS
+- **Insight Extraction**: 95% of key insights captured from raw notes
+- **Customer Scoring**: Consistent scoring across all customers
+- **Follow-up Quality**: 80% of follow-up emails result in positive responses
+- **Action Clarity**: Clear next steps for every customer