standup-formatter

Included with Lifetime

$97 forever

Use when generating standup reports, daily updates, or team status summaries. Formats work activity into concise standup format.

General

What this skill does


<essential_principles>
## Standup Philosophy

### Purpose
Standups exist to:
1. Share blockers that need help
2. Coordinate on dependencies
3. Keep work visible

Standups do NOT exist to:
- Report hours worked
- Justify existence
- Detail every task

### The Ideal Standup

**Done**: What you completed (outcomes, not activities)
**Today**: What you're working on (1-2 focus items)
**Blockers**: What's preventing progress (specific, actionable)

### Time Budgets

- Speaking: 60 seconds max per person
- Written: 3-5 bullet points total
- Detail level: Enough to understand, not to replicate

## Format Guidelines

### Good Examples
```
Done: Merged PR for user auth (#234)
Today: Starting payment integration
Blockers: Waiting on API spec from backend team
```

### Bad Examples
```
Done: Worked on stuff, had meetings, reviewed some code,
      wrote tests, fixed bugs, updated docs, etc.
Today: More of the same
Blockers: Nothing
```

### Async vs Sync

**Async (written):**
- More detail acceptable
- Include links to PRs/tickets
- Post by 9am team time

**Sync (spoken):**
- Extremely concise
- No reading from notes
- Save details for follow-ups
</essential_principles>

<intake>
What standup format do you need?

1. **Individual** - Your personal standup
2. **Team** - Aggregate team status
3. **Project** - Status for specific project

**For what timeframe?**
- Yesterday/today (daily)
- This week (weekly)
- Custom dates

**Source data?**
- Git activity
- Calendar events
- Manual input
</intake>

<templates>
## Individual Standup

```markdown
## Standup - [Date]

### Done
- [Completed item 1]
- [Completed item 2]

### Today
- [Focus item 1]
- [Focus item 2]

### Blockers
- [Blocker with specific need] / None
```

## Team Standup

```markdown
## Team Standup - [Date]

### [Person 1]
- Done: [summary]
- Today: [focus]
- Blockers: [if any]

### [Person 2]
...
```
</templates>

Files: 2

Size: 11.7 KB

Complexity: 16/100

Category: General

Source: https://github.com/aiskillstore/marketplace/tree/main/skills/chaiwithjai/standup-formatter

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts