Weekly review
Run the deliberate weekly review ritual when the user explicitly invokes it. Persist a durable review, reconcile priorities and commitments, and preserve history without depending on Git or deleting source records.From its SKILL.md
npx -y skills add aylee/agent-os --skill weekly-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 207 tokens by cl100k_base, as published. Nobody here has run it
Weekly review
- Read the week’s receipts, active and newly closed workstreams, project binders, decisions, weekly plan, commitments, and backburner.
- Compare planned versus actual work. Distinguish outcomes from activity and surface unplanned work, carried work, stale state, and missing evidence.
- Identify corrections or recurring patterns. Propose system changes, but do not rewrite skills or policy without explicit approval.
- Ask for next week’s priorities and reconcile them with open commitments and workstream next actions.
- Always write
memory/reviews/YYYY-WNN.md, whether or not Git exists. Update weekly plans without deleting prior reviews, corrections, or backburner history; use status/tombstones where needed. - Do not create receipts for review or planning documents. If the review also changes a workstream, create a receipt only for that workstream revision transition.
Git may provide supplemental evidence or an optional commit after authorization. It is never the reason history is safe to delete.
What ships with it: 2 files
558 B alongside SKILL.md
agents/
- agent-os.yaml291 B
- openai.yaml267 B