Results for “follow-ups”

Generates investor outreach emails and monthly updates with templates for warm intros, cold outreach, follow-ups, and a Day 5/10/21 cadence.

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.

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.

Configures personalized status briefings by learning your communication style, audiences, and data sources through an interactive conversation.

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.

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

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

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

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

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.

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.

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.

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

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.

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

Transcribe meeting audio with speaker diarization, generate structured summaries with action items, decisions, and follow-ups, and support multiple audio formats and languages. Use when the user requests meeting transcription or provides relevant inputs for this workflow.

Local CLI issue tracker for todos, follow-ups, structured records, and the canonical pattern for decomposing multi-step work into a parent + subissues with acceptance criteria, dependency edges, and priority. Use when the user mentions a task to remember, a bug to track, an open question, anything that needs to outlive the current turn, or when planning multi-heartbeat work that needs `chainlink issue ready`-driven pickup across sessions. Includes guidance on writing descriptions future-you can act on (handles, success path, failure path) and idempotency tactics for actions that might fire twice (boundary firing, overlapping heartbeats, retried subagent completion). Pairs with five-whys (chainlink is the storage backend for RCA trees). Storage is local — issues live under a `.chainlink/` directory in the operator's repo.