Results for “follow-ups”

Generate today's standup: what was done, what is in progress, what comes

Use to design overnight and follow-the-sun support — coverage models, handoff quality and measuring what is lost between shifts. Trigger for "after-hours coverage", "follow the sun", overnight support design, night shift vs defer async, handoff packet, shift handover quality, global coverage gaps, or when customers reopen tickets after every handoff.

Start-of-session context pickup. Reads the latest handoff file and resumes work where the last session left off. Run this at the start of a new session if a handoff file exists.

Iterate on a pull request until actionable CI checks pass and high/medium review feedback is addressed, stopping at human approval, draft, or merge gates.

Provides patterns and lived experience from an AI partner in a long-term creative partnership, helping AI agents build trust, match energy, push back constructively, and support human breakthroughs.

Progress Tracking

Use after design approval for milestone plans with executable acceptance.

Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.

Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]

Conducts structured post-breach remediation using a lessons learned framework covering root cause remediation, control gap closure, policy updates, training modifications, monitoring enhancements, and regulatory follow-up. Provides a systematic approach to preventing breach recurrence and demonstrating accountability to supervisory authorities. Keywords: post-breach, remediation, lessons learned, root cause, control gap, policy update, training.

Update old notes with new connections. The backward pass that /reflect doesn't do. Revisit existing notes that predate newer related content, add connections, sharpen claims, consider splits. Triggers on "/reweave", "/reweave [note]", "update old notes", "backward connections", "revisit notes".

Applies the same change across multiple repositories in parallel using git worktrees, tests, and pull requests.

Turn "we should get press" into an earned-media plan a journalist might actually answer. The story angle worth their byline, a target list by beat, a pitch built for one reporter at a time, and a follow-up rhythm that is persistent without being a pest. Built for B2B teams doing their own PR, customizable to your story and your beats. Trigger on "help me pitch this", "build a PR plan", "which journalists cover this", "write a media pitch", "how do I follow up with press", or any earned-media outreach question.

Comprehensive checklist for documenting follow-up work and testing needs after implementation

Advises assessing efficacy and safety at least monthly for the first 3 months, then at least every 3 months for all patients prescribed weight‑loss medications. Triggers include clinician questions such as “How often should I check progress after starting orlistat?” or “What is the follow‑up schedule for a patient on liraglutide?”.

Rebuilds working context after a session clear by reading git history, plans, and beads issue state, then produces a visible briefing.

Outreach triggered by funding events with post-funding needs analysis and personalized drafts

Use to define handoff standards for support transfers and to measure whether context survives the handoff — cold vs warm, required fields, and re-ask rate after transfer. Trigger for "transfer protocol", "warm handoff", "customers repeat themselves after transfer", "ping-pong between teams", "what should agents include when transferring", handoff quality, or re-ask rate after escalation.

Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

OpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex". (gstack) Voice triggers (speech-to-text aliases): "code x", "code ex", "get another opinion".