work-report-generatorlisted

# Work Report Generator Turn unstructured daily notes and commit messages into a formal `reports/YYYY-MM-DD/REPORT.md`. Strict no-inference: every task, project assignment, and per-project hour count comes from the user, asked explicitly. Report template, anti-patterns, and closing checklist in [RECIPES.md](RECIPES.md). ## 1. When to use Daily or backfilled work reports written in a formal tone, in any language. Triggered by phrases like "generar reporte", "reporte de trabajo", "work report", "daily report", "reporte del día", or the `/work-report` slash command. Skip this skill for: changelogs, release notes, retrospectives, CV/resume writing, stand-up summaries — those have different structures and audiences. ## 2. File layout All artifacts live under `reports/` at the repository root. Each day gets its own folder. ``` reports/ ├── projects.md persistent catalog of general projects (one bullet per project, with short description) └── YYYY-MM-DD/ ├── LOG.md per-day scratchpad: raw user input, commit dumps, tasks grouped by project, hours per project └── REPORT.md formal report, generated/regenerated from LOG.md ``` - **`projects.md`** is the single source of truth for project names across all reports. Reuse names verbatim so reports stay linkable. - **`LOG.md`** is the working scratchpad — append-only during a session. Paste raw input, record clarification answers, log per-project hours. It is the *input* to the formal report.