skills.rest
Barbaros911
Barbaros911COMMUNITY
Explore all skills by this author →
GitHub

standup-solo

Generates a structured five-minute personal standup summary from yesterday's work notes and commits.

Updated Aug 12, 2026
Search Tags:#productivity#blockers#reflection#solo developer#standup#priorities#daily check-in
One-click install
npx skills add https://github.com/Barbaros911/As-mine --skill standup-solo-barbaros911
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: standup-solo
Source: https://github.com/Barbaros911/As-mine/tree/main/.claude/skills/solo-skills/standup-solo
Command: npx skills add https://github.com/Barbaros911/As-mine --skill standup-solo-barbaros911

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Solo developers lack a team to hold them accountable, making it easy to lose track of what shipped, what is blocked, and what actually matters today. This Skill forces five minutes of structured daily reflection without turning it into a project management session. ## Core Features & Use Cases - Three-question framework: Separates what actually shipped yesterday from work merely started, surfaces blockers, and forces commitment to a single #1 priority for today. - Flexible inputs: Accepts git logs, sent emails or chat messages, todo app screenshots, or a raw stream-of-consciousness brain dump. - Anti-pattern guardrails: Prevents listing hopes as accomplishments, multiple top priorities, and silently accumulating blocked items beyond three days. - Use Case: A freelance developer pastes yesterday's git log and a few notes, then receives a Markdown standup with shipped items, carry-overs, blockers, and one committed priority for the day. ## Quick Start Ask the assistant to run a solo standup using yesterday's git log and a short brain dump of what you worked on.

Frequently Asked Questions about standup-solo

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

FAQPage Schema
How do I run a daily standup as a solo developer?▼

A solo standup answers three questions: what you actually finished yesterday, what is blocked or about to block you, and the single most important thing today. Provide yesterday's git log, messages, or a rough brain dump and receive a structured Markdown summary.

What inputs can I use for a personal standup?▼

You can paste yesterday's git log, sent emails or Slack messages, a screenshot of your todo app, or a stream-of-consciousness brain dump. If you provide nothing, you will be asked for three rough bullets about yesterday's work.

What is the difference between a standup and a postmortem?▼

A standup is a five-minute daily check-in covering yesterday, blockers, and today's priority. A postmortem is a multi-day retrospective analyzing what went wrong or right over a longer period, which requires a different skill.

When should I not do a solo standup?▼

Skip the standup when you need multi-day retrospectives or sprint planning, since those require different granularity. Also avoid pushing through standup routines when clearly burned out; rest is the better recommendation.

Why does the standup limit today to one top priority?▼

Having five number-one priorities means having zero priorities. Forcing a single committed priority creates accountability, and secondary items are only listed to tackle after the first one finishes.

Related Skills

Explore More Personal & Entrepreneur Skills→
jiahao-shao1jiahao-shao1
36

daily-summary

Aggregate Claude Code sessions, Git commits, and Notion tasks into a timeline report.

Community
Intermediate
clawpod-appclawpod-app
46

evening-review

Summarize daily accomplishments, move unfinished tasks, and list tomorrow's top 3 priorities.

Community
Intermediate
XGanQAQXGanQAQ
1

retrospective

Generate structured markdown sprint retrospectives from git history and plan data.

Community
Intermediate
jupitermoneyjupitermoney

sprint-plan

Estimate capacity, select stories, and identify risks for sprint planning.

Official
Advanced