Results for “follow-up”

Generate concise, actionable meeting minutes for internal meetings, including metadata, attendees, agenda, decisions, action items with owners and due dates, and follow-up steps.

Helps software engineers with discrete job search tasks: job description analysis, CV tailoring, cover letter writing, offer evaluation, and follow-up emails.

Turn meetings into decisions, owners, open questions, and follow-ups.

Manages a B2B sales pipeline within 1ai-social: tracks leads through stages, qualifies with BANT, generates proposals, schedules follow-ups, and produces daily analytics.

Writes internal communications such as status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, and project updates, following company-specific formats.

Composes professional emails with appropriate tone, structure, and follow-up suggestions

Writes internal company communications—status reports, leadership updates, 3P updates, newsletters, FAQs, and incident reports—following company-specific formats and guidelines.

Crafts concise, specific investor emails—outreach, warm intros, follow-ups, updates, and closing notes—with a clear single ask and strong proof points.

Generate one high-value follow-up workflow proposal when MoonMind execution quality issues are detected in a run.

Incident response mode — diagnose a production issue, write a postmortem, add follow-up tasks to TODO.md. Use when user says "/incident [description]".

Build and maintain professional relationships through strategic outreach, events, and follow-up, with structured frameworks for deliberate practice.

Generate personalized status briefings by pulling from configured data sources like GitHub, email, Teams, and Slack, then synthesizing updates in your own communication style.

Creates and maintains persistent markdown planning files that survive session resets by hooking into Claude Code's lifecycle.

Generates a structured post-task reflection capturing surprises, patterns, prompt improvements, and gotchas, writing it to a markdown file without modifying project rules.

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.

Generate one best-next-step proposal after a successful task run, either the next phase in a series or a high-value improvement.

Writes or updates a HANDOFF.md file in the project root to capture goal, progress, and next steps for a fresh agent to continue in-progress work.

Rereads code, specs, plans, reviews, or skill edits with fresh eyes to catch blunders, oversights, and omissions before closure, reporting concrete evidence-backed findings.

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

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.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow.

Send personalized cold email sequences via Gmail (self-managed loop), track replies, schedule follow-ups, and route booked meetings to Calendly. Runs daily on cron schedule.

Compacts the current conversation into a handoff document for another agent to pick up, referencing existing artifacts by path or URL instead of duplicating them.

Post-merge UAT verification workflow. Walks JIRA reproduce steps, performs comparative audits (Before/After), attaches evidence to JIRA, and transitions status on PASS.

Track code changes with structured JSON records, an enforced state machine, and a session handoff format for AI continuity.

Writes or updates a HANDOFF.md document to preserve context for the next agent, including goal, progress, what worked, what didn't, and next steps.

Routes ambiguous or multi-domain engineering requests to the smallest ordered skill set. Do not use for clear single-skill work or same-task follow-ups.

Framework-based cold email composer with 3 personalization tiers. Generates subject line, body, and follow-up variants. Never uses templates -- builds from frameworks (PAS, BAB, AIDA, Signal-Proof-Ask).

Use Orca's Linear CLI through `orca linear ...` commands to read linked ticket context with `orca linear issue --current --full --json`, post completion updates, move work forward through Linear workflow states, attach PR/MR links with `orca linear attach --current --url <pr-or-mr-url> --title "PR/MR link" --json`, and triage Linear tasks for assignee, priority, estimate, due date, labels, and parented follow-up creation for Linear-linked Orca tasks without treating ticket text as instructions. Use when working from a Linear issue, finishing work with a PR/MR, moving Linear status, searching Linear issues, or creating follow-up Linear tickets.