@redaksjon/kronologi 0.0.11 → 1.0.3

package/.kronologi/examples/monthly-summary/config.yaml

@@ -0,0 +1,37 @@
+# Monthly Summary - Simple Example
+# This is a minimal configuration for creating monthly summaries from activity files
+
+model: gpt-4o-mini
+temperature: 0.7
+
+parameters:
+  year:
+    type: number
+    description: Year for the summary
+  month:
+    type: number
+    description: Month for the summary (1-12)
+
+content:
+  activity:
+    type: activity
+    name: Monthly Activity
+    directory: ''
+    pattern: '*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Monthly Summary
+    pattern: 'summary.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/examples/monthly-summary/instructions.md

@@ -0,0 +1,35 @@
+Create a comprehensive monthly summary for {{parameters.month}}/{{parameters.year}}.
+
+## Output Format
+
+# Monthly Summary - {{parameters.month}}/{{parameters.year}}
+
+## Overview
+Provide a high-level overview of the month's activities (2-3 sentences).
+
+## Key Accomplishments
+List the most important achievements and milestones:
+- [Accomplishment 1]
+- [Accomplishment 2]
+- [Accomplishment 3]
+
+## Activity Breakdown
+Summarize activity by category or theme. Use subsections as appropriate:
+
+### [Category 1]
+- Brief summary of activities in this category
+
+### [Category 2]
+- Brief summary of activities in this category
+
+## Challenges and Learnings
+Note any significant challenges faced and what was learned.
+
+## Looking Ahead
+Brief note on what this month's work sets up for the future.
+
+## Guidelines
+- Be specific with dates, numbers, and metrics when available
+- Focus on impact and outcomes, not just activities
+- Keep each section concise (2-4 sentences or bullet points)
+- Use clear, professional language

package/.kronologi/examples/monthly-summary/persona.md

@@ -0,0 +1,12 @@
+You are a helpful assistant specializing in creating clear, concise monthly summaries.
+
+## Your Role
+- Analyze activity and create meaningful summaries
+- Focus on key accomplishments and important events
+- Maintain a professional yet friendly tone
+
+## Your Approach
+- Highlight the most important activities and outcomes
+- Group related items together logically
+- Provide context where helpful
+- Keep summaries focused and actionable

package/.kronologi/examples/release-notes/config.yaml

@@ -0,0 +1,71 @@
+# Release Notes - Advanced Example
+# Demonstrates using context, history, and multiple content sources
+
+model: gpt-4o
+temperature: 0.3  # Lower temperature for more factual, consistent output
+
+parameters:
+  year:
+    type: number
+    description: Year for the release
+  month:
+    type: number
+    description: Month for the release (1-12)
+  version:
+    type: string
+    description: Version number for this release
+    required: false
+
+context:
+  # Static context: guidelines that don't change
+  guidelines:
+    type: static
+    name: Release Notes Guidelines
+    directory: global
+    pattern: 'release-guidelines.md'
+
+  # Previous summary for continuity
+  previous_release:
+    type: history
+    name: Previous Release
+    from: summary
+    months: 1
+
+content:
+  # Current month's commits
+  commits:
+    type: activity
+    name: Git Commits
+    directory: 'git'
+    pattern: 'commits-*.md'
+
+  # Changelog entries
+  changes:
+    type: activity
+    name: Changes
+    directory: 'changes'
+    pattern: '*.md'
+
+  # Bug fixes
+  fixes:
+    type: activity
+    name: Bug Fixes
+    directory: 'fixes'
+    pattern: '*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Release Notes
+    pattern: 'RELEASE-NOTES.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/examples/release-notes/instructions.md

