Does this connect to my GitHub repository?

No. The page only copies text into your browser. TogetherLens does not request a repository, token, contributor list, issue history, or portrait.

Where can I use the brief?

Paste the README block into a README, or save the issue template under .github/ISSUE_TEMPLATE in a repository you control. A public Gist is another user-controlled option.

What happens after the brief is ready?

The optional TogetherLens handoff can help make a clearly labelled group scene from permissioned portraits. The README or issue remains useful if the group stops there.

A small file with a real job

Put the photo plan
where the work lives.

A copy-ready README block and issue template for remote teams, open-source communities, and maintainers who need one clear place for the brief, opt-in, and final review.

Two homes, one brief

Keep the context
next to the work.

Use the README block for a visible project note. Use the issue template when the group needs an owner, a deadline, or a review thread. Both stay useful without a TogetherLens account.

README visible contextIssue review ownerGist public copy

PHOTO[Photo] Remote team portraitopen

✓Everyone pictured agreed to the intended use.

□Review owner and audience are clear.

□Generated image is labelled before sharing.

3 checksno private portraits in issues

Copy-ready files

Give the team
a clean handoff.

README.md

## Group photo brief

Use this block in a repository README when a remote team, community, or open-source project needs one shared photo plan. It keeps the creative brief, permission check, and review step visible without adding a service or an upload.

### The brief

- Occasion or release:
- People who opted in:
- What should feel true about the image:
- Where the final image may appear:

### Before the camera comes out

- [ ] Everyone pictured agreed to the intended use.
- [ ] Each person supplied a portrait they are allowed to share.
- [ ] The scene is labelled as AI-generated if the image is created from separate portraits.
- [ ] One person owns the final face, hand, crop, and audience review.

### Three frames to keep open

1. A clear team or group frame.
2. A relaxed in-between frame.
3. One creative frame, labelled clearly before it leaves the repo.

### Optional scene planner

[Open the free TogetherLens scene planner](https://togetherlens.app/resources/github-photo-brief/?utm_source=template&utm_medium=github&utm_campaign=github_photo_brief&utm_content=readme)

This README block is useful on its own. TogetherLens does not receive the repository, contributors, issue history, names, contacts, or images entered into it.

Paste this into a repository README, a project wiki, or a public Gist.

.github/ISSUE_TEMPLATE/photo-brief.md

---
# Save this file as .github/ISSUE_TEMPLATE/photo-brief.md on the default branch.
name: Group photo brief
about: Coordinate a permission-first group or team photo
title: "[Photo] "
labels: ""
assignees: ""
---

## What are we making?

<!-- Name the occasion, release, or team moment. Do not add private contact details. -->

## Who opted in?

<!-- List roles or handles only when your repository's privacy rules allow it. -->

- [ ] Everyone pictured agreed to the intended use.
- [ ] Every portrait can be shared for this purpose.
- [ ] The final audience and archive location are clear.

## Scene and review

- Desired feeling:
- Must-keep details:
- Review owner:
- Review deadline:

## Optional next step

Use the [free TogetherLens scene planner](https://togetherlens.app/resources/github-photo-brief/?utm_source=template&utm_medium=github&utm_campaign=github_photo_brief&utm_content=readme) only after the people pictured agree. Review the result with them before sharing it.

<!-- Keep generated images and private portraits out of public issues. -->

Save this on the default branch so contributors can choose it when opening an issue.

Optional next step

When the brief is clear,
make the scene.

TogetherLens can combine permissioned portraits into one clearly labelled, reviewable group scene. The repository files stay useful even if the group stops here.

Bring the brief into the app

Download on the App Store Get it on Google Play

No GitHub account, repository, token, contributor list, contact list, or portrait upload is requested.

Keep the contextnext to the work.

Give the teama clean handoff.

When the brief is clear,make the scene.

Keep the context
next to the work.

Give the team
a clean handoff.

When the brief is clear,
make the scene.