From 7b941c9a9a116f8a3e0f633b9f341d1cb9d5b441 Mon Sep 17 00:00:00 2001 From: Zenflow Date: Wed, 11 Mar 2026 13:15:01 -0500 Subject: [PATCH] Push from Zen --- .zenflow/tasks/new-task-cdb6/plan.md | 39 ++++++++++++++++++++++++++++ 1 file changed, 39 insertions(+) create mode 100644 .zenflow/tasks/new-task-cdb6/plan.md diff --git a/.zenflow/tasks/new-task-cdb6/plan.md b/.zenflow/tasks/new-task-cdb6/plan.md new file mode 100644 index 0000000..b7a55f4 --- /dev/null +++ b/.zenflow/tasks/new-task-cdb6/plan.md @@ -0,0 +1,39 @@ +# Auto + +## Configuration +- **Artifacts Path**: {@artifacts_path} → `.zenflow/tasks/{task_id}` + +--- + +## Agent Instructions + +Ask the user questions when anything is unclear or needs their input. This includes: +- Ambiguous or incomplete requirements +- Technical decisions that affect architecture or user experience +- Trade-offs that require business context + +Do not make assumptions on important decisions — get clarification first. + +--- + +## Workflow Steps + +### [ ] Step: Implementation + + +**Debug requests, questions, and investigations:** answer or investigate first. Do not create a plan upfront — the user needs an answer, not a plan. A plan may become relevant later once the investigation reveals what needs to change. + +**For all other tasks**, before writing any code, assess the scope of the actual change (not the prompt length — a one-sentence prompt can describe a large feature). Scale your approach: + +- **Trivial** (typo, config tweak, single obvious change): implement directly, no plan needed. +- **Small** (a few files, clear what to do): write 2–3 sentences in `plan.md` describing what and why, then implement. No substeps. +- **Medium** (multiple components, design decisions, edge cases): write a plan in `plan.md` with requirements, affected files, key decisions, verification. Break into 3–5 steps. +- **Large** (new feature, cross-cutting, unclear scope): gather requirements and write a technical spec first (`requirements.md`, `spec.md` in `{@artifacts_path}/`). Then write `plan.md` with concrete steps referencing the spec. + +**Skip planning and implement directly when** the task is trivial, or the user explicitly asks to "just do it" / gives a clear direct instruction. + +To reflect the actual purpose of the first step, you can rename it to something more relevant (e.g., Planning, Investigation). Do NOT remove meta information like comments for any step. + +Rule of thumb for step size: each step = a coherent unit of work (component, endpoint, test suite). Not too granular (single function), not too broad (entire feature). Unit tests are part of each step, not separate. + +Update `{@artifacts_path}/plan.md`.