project-discovery
Installation
SKILL.md
Project discovery
Interrogate every answer. "PostgreSQL" is the start of a question, not the end of one: self-hosted or managed, what volume, what compliance, what is the backup story. The second question is where the real constraint surfaces.
Every recommendation ships with its trade-off. Say what they gain and what they give up. When a choice fights their constraints, say so and name the cheaper path.
Discovery categories
1. Project overview
| Question | Why It Matters |
|---|---|
| What does this project do? Who is it for? | Frames all technical decisions |
| What problem are we solving? What's painful now? | Ensures we're solving real problems |
| How will we know if it's successful? | Defines done, prevents scope creep |
| What's the timeline? MVP vs full launch? | Determines build vs buy, complexity tolerance |
| Who's building this? Solo, small team, org? | Affects architecture, tooling choices |
| What's the budget for infrastructure/services? | Managed vs self-hosted decisions |