skills.rest
serejaris
serejarisCOMMUNITY
Explore all skills by this author →
GitHub

weekly-retro

Automate weekly retrospectives for solo founders across repositories and projects.

215|26|Updated Dec 15, 2025
Search Tags:#automation#retrospective#backlog#issue-tracking#product-management#ai-assisted#weekly-retro
One-click install
npx skills add https://github.com/serejaris/personal-corp-skills --skill weekly-retro-serejaris
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: weekly-retro
Source: https://github.com/serejaris/personal-corp-skills/tree/main/skills/weekly-retro
Command: npx skills add https://github.com/serejaris/personal-corp-skills --skill weekly-retro-serejaris

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Weekly reviews for solo founders are chaotic — no structure, facts get lost, and action items stay in your head instead of the backlog.

Core Features & Use Cases

  • Gather data across repos and project tools to surface the week's facts.
  • Conduct an interview sequence with the founder to capture context and decisions.
  • Optional advisory analysis by multiple sub-agents to surface risks and opportunities.
  • Compile a concise retro summary, and route actions to the correct repos as issues.
  • Create a backlog and wrap up with a plan for the next week.

Quick Start

Add the weekly retro section to your CLAUDE.md project and run the retro workflow to gather data, conduct the interview, and generate the backlog.

Frequently Asked Questions about weekly-retro

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

FAQPage Schema
How do I automate weekly retrospectives for solo founders across multiple repositories?▼

Weekly retrospectives for solo founders are automated by coordinating data gathering, interviewing, analysis, and backlog creation across multiple repositories. The workflow enforces phase discipline and outputs a retro log plus an outcomes scorecard to support planning.

What is the best way to structure a weekly retrospective and route action items to a backlog?▼

Structure a weekly retrospective by conducting an interview sequence to capture context, compiling a concise summary, and routing actions to the correct repositories as issues. This creates a structured backlog and wraps up with a plan for the next week.

Can I use an AI-assisted workflow to surface risks and opportunities during my weekly retro?▼

Yes, AI-assisted workflows support weekly retros by using optional advisory analysis with multiple sub-agents to surface risks and opportunities. This analysis feeds into the retro summary and backlog creation to improve project planning outcomes.

Does a weekly retrospective workflow require dependencies or specific issue-tracking tools?▼

Weekly retrospective workflows have no dependencies and operate independently. They gather data across project tools and repositories to surface facts, conducting interviews and generating scorecards without requiring specific issue-tracking integrations.

How do I start a weekly retro workflow and store the results?▼

Start a weekly retro workflow by adding the weekly retro section to your CLAUDE.md project file. Running the workflow gathers data, conducts the interview, and generates the backlog while storing results in canonical files.

Related Skills

Explore More Personal & Entrepreneur Skills→
cloudofgeorgecloudofgeorge

gstack-openclaw-retro

Analyze engineering activity to generate weekly retrospectives with per-author attribution.

Community
Advanced
serejarisserejaris
215

weekly-planning

Convert retro findings and backlog into prioritized weekly outcomes with assigned owners.

Community
Intermediate
GDSDNGDSDN
3

qa-backlog-add-followup

Create prioritized, tagged QA follow-up items linked to project backlog stories.

Community
Intermediate
Nir-BhayNir-Bhay
19

backlog-refinement-guide

Guide backlog refinement sessions using the DEEP framework and Planning Poker.

Community
Intermediate