saranskumar Goal
Convert a broad request into build-ready implementation requirements.
When to Use
- The request is broad and spans several engineering concerns.
- The stack or runtime is not yet explicit.
- The next step is routing into specialist skills, not ideation.
Instructions
- Restate the request as a build problem, not a startup idea.
- Extract purpose, likely features, runtime needs, data needs, security needs, environment needs, and integration needs.
- Identify which specialist skills should handle the next steps.
- Flag assumptions and unknowns explicitly.
Constraints
- Do not expand into product brainstorming.
- Do not create multiple competing visions.
- Keep the output implementation-oriented.
Output Format
- purpose
- likely functionality
- runtime and environment assumptions
- data and auth needs
- security concerns
- specialist skill handoff plan
Examples
- "Build a dashboard app with auth and background jobs."
- "Create a Python service for report generation."