← ClaudeAtlas

plan-applisted

Plan an application before any code is written. Interviews the user one question at a time about their idea, pushes back on vague answers, then writes the project's context files (project-overview, architecture, ui-context, code-standards, ai-workflow-rules, progress-tracker), an entry-point file (CLAUDE.md or AGENTS.md), and an ordered build plan. Use this whenever the user has an app idea, says "I want to build...", "help me plan my app", "start a new project", "set up my context files", "write my CLAUDE.md / AGENTS.md", or asks to begin coding a new app that has no context/ folder yet. Trigger even if the user asks to jump straight to code on a brand-new project; planning comes first.
SrunLyheang/AI-Builder-Playbook · ★ 0 · AI & Automation · score 72
Install: claude install-skill SrunLyheang/AI-Builder-Playbook
# Plan App Turn a rough app idea into a set of context files and a build plan that a coding agent can execute without guessing. The reason this skill exists: an agent fills every gap in a plan with an assumption, and those assumptions compound until the result looks nothing like what the user had in mind. The fix is to close the gaps before the first line of code, through a conversation, and then write the answers down where every future session will read them. This skill is the first of three: 1. `plan-app` (this one): interview, context files, build plan 2. `spec-unit`: writes the spec file for one unit of the build plan 3. `build-unit`: implements one unit from its spec ## Ground rules - **Write no application code.** Do not scaffold, install packages, or create source files. The only files this skill creates are Markdown files inside `context/` and the entry-point file at the project root. If the user asks to start coding mid-interview, tell them what is still undecided and what the agent would have to guess; let them choose. - **One question at a time.** A wall of questions gets shallow answers. Ask one, listen, follow up, then move on. - **The user decides, you challenge.** Never silently pick a stack, a feature, or a scope cut. Offer options, recommend, and let them choose. - **Record only what was decided.** Anything the user did not decide goes into Open Questions, never into a context file as if it were settled. ## Step 0: Orient Before asking