app-brief — Claude Code skill: what it does, how to install
The app-brief skill for Claude Code and Cursor generates a one-page docs/BRIEF.md file for a new macOS app before writing code.
MIT 1,000 installs ★ 1,933 updated 2026-11-05
npx skills add daveebbelaar/bama --skill app-brief -a claude-codeWhat app-brief does
The skill activates when you have a new app idea or need to document requirements after research. The agent conducts a structured interview, picks an UpperCamelCase name, defines data models, and sets interface shapes. If a specification file or link is provided, the agent extracts the brief and user stories automatically.
The output is saved as docs/BRIEF.md inside the app directory, defaulting to ~/Developer. It strips out unnecessary features such as user accounts, team sharing, and billing for the initial version. The resulting document serves as the foundation for subsequent project generation skills.
Installation requires the skill package manager command for your specific coding assistant platform.
What it helps with
- generate a one-page app brief for a new macOS project
- conduct an interactive interview to gather app requirements
- define core data models and user interface shapes
- outline version one scope and non-functional limits
Example prompts for the agent
- Create a brief for a new menu bar notes app
- Write docs/BRIEF.md for my habit tracker idea
- Run the app brief interview for a tasks utility
How to install app-brief
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill app-brief -a claude-code2Manually: put the files in place
~/.claude/skills/app-brief/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/app-brief/
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill app-brief -a codex2Manually: put the files in place
.agents/skills/app-brief/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill app-brief -a cursor2Manually: put the files in place
.cursor/skills/app-brief/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install daveebbelaar/bama skills/start/app-brief2Manually: put the files in place
.github/skills/app-brief/SKILL.md1Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill app-brief -a gemini-cli2Platform CLI
gemini skills install https://github.com/daveebbelaar/bama --path skills/start/app-briefManually: put the files in place
.devin/skills/app-brief/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add daveebbelaar/bama --skill app-brief -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about app-brief
How to install app-brief in Claude Code?
Run npx skills add daveebbelaar/bama --skill app-brief -a claude-code and check ~/.claude/skills/app-brief/SKILL.md.
What does app-brief do?
It interviews the developer and writes a concise docs/BRIEF.md file detailing the app concept, data structures, and scope before any code is written.
Where is the generated brief stored?
The brief is saved to docs/BRIEF.md within the application folder, located by default in ~/Developer.
Source text
SKILL.md · MIT
---
name: app-brief
description: One-page brief (docs/BRIEF.md) for a new macOS app, written before any code. Use when the user has an app idea, wants to replace an app they pay for, or the research and clone skills are done.
argument-hint: "[idea in a few words]"
---
# App brief
Write `docs/BRIEF.md` in a folder named after the app
(`<parent>/<AppName>/docs/BRIEF.md`; ask for the parent folder, default
`~/Developer`). Every later skill reads it. Keep it to one page.
## 1. Name and read what exists
Pick the name first: one UpperCamelCase word (`Tasks`, `DailyLog`), not the
name of an app already in `~/Applications`, and a bundle id
`com.<yourname>.<appname>` in lowercase. The folder, the research, and the
scaffold all use it.
If `docs/research/` or `docs/screens/INDEX.md` exist, read them first.
Skip every question they already answer.
If the user gives you a spec from BAMA's `specs/` folder (a file or a
link), it already holds the brief and the stories. Copy its **Brief** block
to `docs/BRIEF.md` and its **Stories** block to `docs/STORIES.md`. Keep the
rest of the spec as `docs/SPEC.md`, so later skills read its **How it
works** and **Gotchas**. Ask only what the user wants to change, then call
the Skill tool with `new-mac-app`.
## 2. Interview
Ask a few questions at a time. If the user asked you to decide everything,
answer each question yourself from the research, write the choice in the
brief, and note "decided by the agent" next to it.
1. What do you do today, and which app or habit does it replace?
2. What are the three things you do most often? These become the main pages.
3. What data does it hold? Name the nouns: tasks, notes, recipes, invoices.
4. Is there a reference app you like? Then the `clone` skill comes next.
5. Where does it live: a window with a sidebar, a menu bar item, a
quick-capture panel with a global shortcut, or a mix?
6. Does it need the internet? Default: no.
7. Which three things are out of scope for version one?
8. Should it look like a built-in Mac app, or have its own look? Note a
brand or accent color, and any app they name ("like Things"): the
`design-from-app` skill rebuilds its look. No answer means native with
the Mac's own accent color.
## 3. Cut scope
A personal app has one user. Remove what exists only for other users:
accounts, sharing, teams, sync servers, billing, onboarding, analytics. If
the user wants data on two Macs, note "later: iCloud sync".
Version one is one afternoon of agent time: one window, two to five main
pages, one data model with two to four types. Smart lists that filter one
model (Today, Upcoming, Someday) count as one page.
## 4. Write docs/BRIEF.md
```markdown
# <AppName>
One sentence: what it is and who it is for.
## Replaces
<app or habit>
## Main jobs
1. ...
2. ...
3. ...
## Data
- <Type>: <fields>
## Shape
<sidebar window / menu bar extra / quick panel>, macOS 26 or later.
Local data. Works offline. No accounts.
## System hooks
<global shortcut, menu bar, Share menu, Shortcuts, CLI, or "none">
## Reference
<app name, or "none">
## Look
<native with an accent color (name it, or "system"), own parts, or "like <app>", and why>
## Not in version one
- ...
```
## 5. Hand off
Call the Skill tool with `user-stories`, or with `new-mac-app` if the user
wants to see a window first.
Done when `docs/BRIEF.md` exists, fits on one page, and has every section.
© daveebbelaar · MIT · daveebbelaar/bama