weekly-progress

Generates weekly progress log entries and updates project plan status from git history and spec files.

Updated Jul 1, 2025
One-click install
npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill weekly-progress-mosakuzii0216
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-progress
Source: https://github.com/mosakuzii0216/mosaku-v1/tree/main/.claude/skills/weekly-progress
Command: npx skills add https://github.com/mosakuzii0216/mosaku-v1 --skill weekly-progress-mosakuzii0216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping a weekly progress log and a project plan document in sync is tedious manual work: you must review git history, check spec completion states, summarize what actually happened, and update status columns by hand. This Skill automates that documentation workflow while keeping you in control of every commit. ## Core Features & Use Cases - Weekly log generation: Collects git commits since the last entry, aggregates completed specs from spec.json files, and writes a new dated entry at the top of docs/progress.md following the file's defined format. - Plan status synchronization: Cross-references spec.json phases against docs/project-plan-2026.md and flips status markers from pending to done, updating the last-modified date. - Human-in-the-loop commits: Never commits on its own; it shows you the rendered entry and diff summary first, then proposes commit messages only after your approval. - Use Case: On Friday evening, run the skill to turn a week of scattered commits and completed spec tasks into a clean progress entry and an up-to-date project plan in minutes. ## Quick Start Ask the assistant to run the weekly-progress skill to add this week's entry to docs/progress.md and refresh the status column in docs/project-plan-2026.md.

Frequently Asked Questions about weekly-progress

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a weekly progress log from git history?

Run the weekly-progress skill, which reads git log since the last entry, summarizes completed specs and major commits, and prepends a formatted dated entry to docs/progress.md. It abstracts commits into higher-level accomplishments rather than copying messages verbatim.

How to keep a project plan status table in sync with spec files?

The skill reads each spec.json phase field with jq, treats completed or implementation-validated phases as done, and flips the corresponding status markers in docs/project-plan-2026.md from pending to complete. It also refreshes the last-updated date at the top of the plan.

Does the weekly-progress skill commit changes automatically?

No, it never commits on its own. It first shows you the rendered log entry and a diff summary of plan changes, then proposes commit messages only after you explicitly approve and ask it to commit.

What happens if there are no new commits since the last entry?

The skill detects an empty git log and asks whether you want to add a no-progress entry anyway. Similarly, if docs/progress.md does not exist, it asks before creating a first entry, and it skips plan updates if the status column is missing.

What are the limitations of automated progress summarization?

The skill only records work traceable in git history, spec.json files, or the current conversation, and it will not fabricate accomplishments. It also refuses to change the plan itself, create new specs, modify code, or update steering files, as those belong to other workflows.