What sources does Standup pull from?

Git log --oneline -20, .solopreneur/observer-log.md (if present), and the .solopreneur/{discoveries, specs, designs, plans, releases} folders.

Can I customize the date range?

Yes, you can pass an optional date or range to scope the standup.

Where is the standup report saved?

The report is saved to .solopreneur/standups/{date}.md.

standup

Scanned

npx machina-cli add skill pcatattacks/solopreneur-plugin/standup --openclaw

Files (1)

SKILL.md

1.6 KB

Daily Standup

Generate a standup summary by gathering information from multiple sources.

Process

Gather activity data:
- Check git log --oneline -20 for recent commits
- Read .solopreneur/observer-log.md if it exists (recent entries)
- Scan .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 notes
Check plan progress:
- Read any plan files in .solopreneur/plans/
- Count completed ([x]) vs pending ([ ]) steps
- Identify any blocked or failed steps

Generate 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).

Source

git clone https://github.com/pcatattacks/solopreneur-plugin/blob/main/skills/standup/SKILL.mdView on GitHub

Overview

Standup automatically compiles a daily status summary by aggregating recent commits, observer logs, and changes in .solopreneur folders. It highlights completed work, ongoing tasks with progress, upcoming steps, blockers, and team activity for clear stakeholder updates.

How This Skill Works

It gathers activity data from git log --oneline -20, reads .solopreneur/observer-log.md if present, and scans designated .solopreneur subdirectories for new or modified files (discoveries, specs, designs, plans, releases). It reads plan files to count completed [x] vs pending [ ] steps, flags blocked or failed items, and outputs a Markdown standup with sections Done, In Progress, Up Next, Blockers, and Team Activity, then saves the report to .solopreneur/standups/{date}.md.

When to Use It

Daily status updates for solo projects or small teams
Pre-stakeholder reviews requiring a concise progress snapshot
End-of-day wrap-up to track progress against a release
When blockers emerge that need visibility or decisions
Regular checks to surface activity from discoveries, specs, designs, plans, and releases

Quick Start

Step 1: Provide an optional date or range to scope the standup.
Step 2: Run Standup to gather data from git log --oneline -20, .solopreneur/observer-log.md, and the .solopreneur subdirectories (discoveries, specs, designs, plans, releases).
Step 3: Review the generated Markdown and save it to .solopreneur/standups/{date}.md

Best Practices

Specify a date or range to scope the standup for precision
Cross-check git log, observer-log, and .solopreneur folders for accuracy
Review plan progress by counting completed [x] vs pending [ ] steps and note blockers
Keep Done and In Progress items brief with actionable descriptions
Include clear next steps and team activity notes for accountability

Example Use Cases

Done: Implemented OAuth login; In Progress: UI wiring for dashboard (60%); Up Next: Add unit tests for API layer; Blockers: Backend auth service latency; Team Activity: Agent dev-bot produced login-api.md and dashboard-wireframe.pdf
Done: Draft discovery brief; In Progress: Specs review; Up Next: Design pass; Blockers: Waiting on stakeholder decision; Team Activity: Agent bot-generated discoveries/brief.md
Done: Release notes for v0.1; In Progress: Implement tests; Up Next: Optimize build; Blockers: Flaky tests; Team Activity: Agent release-notes.md and test-run.log
Done: Updated observer-log with yesterday's entries; In Progress: Plans show 3/5 complete; Up Next: Finalize rollback plan; Blockers: Missing approval; Team Activity: Agent ops produced migrations.md
Done: Fixed migration script; In Progress: Documentation updates; Up Next: Prepare demo; Blockers: None; Team Activity: Agent doc-bot produced migrations.md

Frequently Asked Questions

Add this skill to your agents