vincent-workflows

# vincent Workflows Design the smallest reliable vincent workflow for the requested outcome. Spend agent tokens only where reasoning is part of the work; express everything else with deterministic steps and vincent's native control flow. ## Gather only decisions that matter Inspect the repository, its instructions, and existing workflows before asking questions. Infer obvious answers and state material assumptions. Ask a compact set of questions only when an answer changes the YAML, especially: - What deliverable ends the run, and which commands prove it is correct? - Which task inputs are required, optional, typed, or pattern-constrained? - Which host platforms and shells must the commands support? - Which vincent version and environment will execute the workflow, and is the locally available binary representative of that target? - Does any step publish, deploy, push, delete, spend money, mutate an external service, or otherwise become difficult to reverse? - Which choices must be known when the task is created and declared as typed task fields? - Where does a person need a binary approve/reject gate for quality or an external effect? - Must a person answer an agent during the same reasoning session, or is a between-step approval gate sufficient? - Which credentials must already be available through the daemon environment, an OS credential store, or an authenticated CLI without entering workflow data or transcripts? - Can independent work safely share one w...