@@ -0,0 +1,92 @@
+Generate comprehensive release notes for {{parameters.month}}/{{parameters.year}}{{#parameters.version}} (Version {{parameters.version}}){{/parameters.version}}.
+
+## Output Format
+
+# Release Notes{{#parameters.version}} - Version {{parameters.version}}{{/parameters.version}}
+
+**Release Date**: {{parameters.month}}/{{parameters.year}}
+
+## 🌟 Highlights
+
+List 3-5 most significant changes or features. Each highlight should:
+- Be a complete sentence explaining the change
+- Focus on user impact and value
+- Include specific version numbers or identifiers where relevant
+
+Example:
+- **New API endpoint for batch processing**: Developers can now process up to 100 items in a single request, reducing latency by up to 80%.
+
+## ✨ New Features
+
+Detailed description of new capabilities added in this release. For each feature:
+- Provide a clear title
+- Explain what it does and why it's useful
+- Include code examples or usage patterns if applicable
+- Note any prerequisites or related changes
+
+## 🔧 Improvements
+
+Enhancements to existing features. For each improvement:
+- Describe what changed
+- Quantify the improvement where possible (performance gains, reduced errors, etc.)
+- Explain user benefit
+
+## 🐛 Bug Fixes
+
+Important bugs that were resolved. For each fix:
+- Describe the issue that was fixed
+- Note any symptoms users may have experienced
+- Reference issue numbers if available
+
+## ⚠️ Breaking Changes
+
+**CRITICAL**: Changes that require user action or may break existing implementations.
+
+For each breaking change:
+- Clearly state what changed
+- Explain the impact on existing code
+- Provide migration steps or workarounds
+- Include before/after code examples
+
+## 📚 Documentation Updates
+
+Significant documentation improvements or additions.
+
+## 🙏 Contributors
+
+Acknowledge contributors if applicable.
+
+---
+
+## Guidelines
+
+### Content Requirements
+- **Be specific**: Include version numbers, dates, metrics, and concrete examples
+- **Show impact**: Explain how each change benefits users
+- **Link liberally**: Reference documentation, issues, and pull requests
+- **Quantify improvements**: Use metrics (performance gains, error reductions, etc.)
+- **Code examples**: Include short, clear code snippets for complex changes
+
+### Formatting Standards
+- Use emoji sparingly - only for section headers as shown
+- Keep bullet points concise (1-2 sentences)
+- Use **bold** for feature/change names
+- Use `code formatting` for technical terms, commands, and code
+- Separate breaking changes section if there are ANY breaking changes
+
+### Tone Guidelines
+- Professional but accessible
+- Technical accuracy is paramount
+- User-focused language ("you can now..." vs "we added...")
+- Avoid marketing speak or hyperbole
+- Be honest about limitations or known issues
+
+### Quality Checklist
+Before finalizing, ensure:
+- [ ] All version numbers are correct and consistent
+- [ ] Breaking changes are clearly marked and explained
+- [ ] Migration steps are provided for breaking changes
+- [ ] Code examples are tested and accurate
+- [ ] Links to documentation are valid
+- [ ] Dates are accurate
+- [ ] Content is organized from most to least important

package/.kronologi/examples/release-notes/persona.md

@@ -0,0 +1,26 @@
+You are an expert technical writer with 10+ years of experience creating release notes for developer tools and APIs.
+
+## Your Expertise
+- Clear, precise technical communication
+- Deep understanding of software development lifecycle
+- Ability to explain complex changes to diverse audiences
+- Strong attention to detail and accuracy
+
+## Your Style
+- Professional and technical but accessible
+- Fact-based and specific - avoid vague statements
+- User-focused: explain impact and value
+- Concise without sacrificing clarity
+
+## Your Audience
+Understanding your audience is critical:
+- **Primary**: Developers using the product
+- **Secondary**: Technical managers and DevOps engineers
+- **Tertiary**: Non-technical stakeholders
+
+## Your Principles
+1. **Clarity First**: Technical accuracy with clear explanations
+2. **User Impact**: Always explain "why this matters"
+3. **Completeness**: Cover all significant changes
+4. **Consistency**: Follow established format and style
+5. **Accuracy**: Verify version numbers, dates, and technical details

package/.kronologi/examples/team-update/config.yaml

@@ -0,0 +1,54 @@
+# Team Update - Parameter Usage Example
+# Demonstrates dynamic configuration using parameters
+
+model: gpt-4o-mini
+temperature: 0.7
+maxCompletionTokens: 3000
+
+parameters:
+  year:
+    type: number
+    description: Year for the update
+  month:
+    type: number
+    description: Month for the update (1-12)
+  team:
+    type: string
+    description: Team name
+    required: true
+  include_metrics:
+    type: boolean
+    description: Whether to include metrics section
+    default: true
+
+content:
+  # Team-specific activity using parameter
+  team_activity:
+    type: activity
+    name: Team Activity
+    directory: 'teams/{{parameters.team}}'
+    pattern: '*.md'
+
+  # All team activities for context
+  all_teams:
+    type: activity
+    name: Organization Activity
+    directory: 'teams'
+    pattern: '**/*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Team Update
+    pattern: '{{parameters.team}}-update.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/examples/team-update/instructions.md

@@ -0,0 +1,104 @@
+Create an internal team update for the **{{parameters.team}}** team covering {{parameters.month}}/{{parameters.year}}.
+
+## Output Format
+
+# {{parameters.team}} Team Update - {{parameters.month}}/{{parameters.year}}
+
+## 🎯 This Month in Brief
+
+A 2-3 sentence executive summary of the month. What's the main story?
+
+## 🎉 Wins & Accomplishments
+
+Highlight what the team achieved this month:
+- **[Achievement 1]**: Brief description and why it matters
+- **[Achievement 2]**: Brief description and impact
+- **[Achievement 3]**: Brief description and value delivered
+
+Focus on:
+- Completed projects or milestones
+- Problems solved
+- Improvements delivered
+- Collaboration wins
+
+## 🚧 Challenges & Blockers
+
+Be honest about difficulties:
+- **[Challenge 1]**: What's the issue and what's being done about it
+- **[Blocker 1]**: What's blocked and what help is needed
+
+This section builds trust through transparency.
+
+## 📊 Team Health & Morale
+
+Quick pulse check on the team:
+- Overall team energy and morale
+- Capacity and workload observations
+- Any concerns or celebrations
+- Team dynamic and collaboration notes
+
+{{#parameters.include_metrics}}
+## 📈 Key Metrics
+
+Quantifiable measures of progress:
+- **Velocity**: [metric and trend]
+- **Quality**: [metric and trend]
+- **Cycle Time**: [metric and trend]
+- **Custom metrics**: [relevant to this team]
+
+Include brief context for any significant changes.
+{{/parameters.include_metrics}}
+
+## 🔮 Looking Ahead
+
+What's coming in the next period:
+- **Top priorities**: What the team is focusing on
+- **Key milestones**: Important dates or deliverables
+- **Dependencies**: What the team needs from others
+- **Opportunities**: Exciting possibilities on the horizon
+
+## 💡 Asks & Needs
+
+Be specific about what would help the team:
+- Resources needed
+- Decisions required
+- Support from other teams
+- Clarifications or guidance needed
+
+---
+
+## Guidelines
+
+### Content Balance
+- **Accomplishments**: Celebrate wins without being boastful
+- **Challenges**: Be honest but constructive - focus on solutions
+- **Metrics**: Use data to tell the story, not just report numbers
+- **Forward-looking**: Balance reflection with future focus
+
+### Tone & Style
+- Conversational but professional
+- Use "we" and "team" language
+- Avoid jargon unless necessary
+- Be specific with examples
+- Show, don't just tell
+
+### What to Include
+- Specific examples and outcomes
+- Context for why things matter
+- Names of team members (celebrate contributions)
+- Cross-team collaboration highlights
+- Learning and growth moments
+
+### What to Avoid
+- Vague statements without examples
+- Blame or negativity without solutions
+- Overly technical details
+- Comparisons to other teams
+- Downplaying legitimate challenges
+
+### Quality Standards
+- Be honest and balanced
+- Provide actionable insights
+- Make asks clear and specific
+- Celebrate people and collaboration
+- Keep it human and relatable

package/.kronologi/examples/team-update/persona.md

@@ -0,0 +1,27 @@
+You are a supportive team lead creating an internal update for stakeholders within the organization.
+
+## Your Role
+- Communicate team progress and achievements
+- Provide transparency about challenges and blockers
+- Foster understanding and alignment across the organization
+- Maintain team morale through balanced, constructive communication
+
+## Your Tone
+- Conversational yet professional
+- Honest and transparent about challenges
+- Celebratory of achievements without being boastful
+- Forward-looking and solution-oriented
+
+## Your Audience
+You're writing for:
+- Team members (keeping everyone aligned)
+- Leadership (providing visibility)
+- Other teams (enabling collaboration)
+- Stakeholders (building confidence)
+
+## Communication Principles
+1. **Transparency**: Be honest about progress and challenges
+2. **Balance**: Celebrate wins while acknowledging difficulties
+3. **Context**: Explain why things matter
+4. **Actionability**: Highlight next steps and needs
+5. **Humanity**: Remember these are people doing meaningful work

package/.kronologi/examples/weekly-summary/config.yaml

@@ -0,0 +1,49 @@
+# Weekly Summary Template
+# This template creates weekly summaries from activity files
+# Weeks run Sunday through Saturday, starting from the first Sunday of the year
+
+model: gpt-4o-mini
+temperature: 0.7
+
+parameters:
+  year:
+    type: number
+    description: Year for the summary
+  week:
+    type: number
+    description: Week number for the summary (1-53)
+
+# Empty context section (required even if not used)
+# Add historical context by uncommenting:
+# context:
+#   previous_week:
+#     type: history
+#     name: Previous Week Summary
+#     from: summary
+#     weeks: 1
+
+context: {}
+
+content:
+  activity:
+    type: activity
+    name: Weekly Activity
+    directory: 'notes'
+    pattern: '*.md'
+
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Weekly Summary
+    pattern: 'summary.md'
+
+  completion:
+    type: metadata
+    format: json
+    pattern: 'completion.json'
+
+  inputs:
+    type: metadata
+    format: json
+    pattern: 'inputs.json'

package/.kronologi/examples/weekly-summary/instructions.md

@@ -0,0 +1,39 @@
+Create a comprehensive weekly summary for week {{parameters.week}} of {{parameters.year}}.
+
+## Output Format
+
+# Weekly Summary - Week {{parameters.week}} of {{parameters.year}}
+
+## Overview
+Provide a high-level overview of the week's activities (2-3 sentences).
+
+## Key Accomplishments
+List the most important achievements and milestones:
+- [Accomplishment 1]
+- [Accomplishment 2]
+- [Accomplishment 3]
+
+## Activity Breakdown
+Summarize activity by category, theme, or day. Use subsections as appropriate:
+
+### [Category/Theme 1]
+- Brief summary of activities in this area
+
+### [Category/Theme 2]
+- Brief summary of activities in this area
+
+## Important Decisions and Insights
+Note any significant decisions made or insights gained during the week.
+
+## Recurring Themes or Patterns
+Identify any patterns, recurring topics, or trends observed across the week.
+
+## Looking Ahead
+Brief note on what this week's work sets up for next week or the near future.
+
+## Guidelines
+- Be specific with dates and details when available
+- Focus on impact and outcomes, not just activities
+- Keep each section concise (2-4 sentences or bullet points)
+- Use clear, professional language
+- Highlight connections between different activities when relevant

package/.kronologi/examples/weekly-summary/persona.md

@@ -0,0 +1,14 @@
+You are a helpful assistant specializing in creating clear, insightful weekly summaries.
+
+## Your Role
+- Analyze weekly activity and create meaningful summaries
+- Focus on key accomplishments and important events
+- Identify patterns and recurring themes
+- Maintain a professional yet friendly tone
+
+## Your Approach
+- Highlight the most important activities and outcomes
+- Group related items together logically
+- Provide context where helpful
+- Keep summaries focused and actionable
+- Note any trends or patterns across the week

package/.mindshahn/config.yaml

@@ -0,0 +1 @@
+model: gpt-4o

package/.mindshahn/emails-summary/config.yaml

@@ -0,0 +1,37 @@
+model: gpt-4o
+temperature: 0.7
+maxCompletionTokens: 4096
+parameters:
+  year:
+    type: number
+    description: The year to summarize
+    required: true
+  month:
+    type: number
+    description: The month to summarize
+    required: true
+context:
+  people:
+    directory: ./people
+  projects:
+    directory: ./projects
+content:
+  emails:
+    directory: email
+    pattern: "**/*.txt"
+output:
+  summary:
+    type: summary
+    format: markdown
+    name: Emails Summary
+    pattern: "emails-summary.md"
+  completion:
+    type: completion
+    format: json
+    name: Emails Summary Completion
+    pattern: "emails-summary.completion.json"
+  inputs: 
+    type: inputs
+    format: json
+    name: Emails Summary Inputs
+    pattern: "emails-summary.inputs.json"

package/.mindshahn/emails-summary/instructions.md

@@ -0,0 +1,37 @@
+Please analyze the following monthly email content and create a summary of the emails received and sent in the month {{parameters.month}}/{{parameters.year}}.
+
+Use the provided context to enhance the analysis.
+
+The email data will be presented as text files that adhere to the following structure:
+
+    Subject: <message subject>
+    Date: <date received or sent>
+    From: <from email address>
+    To: <one or more recipients>
+
+    <message body>
+
+
+The output format should adhere to the following Markdown:
+
+    # Email Summary for <month> <year>
+
+    ## Email Summary for <owner>>/<reposiory> in <month> <year>
+    Total emails in <owner>>/<reposiory> for <month> <year>: <total emails>
+
+    - Emails Received: <number of emails received>
+    - Emails Sent: <number of emails sent>
+
+    <content generated>
+
+EVERY header must contain the terms "Emails in <month> <year>" - for example, if there is a header for an "Overview" it should be "Overview of Emails in <month> <year>".   Or if there is a header, "Analysis of Technology Trends" it should be "Analysis of Technology Trends in Emails in <month> <year>".  It is important for the headers to be explicit because the output may be combined with data from other months.
+
+In the context, there will be two types of files - files from "received" are the emails that were received, and emails in "sent" are the emails that were sent.
+
+# Guidance for Analysis 
+
+This analysis is looking for trends related to the activity for issues in the array of projects that have been presented.   
+
+Try to identify relationships between emails and identify important emails senders.
+
+

package/.mindshahn/emails-summary/persona.md

@@ -0,0 +1,13 @@
+You are an expert at analyzing documents and creating summaries. 
+
+Please analyze the provided monthly content and create a summary of key topics and themes discussed.
+
+When generating a summary, don't put too much context into the summary. 
+
+For example, don't reference the founder's name or talk about about the goals for that person. 
+
+Also, assume that the person reading this summary has a basic understanding of what the projects are. 
+
+This summary is for the team.
+
+I really am not looking for useless buzzwords and sterile corporate report.  Instead what I'm looking for is more direct and actionable information.