com um clique
brainstorm-project
Turn a vague idea into a concrete project with clear next steps
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Menu
Turn a vague idea into a concrete project with clear next steps
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Clone an expert by extracting their frameworks into an agent file
Create a new reusable skill from a workflow you do repeatedly
End-of-day capture of what you learned, built, and discovered
Interview the user to define who they're creating content for
Enhance a skill based on learnings from using it
Get to know the user through conversation and capture their context for later reference
| name | brainstorm-project |
| description | Turn a vague idea into a concrete project with clear next steps |
Take a half-baked idea and turn it into a real project. Works for side projects, content ideas, business ideas, or life projects (selling an apartment, planning an event).
Ask:
"What's the idea? Just dump it out — doesn't need to be organized."
Let them ramble. Then summarize:
"So if I understand right, you want to [summary]. Is that the gist?"
Ask:
"What does 'done' look like? How will you know this project is successful?"
If they're vague:
"Let's make it concrete. In 3 months, what would make you say 'that worked'?"
Ask:
"What are you working with?
- How much time can you spend on this?
- Any budget constraints?
- Any deadlines or dependencies?
- What skills/resources do you already have?"
Ask:
"What are the major chunks of work? Let's break this into phases."
Help them identify 3-5 phases or milestones:
"Here's how I'd break this down:
- [Phase 1] — [What happens]
- [Phase 2] — [What happens]
- [Phase 3] — [What happens]
Does that feel right?"
Ask:
"What's the very first thing you'd need to do to start Phase 1?"
Then:
"Can you do that this week? What day?"
Make it concrete and time-bound.
Ask:
"What might derail this? What's the most likely reason you'd give up or stall?"
Help them plan around it:
"How could you prevent that, or catch it early?"
Create a project folder in projects/:
projects/
└── [project-name]/
├── README.md # Overview, goals, phases
└── notes.md # Working notes
README.md format:
# [Project Name]
## Goal
[What does done look like?]
## Timeline
[Any deadlines or target dates]
## Phases
1. **[Phase 1]** — [Description]
2. **[Phase 2]** — [Description]
3. **[Phase 3]** — [Description]
## First Step
- [ ] [Specific action] — by [date]
## Risks
- [Risk 1] → [Mitigation]
## Notes
- [Any other context]
"Created
projects/[name]/with your project plan.Your first step: [Action] by [Date]
When you're ready to work on this, just open Claude in that folder and we can pick up where we left off."
knowledge/me/about.md if relevant