protosphinx/sphinxstack - Page 26

write-a-technical-tutorial

Turn a working technical process into a reproducible tutorial with explicit prerequisites, copy-safe steps, expected observations, troubleshooting, and a clean-environment verification. Use when documenting setup, integration, analysis, deployment, or another…

write-a-test-plan

Turn a product or code change into a risk-based test plan with environments, cases, ownership, and release evidence. Use when someone asks what to test, needs QA coverage for a feature, or wants a repeatable verification plan before release.

write-a-unit-test

Write a focused deterministic unit test that specifies one behavior, boundary, failure, or invariant with useful diagnostics. Use when a small code unit can be verified without production dependencies.

write-a-video-description

Write an accurate video description with useful context, chapters, credits, accessibility links, sources, and calls to action. Use when publishing video to a searchable or shared platform.

write-a-work-status-update

Turn working notes into a concise status update covering outcomes, evidence, risks, decisions, and next actions. Use when reporting project or operational progress.

write-accessible-error-messages

Write accurate error messages that help users understand and recover. Use when forms, workflows, permissions, services, or validation need text that works with assistive technology and without guesswork.

write-an-academic-cv

Write an academic CV that organizes research, teaching, service, recognition, and institutional contribution for a specific review. Use when applying for academic appointments, promotion, tenure, fellowships, or visiting roles.

write-an-accessible-policy-document

Write an accessible policy document with clear rules, navigable structure, usable formats, inclusive language, defined terms, exceptions, contacts, and verified source fidelity. Use when people must understand and act on an authoritative policy.

write-an-annotated-bibliography

Produce consistent source annotations that summarize, evaluate, and explain relevance without copying abstracts. Use when preparing a research project or source review.

write-an-architecture-decision-record

Record a consequential technical decision with context, constraints, considered options, trade-offs, consequences, and conditions for review. Use when a team must choose an architecture, dependency, data model, protocol, or operational approach that will be…

write-an-event-invitation

Write an accurate and accessible invitation with a clear reason to attend and next step. Use when an event needs email, page, message, or printed invitation copy.

write-an-event-recap

Turn an event record into an accurate recap with outcomes, resources, and next steps. Use when participants, sponsors, leaders, or the public need a durable summary after an event.

write-an-executive-resume

Write an executive resume that shows verified scope, decisions, systems, teams, and outcomes without inflated leadership language. Use when senior hiring, board, advisory, or succession decisions need concise evidence.

write-an-incident-communication-plan

Write an incident communication plan for audiences, triggers, verified facts, uncertainty, channels, approvals, accessibility, cadence, correction, and closeout. Use when service, safety, security, privacy, operational, or public incidents require timely…

write-an-incident-communication

Write timely incident updates that distinguish facts, impact, actions, and uncertainty. Use when preparing internal notices, status pages, customer messages, leadership briefings, or recovery updates during a disruption.

write-an-interview-brief

Write an interview brief that aligns purpose, participant context, evidence needs, consent, questions, and production roles. Use when a recorded conversation needs focused and ethical preparation.

write-an-operations-runbook

Create a dependable operations runbook for diagnosing, mitigating, recovering, and escalating one service condition. Use when on-call or support operators need a tested procedure that works without unwritten expert context.

write-clearly

Workshop one paragraph until it is plain and true. They type every word; you push back. Use when they say "help me write this", "does this sound okay", or paste a paragraph that reads puffed-up or machine-made.

write-meeting-notes

Capture a meeting's evidence, decisions, dissent, actions, owners, and unresolved questions. Use when participants need an accurate operating record rather than a transcript.

write-release-notes

Write audience-specific release notes from verified shipped changes, limitations, and required actions. Use when a product, library, service, or internal tool release needs an accurate customer or operator summary.

write-resume-bullet-points

Write resume bullets that connect owned action, scope, method, and verified outcome in compact language. Use when turning work, study, project, or volunteer evidence into experience entries.