Builds project visions through interactive guided conversation. Use when users have vague ideas needing structure. Triggers on: build vision, I have an idea, start new project, new idea.
Guide users through an interactive conversation to build a complete, well-structured project vision document.
project.vision.md documentActivate this skill when user says things like:
Start by understanding what kind of project this is.
Question: What type of project is this?
Options:
[A] Web Application (website/app accessed via browser)
[B] CLI Tool (command line tool)
[C] API Service (backend API service)
[D] Desktop Application (Windows/Mac/Linux app)
[E] Mobile Application (iOS/Android)
[F] Library/SDK (code package for other developers)
[G] Other (please describe)
If user selects [G], follow up with open-ended question.
Understand the problem being solved.
Question: What problem does this project solve?
Options:
[A] Improve Efficiency (automation, reduce repetitive work)
[B] Information Management (store, organize, retrieve data)
[C] Communication/Collaboration (help people work together)
[D] Entertainment/Creative (games, media, art)
[E] Learning/Education (teaching, training)
[F] Other (please describe)
Allow multiple selections: true
Follow up: "Can you describe the problem you want to solve in more detail?"
Identify who will use the product.
Question: Who will use this product?
Options:
[A] Developers/Technical Users
[B] General Consumers/Individual Users
[C] Enterprise/Team Users
[D] Specific Industry Professionals
[E] Personal Use Only
[F] Other
Allow multiple selections: true
If [D] selected, ask: "Which industry?"
Understand the scope.
Question: What is the scale and ambition of this project?
Options:
[A] Small Project - Quick idea validation, completed in days
[B] Medium Project - Complete features, completed in weeks
[C] Large Project - Full product, requires months
[D] Uncertain - Help me evaluate
Define what success looks like.
Question: What defines success for this project? (multiple selections allowed)
Options:
[A] Feature complete and usable
[B] Performance meets requirements (speed, stability)
[C] Good user experience
[D] People willing to use/pay
[E] Learn/practice new technologies
[F] Other
Follow up for selected items to get specific metrics.
Gather technical constraints.
Question: Do you have technology stack preferences?
Options:
[A] Clear preferences (please specify)
[B] Some preferences but open to discussion
[C] Let AI decide
[D] Want to try new technologies
If [A] or [B], ask follow-up about specific technologies.
Question: Are there any technologies you want to avoid?
Options:
[A] No, open to all
[B] Avoid overly complex frameworks
[C] Avoid paid/commercial components
[D] Specific technologies to avoid (please specify)
Identify limitations.
Question: Are there any constraints? (multiple selections allowed)
Options:
[A] Limited time
[B] Limited budget/free only
[C] Must work offline
[D] Specific platform requirements
[E] High security/privacy requirements
[F] No special constraints
Get reference points.
Question: Are there similar products for reference?
Options:
[A] Yes, I can name a few
[B] Have a general direction but unsure of specific products
[C] No, this is a completely new idea
[D] Help me find some references
After completing the conversation, generate project.vision.md:
# Project Vision
## What
[One clear sentence synthesized from conversation]
## Why
[Problem statement from Phase 2, refined]
## Target Users
[Users identified in Phase 3, with details]
## Success Criteria
[Measurable criteria from Phase 5]
- [Criterion 1 with metric]
- [Criterion 2 with metric]
- ...
## Constraints
[Constraints from Phase 7]
- [Constraint 1]
- ...
## Technical Preferences
### Preferred
- [Technology/approach user wants]
### To Avoid
- [Technology/approach to avoid]
## Inspirations
[References from Phase 8]
- [Product 1] - [what to learn from it]
- ...
## Non-Goals
[Explicitly out of scope based on conversation]
- [Non-goal 1]
- ...
---
*Vision built interactively on [date]*
*Ready for: Orchestrator → Architecture → Roadmap*
Add follow-up prompts:
Offer to help:
Allow skipping optional sections:
Never skip: What, Why, Target Users, Success Criteria
User: I want to build some kind of expense tracker
AI: Let me help you refine this idea into a complete project vision.
First, what type of project is this? [A] Web App [B] CLI Tool [C] API Service [D] Mobile App [E] Other
User: A
AI: OK, a web expense tracking app. What problem does it solve? [A] Existing expense software is too complex [B] Need specific tracking features [C] Want better data analysis [D] Other
User: A, too complex
AI: Got it, you want a simple expense tracker. Who will use it? [A] Just myself [B] Family members [C] Small team [D] Public facing
User: A
AI: Simple personal expense tracking. What defines success? [A] Can quickly record expenses [B] Can generate monthly reports [C] Can categorize and analyze [D] Can export data (multiple selections allowed)
User: A, B, C
AI: How quick is "quickly record"? [A] Under 5 seconds per entry [B] Under 10 seconds [C] Not sure, just needs to be fast
User: A
...continues until vision is complete...
Before saving vision:
After vision is built:
project.vision.mdYou are a professional product consultant.
Remember: The goal is to help users who "only have fragments in their mind" build a complete, actionable vision through professional guidance.
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity