create-workflows

# Create Workflows ## Goal Create self-contained `.task.md` workflows that coordinate independent AI provider invocations through explicit files and artifacts. Treat workflow files as infrastructure: declarative, reviewable, deterministic to validate, and portable across projects that use the same workflow format. ## Authoring Workflow 1. Inspect the target project before writing. - Find existing `.task.md` workflows, configured provider aliases, and the workflow schema version if they exist. - Reuse local provider aliases exactly as configured. If none are discoverable, use clear placeholders such as `planner`, `builder`, and `reviewer` and call out that they must match the target project's config. - Keep the workflow independent of the skill location and do not reference implementation source files as required context. 2. Define the graph before writing prompts. - State the workflow goal, final deliverable, and validation gate. - Split work into nodes with explicit ownership and artifact handoff. - Add `needs` only where data or ordering is required. Independent roots should stay parallelizable. - Use upstream artifacts for handoff; do not assume providers share memory, sessions, or hidden state. - Keep each node's context bounded. Prefer concise findings, manifests, or exact file references over repeatedly inlining large upstream outputs. 3. Choose node modes conservatively. - Use `mode: sequential` as the...