Menu
Generate a daily standup summary showing what was done, what is planned, and any blockers. Use when the user wants a status update or progress report.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | standup |
| description | Generate a daily standup summary showing what was done, what is planned, and any blockers. Use when the user wants a status update or progress report. |
| argument-hint | optional: date or range |
Generate a standup summary by gathering information from multiple sources.
Gather activity data:
git log --oneline -20 for recent commits.solopreneur/observer-log.md if it exists (recent entries).solopreneur/ subdirectories for recently created/modified files:
.solopreneur/discoveries/ - discovery briefs.solopreneur/specs/ - product specs.solopreneur/designs/ - design docs.solopreneur/plans/ - build plans (check for completion checkboxes).solopreneur/plans/ - implementation plans.solopreneur/releases/ - release notesCheck plan progress:
.solopreneur/plans/[x]) vs pending ([ ]) stepsGenerate standup in this format:
# Standup - [Date]
## Done
- [Completed items with brief descriptions]
## In Progress
- [Items currently being worked on, with % completion if from plans]
## Up Next
- [Suggested next steps based on lifecycle flow]
## Blockers
- [Any issues, failed steps, or decisions needed from the CEO]
## Team Activity
- [Which agents were invoked and what they produced]
Save to .solopreneur/standups/{date}.md (create the directory if needed).
Design and scaffold your own AI org structure with custom agents, skills, teams, hooks, and MCP servers. Interactive wizard that interviews you, proposes an org, generates a visual chart, and creates all files.
Create design direction, HTML mockups, and UI/UX recommendations for a feature or product. Use when the user needs visual direction, component specifications, or user flow diagrams.
Research and validate product ideas, market opportunities, or feature concepts. Use when the user wants to explore whether an idea is worth pursuing, needs competitive analysis, or wants to understand a market.
Review code, specifications, or designs for quality, bugs, security, and best practices. Use when the user wants feedback on recent work, a pull request, or any artifact.
Execute a batch of backlog tickets in parallel. Use when the user wants to build multiple unblocked tickets simultaneously with integrated QA review.
Break a spec or feature into prioritized, dependency-tracked tickets for implementation. Use when a spec is too large to build at once, or when the user wants to create individual work items with MVP/P1/P2 phasing.