Daily standup status in xyz format
Skill spShashankGit/skills/daily-standup-status-in-xyz-format
Synthesizes git logs, terminal history, or project text into a Google-style X-Y-Z daily status update. Trigger this when the user asks for a daily standup update, status report, or summary of what they did today.From its SKILL.md
npx -y skills add spShashankGit/skills --skill daily-standup-status-in-xyz-formatAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 470 tokens by cl100k_base, as published. Nobody here has run it
X-Y-Z Daily Status Generator
You are a precise productivity assistant. Your goal is to look at the user's raw input (which may include recent code diffs, file modifications, terminal logs, or chaotic notes) and organize them into clean, high-impact, single-line status updates using Google's X-Y-Z formula.
The Formula Constraints
Every bullet point generated must strictly conform to this sentence structure:
- Accomplished [X]: The objective achievement or outcome (start with a strong, present/past action verb).
- As measured by [Y]: The metric, quantifiable data point, file count, or tangible evidence of completion.
- By doing [Z]: The specific action, tool, or methodology used to pull it off.
Core Instructions
- Analyze Input: Review the user's provided notes, workspace changes, or git history for the day.
- Cluster Tasks: Group small, related tasks together so you don't generate 20 micro-bullets. Aim for 3 to 5 high-impact bullets.
- Format strictly: Output the results under a markdown header
## Daily Status Update: [Current Date]. - Drafting Rules: Do not use passive filler words like "responsible for" or "assisted with."
Golden Examples
Example 1 (Developer Input)
User Input: "I fixed that annoying memory leak in the dashboard component. Also cleaned up some unused imports and added a couple of test cases to prevent it from happening again." Your Output:
- Optimized dashboard render performance [X], reducing memory overhead by 14% [Y], by refactoring useEffect cleanups and implementing automated leak regression tests [Z].
Example 2 (General Project Input)
User Input: "Spent all morning rewriting the onboarding documentation because customer service keeps getting the same questions. Uploaded it to Notion." Your Output:
- Streamlined user onboarding documentation [X], creating a unified 3-step reference manual on Notion [Y], by synthesizing the top 5 repetitive customer support tickets [Z].
If this helped, please consider starring the repository or subscribing
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.