Results for “status-reports”

Report what a repository is, what recent conversation history says about it, current application status, and outstanding work

Writes internal communications using company-specific formats and templates for status reports, leadership updates, newsletters, FAQs, incident reports, and project updates.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Write grant reports with progress, financials, and outcomes. TRIGGERS - Use when user needs help with grant-report related tasks.

Write business reports including executive summaries, status updates, postmortems, competitive analyses, data analyses, and quarterly reviews. Use when communicating findings, decisions, or status to stakeholders. Also trigger for 'executive summary', 'status report', 'postmortem', 'incident report', 'competitive analysis', 'quarterly review', 'business report', or 'data analysis report'.

Capture delivery evidence, commands, changed files, blockers, and standards feedback after a work session.

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Read-only queue dashboard for workspace-aware ship. (gstack)

Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

Pull latest changes from remote and report status

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Report-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".

Turn raw revenue data into a weekly or monthly wrap-up that drives action, not another dashboard screenshot. Position vs plan, what moved, the risks worth naming, and the specific next moves. Built for B2B revenue teams, customizable to your data and your cadence. Trigger on "write the revenue report", "how did we do this month", "revenue wrap-up", "are we on plan", "monthly number", or any revenue-recap request.

Report your own governed session state: authority band, budget spent/remaining, action count, denial count. Value-free and instant — answered by the governance layer, no subprocess, no credentials. Use when unsure what you are allowed to do or how much budget remains.

Report-only QA testing. (gstack)

Generate test report. Use when user says "test report", "results summary", "test status", "show results", "test dashboard", or "how did tests go".

Creates a 6-8 page horizontal-swipe weekly report deck with sections for shipped items, in-flight progress, blockers, metrics, and asks.

Write board reports with KPIs and strategic updates. TRIGGERS - Use when user needs help with board-report related tasks.