🎯 Activity Prompt: Please Transfer Context

I came across this prompt on a forum somewhere. It said that Claude Code uses it to transfer context between sessions. It has been working wonders for me so far, especially when combined with the last chat summary. May it be as useful to you as it is to me ✌️.

ultra-wide-turbo-workspace/prompt-engineer/prompts/activities/plx-transfer-context.md at main · ultrawideturbodev/ultra-wide-turbo-workspace

A virtual organization where you are the CEO and the main folders represent different roles working for you. Each role has its own set of prompts, documents, and main activities. - ultrawideturbode…

GitHubultrawideturbodev

<analysis>
Let me analyze the conversation chronologically:

1. Initial Request:
   - The user requested assistance with research regarding an audit for a company that developed 3 applications: a frontend web app, an admin panel, and a backend.
   - They provided an Excel file (sm-audit-roadmap-2024.xlsx) and asked to transform it into usable markdown information.
   - They specified the audit goals: Quality check, Verification of delivered work, Architecture assessment, and Hours verification.

2. My Approach:
   - I searched for and converted the Excel file to markdown for analysis.
   - I created multiple structured markdown documents in the auditor/markdown directory.
   - I developed a comprehensive audit methodology framework with specific tools and templates.

3. Key Files Created:
   - I created several key files including roadmap-analysis.md, audit-plan.md, initial-findings.md, and many other methodology documents.
   - I organized these into a coherent framework for conducting the audit.
   - Most recently, I created specialized documents for specific aspects of the audit: technology-specific code reviews, documentation quality assessment, time tracking visualization, and git commit analysis.

4. Technical Concepts:
   - Software audit methodology for three applications
   - Time tracking analysis and visualization
   - Code quality assessment
   - Architecture evaluation
   - Git commit history analysis for time verification
   - Documentation quality verification

5. Current Work:
   - My most recent work was creating several specialized audit methodology documents:
     - technology-specific-code-review.md
     - time-tracking-visualization-templates.md
     - documentation-quality-assessment.md
     - git-commit-analysis-guide.md
   - I also updated master-audit-strategy.md to reference these new documents
   - I created README.md as an index for all the audit methodology documents

6. Technical Details:
   - The audit focuses on four main areas: Quality Assessment (Kwaliteitscheck), Deliverables Verification (Gedaan wat ze zouden doen), Architecture Evaluation (Architectuur), and Time Registration Validation (Uren klopt).
   - The project involves approximately 1,461.25 hours of work distributed across different components.
   - The audit methodology includes templates for visualizing time tracking data, guidelines for assessing code quality and architecture, and approaches for validating reported hours.
</analysis>

<summary>
1. Primary Request and Intent:
   The user requested assistance with research regarding an audit for a company that developed three applications (frontend web app, admin panel, and backend). They provided an Excel file (sm-audit-roadmap-2024.xlsx) and asked to transform it into usable markdown information for the audit. The audit was to focus on four primary aspects: quality assessment ("Kwaliteitscheck"), verification of delivered work ("Gedaan wat ze zouden doen"), architecture evaluation ("Architectuur"), and verification of reported hours ("Uren klopt").

2. Key Technical Concepts:
    - Software Audit Methodology
    - Time Tracking Analysis and Visualization
    - Code Quality Assessment Framework
    - Architecture Evaluation Criteria
    - Git Commit History Analysis for time verification
    - Documentation Quality Assessment
    - Technology-Specific Code Review (JavaScript/TypeScript, React, Node.js)
    - Requirements Traceability and Verification
    - Risk Assessment Framework for software audits
    - Technical Debt Identification

3. Files and Code Sections:
    - auditor/markdown/roadmap-analysis.md
        - Initial analysis of the Excel file data, breaking down the project hours and components
        - Summary of core project details, time registration, and breakdown by phase
        
    - auditor/markdown/audit-plan.md
        - High-level methodology for conducting the software audit
        - Outlines the four primary audit objectives and the approach for each
        
    - auditor/markdown/initial-findings.md
        - Preliminary observations from analyzing the roadmap
        - Highlights concerns like low testing allocation (3.4% of total hours)
        
    - auditor/markdown/technology-specific-code-review.md
        - Framework for evaluating codebase based on specific technologies
        - Contains detailed checklists for JavaScript/TypeScript, React, Node.js patterns
        - Example section: 
          ```
          ### React-Specific Patterns
          - Component composition and reusability
          - Hooks implementation (useState, useEffect, useMemo, useCallback)
          - Context API usage
          - React component lifecycle management
          - Memoization practices
          - React performance optimizations
          - PropTypes or TypeScript interface usage
          - Error boundaries implementation
          ```
        
    - auditor/markdown/time-tracking-visualization-templates.md
        - Templates for visualizing and analyzing time tracking data
        - Includes component distribution charts, timeline visualizations, and productivity metrics
        
    - auditor/markdown/documentation-quality-assessment.md
        - Methodology for evaluating documentation completeness and quality
        - Includes evaluation criteria and scoring system for different types of documentation
        
    - auditor/markdown/git-commit-analysis-guide.md
        - Framework for using git history to validate time tracking records
        - Provides git commands and visualization templates for commit analysis
        
    - auditor/markdown/master-audit-strategy.md
        - Primary reference document linking all audit components
        - Updated to include references to newly created specialized documents
        
    - auditor/markdown/README.md
        - Created as an index for all audit methodology documents
        - Provides overview of the audit focus areas and document structure

4. Problem Solving:
   The main challenge addressed was developing a comprehensive framework for conducting a software audit with limited initial information. I approached this by:
   - Creating structured methodology documents for each aspect of the audit
   - Developing specialized assessment frameworks for different areas (code, architecture, documentation, time tracking)
   - Creating visualization templates for time tracking analysis
   - Providing specific git commands and analysis approaches for validating reported hours
   - Organizing all documents into a coherent audit framework with a central reference document

5. Pending Tasks:
    - The actual execution of the audit (obtaining source code, time tracking records, and documentation)
    - Conducting interviews with stakeholders
    - Analyzing the codebase against the established criteria
    - Validating time tracking records against git commit history
    - Preparing the final audit report

6. Current Work:
   Immediately before the summary request, I had completed creating several specialized audit methodology documents and an index README.md file. I had just finished updating the master-audit-strategy.md file to reference all the newly created documents. The most recent documents created were:
   
   - technology-specific-code-review.md: A detailed checklist for evaluating code based on specific technologies (React, Node.js, etc.)
   - time-tracking-visualization-templates.md: Templates for visualizing and analyzing time tracking data
   - documentation-quality-assessment.md: Framework for evaluating documentation quality
   - git-commit-analysis-guide.md: Methodology for using git history to validate time tracking

   These documents form essential components of the comprehensive audit methodology framework.

7. Optional Next Step:
   Based on the established audit framework, the next logical step would be to develop a standardized report template that incorporates findings from all the different assessment areas into a cohesive final deliverable. This would include sections for code quality findings, architecture assessment, deliverables verification, and time tracking validation, all aligned with the four primary audit focuses requested by the client.

   However, I should confirm with the user if they want to proceed with developing this report template or if they prefer to begin implementing the audit methodology by gathering the required source code, documentation, and time tracking data first.
</summary>

ultra-wide-turbo-workspace/prompt-engineer/prompts/activities/plx-transfer-context.md at main · ultrawideturbodev/ultra-wide-turbo-workspace

A virtual organization where you are the CEO and the main folders represent different roles working for you. Each role has its own set of prompts, documents, and main activities. - ultrawideturbode…

GitHubultrawideturbodev