# Brainstorm: [Project Name]

Use this at the start of a project or substantial feature. Fill it out directly or through an interview with an agent. Keep it lightweight: capture what you know, mark assumptions, and leave unresolved decisions as open questions. Omit sections that don't apply.

## What are you building?
_One or two sentences: what is it, who is it for, what problem does it solve, and why are you building it?_

**Project type:** [customer-facing product / personal project / internal tool / MVP / learning project / other]

## MVP Features
_What are the absolute minimum features needed for a useful first version?_

- [Must-have feature]
- [Must-have feature]

## Future Ideas (v2, v3)
_Features you might want later, but NOT in the first version. These are possibilities, not commitments._

- [Future idea]

## Out of Scope
_What are you explicitly NOT building as part of this project or feature?_

- [Explicit exclusion]

## Success and Proof
_What would make this first version successful, and how will you check? Use an observable result rather than "it works."_

- **Success looks like:** [What the user can accomplish]
- **How to verify:** [A concrete demo, test, metric, or review]

## Design & Style
_Any apps you want it to look or feel like? Include links and explain what you like about them. Note any accessibility or usability needs you already know._

- [Reference or preference]

## Tech Stack
_Optional: list preferences or existing tools. Write "Agent to recommend" if undecided. You don't need to choose a stack to finish the brainstorm; create-spec and focused research can resolve it._

- Language: [Preference / undecided]
- Framework: [Preference / undecided]
- Database: [Preference / not needed / undecided]
- Hosting: [Preference / undecided]
- Auth: [Preference / not needed / undecided]
- Already set up: [Accounts, services, or integrations — never paste secret keys]

## Other Engineering Requirements
_Any architecture constraints, deployment preferences, integrations, privacy needs, or technical considerations already known? Include relevant deadlines or budget limits._

- [Constraint or requirement]

## Existing Context
_What should the agent read or reuse? Link relevant code, docs, assets, prior attempts, or research._

- [Path or link + why it matters]

## Decisions and Assumptions
_Separate choices you've made from beliefs that still need checking. Keep this short; don't repeat every requirement._

- **Decided:** [Choice and brief reason]
- **Assumption to validate:** [Assumption and how it could affect the plan]

## Agent Autonomy Boundary
_What can the agent decide on your behalf, and what should it bring back to you? These preferences remain subject to repository instructions and tool permissions._

**Default:** Keep working until success is verified.

- **Agent can decide:** [Decisions it may make independently]
- **Discuss with me first:** [Decisions requiring your input]

## Open Questions and Next Step
_Optional: capture anything still unresolved. The agent should make a call when it has enough context and the decision falls within its autonomy boundary, research factual unknowns, or ask the user when their input is needed. Record the resolution so it carries through into implementation._

- **Open questions:** [Unresolved questions, or "None"]

**Default next step:** Build the MVP/v1 and keep working until success is verified against the Success and Proof section. Resolve blocking questions first; create a spec or do focused research as needed to support the build.

**User override (optional):** [A different next step or stopping point, such as "Only create the spec" or "Research the API options, then discuss with me"]