app-brief

1# App brief
2 
3Write `docs/BRIEF.md` in a folder named after the app
4(`<parent>/<AppName>/docs/BRIEF.md`; ask for the parent folder, default
5`~/Developer`). Every later skill reads it. Keep it to one page.
6 
7## 1. Name and read what exists
8 
9Pick the name first: one UpperCamelCase word (`Tasks`, `DailyLog`), not the
10name of an app already in `~/Applications`, and a bundle id
11`com.<yourname>.<appname>` in lowercase. The folder, the research, and the
12scaffold all use it.
13 
14If `docs/research/` or `docs/screens/INDEX.md` exist, read them first.
15Skip every question they already answer.
16 
17If the user gives you a spec from BAMA's `specs/` folder (a file or a
18link), it already holds the brief and the stories. Copy its **Brief** block
19to `docs/BRIEF.md` and its **Stories** block to `docs/STORIES.md`. Keep the
20rest of the spec as `docs/SPEC.md`, so later skills read its **How it
21works** and **Gotchas**. Ask only what the user wants to change, then call
22the Skill tool with `new-mac-app`.
23 
24## 2. Interview
25 
26Ask a few questions at a time. If the user asked you to decide everything,
27answer each question yourself from the research, write the choice in the
28brief, and note "decided by the agent" next to it.
29 
301. What do you do today, and which app or habit does it replace?
312. What are the three things you do most often? These become the main pages.
323. What data does it hold? Name the nouns: tasks, notes, recipes, invoices.
334. Is there a reference app you like? Then the `clone` skill comes next.
34…