← ClaudeAtlas

work-summarylisted

Generate structured work summaries, progress reports, and task tickets. TRIGGER when: user says 'summarize what we did', 'work summary', 'progress report', 'create a ticket', 'open a task', 'סיכום עבודה', 'סיכום יומי', 'דוח התקדמות', 'תפתח טיקט', 'end of day summary', 'what did we accomplish', or at the end of a productive session when asked to wrap up.
hiyabh/claude-skills · ★ 0 · Data & Documents · score 66
Install: claude install-skill hiyabh/claude-skills
# Work Summary Generator ## Purpose Automatically generate structured work summaries, progress reports, and task tickets from the current session's activity. Instead of manually tracking what was done, Claude analyzes the session and produces organized output. This follows Anthropic's practice of automation skills that read daily activity and produce organized work summaries or open tickets for other developers autonomously. ## Summary Types ### 1. Session Summary (Quick) For end-of-session wrap-up: ```markdown # Work Summary - {Date} ## Done - Bullet list of completed items ## In Progress - Items started but not finished ## Blockers - Anything preventing progress ## Time Estimate Approximate effort spent: X hours ``` ### 2. Progress Report (Detailed) For stakeholder updates or team communication: ```markdown # Progress Report: {Project Name} **Period**: {Date range} **Author**: Generated by Claude ## Executive Summary 2-3 sentences on overall progress. ## Completed Tasks | Task | Status | Impact | |------|--------|--------| | ... | Done | ... | ## Upcoming Work Prioritized list of next tasks. ## Risks & Blockers Items that could delay progress. ## Metrics (if applicable) - Tests passing: X/Y - Files changed: N - New features: N ``` ### 3. Task Ticket For creating actionable tickets for other developers: ```markdown # {Ticket Title} ## Description What needs to be done and why. ## Acceptance Criteria - [ ] Specific measurable criteria - [ ] That define "do