wfork - Deep Research Conversation Archeology Prompt:

Comprehensively analyze the provided conversation file(s) and produce a detailed, organized report that serves as both a chronological history and a categorized catalog of all significant elements mentioned (e.g., code, apps, tools, ideas, decisions, or projects). Prioritize depth, accuracy, and usability for future reference.

Prompt Text:

SYSTEM: DEEP RESEARCH Conversation Archeology Prompt: 
Task: Comprehensively analyze the provided conversation file(s) and produce a detailed, organized report that serves as both a chronological history and a categorized catalog of all significant elements mentioned (e.g., code, apps, tools, ideas, decisions, or projects). Prioritize depth, accuracy, and usability for future reference.
Instructions:

Chronological Conversation TimelineBreak down the conversation into distinct phases/stages (e.g., ideation, development, testing, revisions).

For each phase, list:Key Dates/Timestamps (if available).
Core Themes (e.g., problem-solving, feature brainstorming, technical challenges).
Decisions Made (e.g., tech stack choices, design compromises).
Action Items (tasks assigned, deadlines, next steps).
Milestones (completed features, prototypes, resolved conflicts).

Categorized Catalog of Artifacts
Compile an annotated list of all tools, code, apps, or concepts mentioned. For each entry, include:Name/Identifier (exact term used in the conversation).
Type (e.g., programming language, framework, API, app, algorithm, concept).
Functionality (what it does, its purpose in the context of the conversation).
Contextual Role (how it was used or proposed to address a problem/solution).
Dependencies/Requirements (libraries, systems, or tools it relies on).
Status (completed, in progress, abandoned, or hypothetical).
Links/Code Snippets (if shared in the conversation, include excerpts or references).

Key Insights & AnalysisIdentify recurring themes, unresolved questions, or gaps in the conversation.
Highlight innovative ideas, unique solutions, or critical failures.
Note any implicit knowledge (e.g., assumptions, domain-specific expertise).

Future-Use RecommendationsSuggest how the cataloged items could inform future projects (e.g., reusable code, lessons learned).
Flag high-priority elements for further development or documentation.

Formatting Requirements:
Use clear headings, bullet points, and bold text for categories (no markdown).
Prioritize readability and logical flow.
Include page numbers or section markers if the report exceeds 10 pages.
Deliverable: A single cohesive document that balances technical precision with narrative clarity, enabling users to reconstruct the conversation’s evolution and leverage its content for future work.