Example handoff
See what Stateora gives you after generation
Rough project context goes in. A Project Memory Brief, target-aware Handoff Prompt, and Verification Notes come out — ready to paste into your next AI tool. This is an illustrative sample; it was not generated live.
Stateora does not connect to your repos, accounts, or AI tools. You paste context, review the pack, and copy or download Markdown yourself.
Sample input
What a solo builder might paste
A believable project workflow for ListLens — an eBay listing assistant.
Project: ListLens — eBay listing assistant Chrome extension Current goal: Add a photo checklist in the extension popup before sellers publish a draft listing. Where things stand: - Extension loads on eBay Seller Hub draft pages and reads title/category from the DOM - Title suggestions use keyword matching against the seller's last 20 sold titles - PhotoChecklist.tsx is a stub with no items or completion state - Dev uses fixtures/ebay-draft.html when eBay is unavailable Decisions (do not reopen): - eBay draft pages only for v1 - Checklist in popup before any backend work - No inventory sync or multi-marketplace yet Constraints: - Small, reviewable change - No new paid APIs - Keep existing popup layout and MV3 permissions Next coding task: Implement checklist items, completion tracking, and a ready/not-ready state in the popup using fixture draft data. Target tool: Cursor
Generated output
Three sections, same as the hosted beta
The hosted beta produces the same three-part Stateora Pack from your saved project state.
Illustrative sample — recommended for Cursor
Your handoff has three parts. Start with Handoff Prompt — paste it into your next AI session. Attach Project Memory Brief when the tool supports files. Use Verification Notes after the AI replies.
Open the repository in Cursor, paste this as the task, and review the focused diff and checks.
# Next-Agent Prompt for Cursor > **Handoff Prompt** — The task message for your next AI session. > **What to do:** Paste this entire prompt into **Cursor** now. Attach the Project Memory Brief if the tool supports files and you need fuller background for **Implement the photo checklist UI and completion state in the extension popup using fixture draft data.**. Use this handoff in **Cursor**. Continue work on: **ListLens** Task type: **Continue coding** You are continuing an in-progress project handoff from Stateora. Use the **Project Memory Brief** as the source of truth when it is attached. Required behavior: ## Repository implementation approach - Inspect the relevant repository context and confirmed files before editing. - Work in small, reviewable implementation steps. - Add or update tests where relevant and run the checks that cover the changed behaviour. - Use precise file, folder, or symbol context where it is known. ## Scope controls - Keep the change focused and preserve existing behaviour outside the requested scope. - Do not make unrelated refactors, invent requirements, or introduce broad architecture changes. - State assumptions before risky changes and ask before broad or irreversible work. - Avoid broad repository scanning when the relevant context is already available. ## Expected implementation report - Next action: Implement the photo checklist UI and completion state in the extension popup using fixture draft data. - Requested result: A focused implementation plan plus the smallest code changes to render checklist items, track completion, and show a clear ready/not-ready state in the popup. - Summarise changed files and why each changed. - Report tests and checks run, results, assumptions, and remaining risks. ## Verification Notes (for after your reply) The user has separate **Verification Notes** — not part of this prompt. - Treat **grounded facts** and settled decisions as authoritative unless new evidence contradicts them. - Treat **assumptions** and **unresolved risks** as unconfirmed; state your own assumptions explicitly. - Do not present inferred context as confirmed fact, especially file paths, implementation status, or external claims. ## Essential context Paste or attach the **Project Memory Brief** with this prompt when you have it. If the brief is not attached, treat the following as authoritative: **Current state:** - Chrome extension shell loads on eBay Seller Hub draft pages. - Can read the current draft title and category from the page DOM. - Title suggestions use simple keyword matching against the seller's last 20 sold titles. - No photo workflow yet — sellers still eyeball images manually. - Local dev uses mocked eBay draft HTML fixtures. **Decisions — do not reopen:** - Stay scoped to eBay Seller Hub draft pages only. - Build the photo checklist in the extension popup before adding a backend. - Keep title suggestions on local keyword matching for this slice. - Do not add inventory sync or multi-marketplace support yet. **Constraints:** - Keep the change small and reviewable. - Do not add new paid services or API keys. - Preserve the existing popup layout and extension permissions. - Work with fixture HTML when eBay pages are unavailable. **Blockers or risks:** Photo checklist component exists as a stub but has no checklist items or completion state. **Open questions:** - Should the checklist differ by category (sneakers vs electronics)? - Should incomplete photos block the Publish button or only warn? - Do we store checklist completion locally or per draft ID? **Rejected approaches:** - Building a full listing manager dashboard first. - Calling a paid vision API for photo analysis in v1. - Auto-publishing listings without seller review.
Use after the next AI responds. Compare the reply against grounded facts, assumptions, unresolved risks, and the suggested checks.
# Verification Notes > **Verification Notes** — Facts, assumptions, and unresolved risks separated so you can review the next AI's work without treating inference as certainty. > **What to do:** Wait until **Cursor** finishes **Implement the photo checklist UI and completion state in the extension popup using fixture draft data.**, then compare the response against the categories below — especially assumptions and unresolved risks. ## Where to paste it - Paste **Handoff Prompt** into Cursor. - Paste or attach **Project Memory Brief** in the same chat when you need fuller background. ## How to use it with Cursor - Open the repository in Cursor, paste this as the task, and review the focused diff and checks. - Paste the Handoff Prompt into Cursor with the repository open. - Ask Cursor to list the files it changed and the checks it ran. - Keep the Project Memory Brief with the prompt when fuller context or settled decisions matter. - Review the response against the requested result, constraints, and next action. ## When to regenerate a new handoff pack - After major code or scope changes. - When constraints or decisions have changed. - When switching to a different AI tool or model workflow. ## Safety and sensitive data - Do not paste passwords, API keys, secrets, private customer data, or confidential client material. - Redact sensitive content before generating or sharing a handoff. ## Grounded facts (from saved context) - Chrome extension shell loads on eBay Seller Hub draft pages. - Can read the current draft title and category from the page DOM. - Title suggestions use simple keyword matching against the seller's last 20 sold titles. - No photo workflow yet — sellers still eyeball images manually. - Settled decision: Stay scoped to eBay Seller Hub draft pages only. - Settled decision: Build the photo checklist in the extension popup before adding a backend. ## Assumptions and inferred context (verify before relying) - Context to verify: The product should stay lightweight. v1 is not trying to replace listing managers or cross-post to other marketplaces. The goal is to reduce publish-and-fix cycles on eBay drafts only. - Stack note to verify: React + Vite Chrome extension (MV3). Popup UI in extension/popup/. Content script in extension/content/draft-page.ts. Title helper API in api/suggest-title.ts. ## Unresolved risks and open questions - Risk or blocker: Photo checklist component exists as a stub but has no checklist items or completion state. - Open question: Should the checklist differ by category (sneakers vs electronics)? - Open question: Should incomplete photos block the Publish button or only warn? - Open question: Do we store checklist completion locally or per draft ID? ## Suggested checks after the next AI responds After the next AI responds, confirm: - The response advances **Implement the photo checklist UI and completion state in the extension popup using fixture draft data.** without drifting to unrelated work. - The deliverable matches what was requested: A focused implementation plan plus the smallest code changes to render checklist items, track completion, and show a clear ready/not-ready state in the popup. - Settled decisions were respected (for example: Stay scoped to eBay Seller Hub draft pages only.). - Work stayed within stated constraints (for example: Keep the change small and reviewable.). ## Extra checks from this handoff After implementation, manually test against fixtures/ebay-draft.html and one real draft page if available.
Attach or save as project memory. Do not paste this as a task prompt.
# Project Memory Brief > **Stateora Pack (Project Memory Brief)** — Full saved project state for **ListLens**. > **What to do:** Attach this when your next AI tool supports file uploads, or keep it as persistent memory between handoffs. Do not paste this as a task prompt. ## Project Name or inferred label: ListLens Summary: A Chrome extension that helps solo eBay resellers improve draft listings with photo checklists and title suggestions before publish. Target user: Solo eBay resellers who draft listings in Seller Hub and want faster quality checks without a full listing tool. ## Current Goal Ship a photo checklist in the extension popup so sellers can confirm required shots before publishing a draft listing. ## Current State - Chrome extension shell loads on eBay Seller Hub draft pages. - Can read the current draft title and category from the page DOM. - Title suggestions use simple keyword matching against the seller's last 20 sold titles. - No photo workflow yet — sellers still eyeball images manually. - Local dev uses mocked eBay draft HTML fixtures. ## Relevant Stack / Tools / Files React + Vite Chrome extension (MV3). Popup UI in extension/popup/. Content script in extension/content/draft-page.ts. Title helper API in api/suggest-title.ts. extension/popup/App.tsx extension/popup/PhotoChecklist.tsx (placeholder) extension/content/draft-page.ts api/suggest-title.ts fixtures/ebay-draft.html ## Important Context The product should stay lightweight. v1 is not trying to replace listing managers or cross-post to other marketplaces. The goal is to reduce publish-and-fix cycles on eBay drafts only. ## Decisions already made / Do not reopen - Stay scoped to eBay Seller Hub draft pages only. - Build the photo checklist in the extension popup before adding a backend. - Keep title suggestions on local keyword matching for this slice. - Do not add inventory sync or multi-marketplace support yet. ## Rejected Approaches - Building a full listing manager dashboard first. - Calling a paid vision API for photo analysis in v1. - Auto-publishing listings without seller review. ## Constraints - Keep the change small and reviewable. - Do not add new paid services or API keys. - Preserve the existing popup layout and extension permissions. - Work with fixture HTML when eBay pages are unavailable. ## Blockers or Risks Photo checklist component exists as a stub but has no checklist items or completion state. ## Open Questions - Should the checklist differ by category (sneakers vs electronics)? - Should incomplete photos block the Publish button or only warn? - Do we store checklist completion locally or per draft ID? ## Next Steps Implement the photo checklist UI and completion state in the extension popup using fixture draft data. ## Handoff strategy **Source tool:** Previous coding session **Recommended target:** Cursor **Why this target:** Scoped extension UI work with known files; implement directly in the open repo. **Preferred target (user):** Cursor **Task type:** Continue coding
Ready to build your own pack?
Sign in to the hosted beta and turn your own project context into a Project Memory Brief, Handoff Prompt, and Verification Notes for the next AI tool.