workflow-project-intake

Requirements clarification uses structured intake to turn vague ideas into actionable plans. It asks one focused question at a time to identify goals, constraints, and success criteria, persisting the gathered context as an artifact for replayable execution.

The best way to route requirements is to use an intake skill that evaluates your input type or trigger and dispatches the context to a target workflow. It defaults to workflow-ship-faster but allows specifying a different downstream skill when ready.

Persist project context for replayable execution by saving goals and artifacts during the intake and brainstorming phase. This creates a persistent record that supports audit trails and allows downstream workflows to access the original requirements.

Yes, you can use a single-question intake process for project kickoff and discovery. It enforces a structured workflow by asking one focused question at a time to fill in missing details, ensuring requirements are captured accurately before routing.

You do not need a complete prototype to start brainstorming requirements; providing either a project idea or a repository path is sufficient. The intake process will then guide you through checkpointed write plans to clarify any missing details.

Requirements intake workflows need checkpointed write plans to enforce structured progress and prevent context loss. By checkpointing gathered information, the workflow ensures goals and constraints are safely persisted before routing to downstream execution.