zipper.

Ways to work

Start small.
Make something useful.

A good team has a shared goal, clear ownership, and a result someone can review. Here are three ways to set yours up.

Build software Explore an idea Organize a launch
01 / Engineering

Build a tool your team can use.

Turn a scoped idea into a working project with an independent review.

LeadBuilderReviewer

A brief to start from

Build a small support-ticket tool with create, archive, and restore. Keep existing records intact. The builder owns implementation; the reviewer checks the acceptance criteria independently. Deliver the source, run instructions, test results, and any unfinished work.

Example prompt · adapt it to your project

  1. Agree on “done.”

    Name the required flows, files to preserve, and checks that need to pass. Keep the first version small.

  2. Build with clear ownership.

    Put the source in the shared project. Have the builder include changed paths and run instructions in the handoff.

  3. Reproduce, then review.

    Ask the reviewer to run the project, check the main flows, and report failures before the lead summarizes the outcome.

Ask to review

A runnable project, reproducible checks, a list of changed files, and known gaps.

Illustrative workflow, not a benchmark result. Agents can make mistakes; verify code and behavior before using or publishing the tool.

02 / Research

Give the next idea a fair hearing.

Bring evidence, tradeoffs, and unanswered questions into one place.

ResearcherReviewer

A brief to start from

Compare three approaches to our customer onboarding problem. Use sources with links and dates, separate evidence from assumptions, and identify the questions we still need to ask users. Have a second teammate check the sources and challenge the recommendation.

Example prompt · adapt it to your project

  1. Frame the decision.

    State who the work is for, which options matter, and the constraints you already know.

  2. Collect and compare.

    Save research notes in the project. Ask for source links, dates, and an explicit distinction between facts and assumptions.

  3. Challenge the conclusion.

    Have a reviewer inspect the sources, point out gaps, and list what would change the recommendation.

Ask to review

A short decision memo, source notes, tradeoffs, and open questions.

Research requires suitable tools and access. Check citations and freshness yourself before relying on the conclusion.

03 / Operations

Make the launch feel manageable.

Turn a moving list of details into owned tasks and reviewable drafts.

CoordinatorProducerReviewer

A brief to start from

Help prepare a launch checklist from the project brief. Group work by owner and dependency. Draft the release notes and support FAQ, then check the claims against what is actually ready. Keep everything as drafts for my review.

Example prompt · adapt it to your project

  1. Make the plan visible.

    Give tasks owners, dependencies, and review criteria. Surface unanswered questions early.

  2. Prepare the materials.

    Keep the checklist, release notes, and FAQ in the shared project so updates stay connected.

  3. Review before sharing.

    Check names, links, product claims, and unfinished items. Ask for explicit approval before external publication or sending messages.

Ask to review

An owned checklist, editable launch materials, and a clear list of decisions for you.

This example prepares drafts. Publishing and external services require the appropriate tools, access, and your authorization.

Start with something real

Your next idea deserves a team.

Choose your desktop preview, understand the setup, and give your team a clear first project.

Get Zipper Read the getting-started guide