Prepare a project handoff using recent work records and checks of current materials. Give the recipient a verified status, accessible artifact locations, blockers, and concrete next steps, while distinguishing delivered work from drafts and intentions.
Prepare an evidence-backed handoff with current state, relevant artifacts, blockers, and next actions.
Review the instructions the agent will receive before you install.
Identify the project and intended recipient. Use screenpipe-api to recover recent work, decisions, and artifact references; inspect current project files or connected systems when available to verify what still applies.
Give the recipient the purpose, verified current state, where to continue, blockers, and concrete next steps. Distinguish merged or delivered work from drafts, tests, and intentions. Name owners and dates only when supported; otherwise leave them open.
Include source links and exact artifact locations that the recipient can access. Remove unrelated conversations, credentials, and private customer details. Draft in chat unless another destination is requested. A handoff request alone does not authorize sending it, granting access, or assigning work.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Develop and test Windows-specific Screenpipe changes on a disposable Azure virtual machine. The workflow verifies native behavior, preserves logs and desktop video, and handles branch and pull request delivery when authorized.
Prepare screenpipe component releases by updating versions and dependency lock files, running required build checks, and triggering GitHub Actions. Verify build results and release artifacts, then hand public app publication over to a person.
Create charts, dashboards, scorecards, and styled summaries as standalone HTML reports for the screenpipe viewer. Keep styles, scripts, and images inside the file so the report renders in a sandbox with no network access.
Search Screenpipe recordings, screen text, audio transcripts, and synced-device history through its local API. Use the evidence to review activity, find meeting details, and inspect saved workflows, including recorded steps that can inform automation.
Use Screenpipe’s local REST API, an interface for programmatic requests, to search screen and meeting history, review app activity and active time, retrieve synced-device records, export recordings, and rerun audio transcription.
Turn a recorded software failure into a draft bug report with timestamps, reproduction steps, expected and actual behavior, and relevant evidence. Separate visible symptoms from possible causes and remove sensitive details from shareable evidence.