weekly-work-summarylisted

# Weekly Work Summary ## Positioning Use this skill as a workspace-agnostic local-evidence reporting protocol, not as a prompt macro. The value is to make weekly summaries consistent when the user gives a short or vague request. Always reconstruct the summary from available workspace evidence instead of relying on memory, conversation history, or a literal restatement of the user's wording. ## Scope Apply this skill to whichever workspace, repository, or folder is active in the current task. If the target is ambiguous and cannot be inferred from context, ask for the target folder before collecting evidence. Do not assume any project-specific structure, language, file naming scheme, or output directory. Treat `.taskflow` as one possible signal, not a required dependency. Use China Shanghai time (`Asia/Shanghai`) as the fixed default time basis for "this week", "last week", "today", workdays, and date windows, regardless of the user's device timezone, unless the user explicitly requests a different timezone. ## Core Contract 1. Produce a concise human-readable status summary from local workspace activity. 2. Make the evidence path stable across sessions, folders, and projects. 3. Filter noisy filesystem churn before drawing conclusions. 4. Separate facts from inference when the evidence is indirect. 5. Do not edit project files for a summary request. 6. For ordinary weekly-summary requests, final output should be only the weekly summary itself; do not append project de