workflow-project-intake

To clarify vague project ideas into executable requirements, use a structured questioning protocol to define goals, success criteria, non-goals, and technical switches like database and authentication needs. This process transforms abstract concepts into a structured plan.

The best way to document project intake is to persist clarified requirements and context into structured artifacts like proposal.md and context.json. This ensures traceability and provides downstream workflows with necessary implementation inputs.

Route a validated project idea to an implementation workflow by evaluating clarified requirements and technical switches. The intake process determines the most appropriate downstream workflow, such as workflow-ship-faster, based on your defined project parameters.

During project intake, define key technical requirements including database needs, billing integration, authentication methods, and deployment configurations. Also establish clear success criteria and non-goals to bound the project scope effectively.

Yes, you can use this project intake process for a new web app idea. It guides you to define what the app should do, how to measure success, and whether it needs a database or authentication before handing it off to a development workflow.

Define non-goals during project planning to prevent scope creep and ensure development workflows focus only on executable inputs. Establishing boundaries helps clarify the exact deliverables and technical switches required for successful implementation.