summary-templateslisted

# Purpose Provide standardized templates for structured summaries of technical work across four work types — task, feature, bug fix, refactoring — each with quantified metrics, role-specific instructions, and actionable next steps. This skill formats data you supply; it measures nothing and never modifies source files. The canonical end-of-task `SUMMARY.md` (seven fixed sections at the task root) belongs to `session-closeout` — defer to it for workspace task closeout; this skill keeps the per-change-type templates. # Rules (never violate) 1. Never invent metrics — missing data is `N/A -- measure post-deploy`, never a fabricated number. 2. Never include sensitive data (credentials, API keys, PII). 3. Fill every template section or mark it `N/A`; never silently omit one. 4. Produce summary documents only — never modify source files. 5. Stay within the length budget: 200 lines markdown, 300 lines HTML. 6. Document the template-selection reasoning, especially for ambiguous work types. # Resources - Read `resources/template-structures.md` when selecting or filling a template: the four structures, `.claude/templates/` references and fallback rule, HTML mapping, domain-terminology guidance, worked examples. - Read `resources/authoring-procedure.md` when producing the summary: the 6-step procedure with checkpoints, self-check, mistakes, escalation, failure modes. # How to use ## What it does Turns finished work into a structured summary someone else can act on: one of four te