weekly-review

Reviews project harness health, fixes unambiguous issues, and proposes decisions via parallel subagents.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/gabesan21/project-of-projects --skill weekly-review-gabesan21
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/gabesan21/project-of-projects/tree/main/.agents/skills/weekly-review
Command: npx skills add https://github.com/gabesan21/project-of-projects --skill weekly-review-gabesan21

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project harnesses (AGENTS.md, roadmaps, specs, memory, kanban metadata) silently rot over time: dead links, oversized files, stale specs, orphaned worktrees, and stalled epochs accumulate without anyone noticing. This Skill performs a periodic, structured sweep of the current scope, automatically fixing what is unambiguous and surfacing everything else as proposals for human decision. ## Core Features & Use Cases - Script-driven measurement: Runs pop_status.py and pop_validate.py first to gather kanban overview, blocked tasks, pending gates, and limit violations before any manual inspection. - Parallel subagent waves: Delegates collection and correction to waves of 3-5 parallel subagents, one per front (base files, orphaned worktrees, outdated specs, DOX audit, note health, memory, stalled epochs, dated gate debt, swollen modifications, orphaned yolo branches), with disjoint write sets to prevent conflicts. - Strict fix-vs-propose boundary: Directly fixes unambiguous issues in the scope's own harness (dead links, oversized files, completed modification rows) while never touching managed harness files or project content, and proposing anything that changes meaning. - Consolidated report: Writes a structured review report (waiting on you, adjusted, stalled, progress, proposals) into the scope's notes directory, linked from INBOX.md. - Use Case: Ask for a roadmap review at the end of a sprint; the skill sweeps every harness front, reinstalls stale managed harnesses, prunes completed modifications, and hands you a report of decisions only you can make. ## Quick Start Ask the agent to run a weekly review of the current project scope and produce a report of fixes and proposals.

Frequently Asked Questions about weekly-review

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

FAQPage Schema
How do I run a periodic review of my project roadmap and harness?▼

Invoke the weekly-review skill on the current scope. It runs pop_status.py and pop_validate.py first, then launches parallel subagents to sweep fronts like specs, notes, memory, and worktrees, and finally writes a consolidated report in the scope's notes directory.

What does the weekly review fix automatically versus propose?▼

It directly fixes unambiguous issues in the scope's own harness, such as dead links, oversized files, and completed modification rows. Anything that changes meaning, like rewriting a spec contract or promoting an epoch, is reported as a proposal for human decision.

Does the weekly review create kanban cards or move tasks?▼

No. The review always runs outside the kanban: it never creates cards, opens branches, moves tasks, or touches project content. Reviewing the harness is maintenance of the material the kanban consults, not kanban work itself.

Can the review edit managed harness files like WORKFLOW.md?▼

No. Managed harness files such as WORKFLOW.md, templates, and scripts are never edited. Staleness in that class is resolved by reinstalling from the origin with pop_install_unirepo.py, and any other finding is only reported.

Why does the review use parallel subagents instead of one pass?▼

Collection and correction are delegated to waves of 3-5 parallel subagents, one per front, with disjoint write sets so no two workers edit the same file. This keeps the main agent as orchestrator and prevents corrections from overwriting each other.

What happens when the harness origin hosts child project scopes?▼

If an origin-scope.md file sits next to SKILL.md, extra fronts apply: freshness checks of installed harnesses via --check-fresh, managed-set boundary audits, drift diffs, index-versus-reality checks, stalled projects, and pending drafts.