App Plan
Start a new app build with a structured interview that turns vague ideas into scoped features, stack choices, and a documentation folder plan.
Overview
app-plan is an agent skill most often used in Validate (also Idea research, Build pm) that interviews you about app features and derives tech stack plus documentation structure.
Install
npx skills add https://github.com/vibewithaisy/app-plan-skill --skill SKILL.mdWhat is this skill?
- Interview-driven scoping triggered by phrases like new project start, app plan, or doc structure setup
- Feature-first questions before deep implementation choices
- Derives recommended tech stack from functional answers
- Outputs a documentation structure tailored to the planned app
- Bilingual-friendly triggers including Korean and English planning intents
- 3 output pillars: features, tech stack, documentation structure
Adoption & trust: 40 GitHub stars.
What problem does it solve?
You want to build an app but only have a fuzzy idea—no ordered feature list, stack, or docs layout for your agent to follow.
Who is it for?
Solo builders kicking off mobile or web apps who want a guided planning interview before repo scaffolding.
Skip if: Projects with an approved PRD and fixed architecture, or when you only need a single UI component without product scope.
When should I use this skill?
When the user says they want to build an app, start a new project, plan an app, set up doc structure, or uses phrases like 'app plan' or '프로젝트 세팅'.
What do I get? / Deliverables
You end with scoped features, a suggested tech stack, and a doc structure ready for prototyping or implementation planning.
- Scoped feature list from interview
- Recommended tech stack
- Proposed documentation directory structure
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Validate/scope is the first hard gate where features, constraints, and doc structure must exist before full implementation. Scope subphase matches feature-centric questioning and tech-stack derivation before prototype or landing work.
Where it fits
Clarify core user jobs and must-have features before committing to a stack.
Run the interview when you say you want to start an app project or need a doc structure.
Reuse the derived doc tree as the backbone for specs and implementation tasks.
Hand interview answers to a thin prototype plan with known libraries and modules.
How it compares
Use instead of unstructured chat brainstorming when you need stack and folder structure—not just feature ideas.
Common Questions / FAQ
Who is app-plan for?
Indie developers beginning an app build who need feature scoping, stack guidance, and documentation layout from a structured Q&A.
When should I use app-plan?
At idea-to-validate transition when you say you are starting a project, want an app plan, or need doc structure; also early in build pm when specs are still fluid.
Is app-plan safe to install?
Review Prism’s Security Audits panel; the skill is conversational planning and should not require secrets—still verify the skill package before use.
SKILL.md
READMESKILL.md - App Plan
앱 빌딩 프로젝트를 시작할 때 기획을 구체화하는 인터뷰 스킬. 사용자가 만들고 싶은 앱에 대해 기능 중심으로 질문하고, 그 답변을 기반으로 필요한 기술 스택과 문서 구조를 도출한다. '앱 만들려고', '새 프로젝트 시작', '앱 기획', 'app plan', '문서 구조 잡아줘', '프로젝트 세팅' 같은 말이 나오면 트리거한다. # app-plan { "name": "app-plan", "description": "앱 빌딩 프로젝트를 시작할 때 기획을 구체화하는 인터뷰 스킬. 사용자가 만들고 싶은 앱에 대해 기능 중심으로 질문하고, 그 답변을 기반으로 필요한 기술 스택과 문서 구조를 도출한다. '앱 만들려고', '새 프로젝트 시작', '앱 기획', 'app plan', '문서 구조 잡아줘', '프로젝트 세팅' 같은 말이 나오면 트리거한다." }