Bring an idea and an AI tool. Work through a conversation at each step, review the result, and save a set of briefs you can build from. You can pause and return later.
You’ll need Node.js, Git, and an AI coding tool that supports skills. Follow the setup guide if you haven’t prepared them yet.
Use the same project folder and conversation throughout. Answer the tool’s questions, review each brief, and check that it was saved before marking the step done.
This is a common planning route. Skip a planning step if it doesn’t apply or you already have that brief. For a route tailored to your project, start with the build-an-app skill.
Your idea goes into every prompt. Leave it blank if you want help exploring.
Loading your workshop…
Next: Prepare your coding tool
Open an existing project or an empty planning folder in your coding tool. Run this command in that folder’s terminal, then follow the installer’s prompts.
npx skills add StanfordSpezi/SpeziVibe --skill '*'Before marking done: Ask your coding tool to list its SpeziVibe skills. Check that it can find build-an-app before continuing.
Clarify who needs help, the problem they face, and what a better outcome would look like.
My app idea: I am still exploring a digital health app idea; help me clarify it.
Help me define a clear need statement using the biodesign-needs-finding skill.
Guide me interactively, reuse the decisions I already shared, and wait for my answers before finalizing the brief.
When we agree on the result, save it as docs/planning/need-statement.md.Before marking done: Review the population, problem, and desired outcome. Save the agreed need statement.
Map the main user journey, onboarding, and the everyday actions your app should support.
My app idea: I am still exploring a digital health app idea; help me clarify it.
Use the digital-health-ux-planning skill to plan the user journeys and onboarding.
Read the earlier planning briefs, if available:
- docs/planning/need-statement.md
If any are missing, ask what has been decided so far. Do not assume you have read a document that was not provided.
Guide me interactively, reuse the decisions I already shared, and wait for my answers before finalizing the brief.
When we agree on the result, save it as docs/planning/ux-brief.md.Before marking done: Review how someone starts using the app and completes its main task. Save the UX brief.
Define the information your app needs, how it relates, and whether it must be shared with other systems.
My app idea: I am still exploring a digital health app idea; help me clarify it.
Use the health-data-model-planning skill to define the data entities, relationships, and interoperability needs.
Read the earlier planning briefs, if available:
- docs/planning/need-statement.md
- docs/planning/ux-brief.md
If any are missing, ask what has been decided so far. Do not assume you have read a document that was not provided.
Guide me interactively, reuse the decisions I already shared, and wait for my answers before finalizing the brief.
When we agree on the result, save it as docs/planning/data-model-brief.md.Before marking done: Review what is collected, where it comes from, and how it is connected. Save the data model brief.
Use your planned workflows and data to identify privacy, regulatory, and governance questions that need to be resolved.
My app idea: I am still exploring a digital health app idea; help me clarify it.
Use the digital-health-compliance-planning skill to identify relevant privacy and compliance questions, proposed controls, and decisions that need expert review.
Read the earlier planning briefs, if available:
- docs/planning/need-statement.md
- docs/planning/ux-brief.md
- docs/planning/data-model-brief.md
If any are missing, ask what has been decided so far. Do not assume you have read a document that was not provided.
Guide me interactively, reuse the decisions I already shared, and wait for my answers before finalizing the brief.
When we agree on the result, save it as docs/planning/compliance-brief.md.Before marking done: Review the proposed controls, unresolved questions, and who needs to resolve them. Save the compliance brief.
Bring your decisions together into small milestones, tasks, and checks your coding agent can work through.
My app idea: I am still exploring a digital health app idea; help me clarify it.
Use the app-build-planner skill to create a milestone-based implementation plan with tasks and verification criteria. Flag missing planning inputs and unresolved decisions instead of inventing them. Keep an undecided platform explicit.
Read the earlier planning briefs, if available:
- docs/planning/need-statement.md
- docs/planning/ux-brief.md
- docs/planning/data-model-brief.md
- docs/planning/compliance-brief.md
If any are missing, ask what has been decided so far. Do not assume you have read a document that was not provided.
Also ask about any additional study, FHIR, or EHR integration briefs and incorporate those if available.
Guide me interactively, reuse the decisions I already shared, and wait for my answers before finalizing the brief.
When we agree on the result, save it as docs/implementation-plan.md.Before marking done: Review the first milestone, its verification criteria, and the open questions. Save the implementation plan.