poe-code 3.0.97 → 3.0.98
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -9,7 +9,13 @@ Ask the user for a one-sentence description of what they want to build.
|
|
|
9
9
|
|
|
10
10
|
## Goal
|
|
11
11
|
|
|
12
|
-
Write a YAML pipeline plan
|
|
12
|
+
Write a YAML pipeline plan. Before writing, determine where to place it:
|
|
13
|
+
|
|
14
|
+
1. If `.poe-code/pipeline/steps.yaml` exists in the **project** → write to `.poe-code/pipeline/plans/plan-<name>.yaml`
|
|
15
|
+
2. Otherwise, if `~/.poe-code/pipeline/steps.yaml` exists → write to `~/.poe-code/pipeline/plans/plan-<project>-<name>.yaml`
|
|
16
|
+
3. If neither exists, use stepless tasks and write to `~/.poe-code/pipeline/plans/plan-<project>-<name>.yaml`
|
|
17
|
+
|
|
18
|
+
Read the steps file from whichever location you found it.
|
|
13
19
|
|
|
14
20
|
## Rules
|
|
15
21
|
|
|
@@ -17,7 +23,7 @@ Write a YAML pipeline plan for `.poe-code/pipeline/plans/plan-<name>.yaml`
|
|
|
17
23
|
- Do not create tasks that depend on hidden state from previous tasks.
|
|
18
24
|
- Use short kebab-case ids.
|
|
19
25
|
- Keep titles concise and descriptive.
|
|
20
|
-
- The available steps come from
|
|
26
|
+
- The available steps come from the `steps.yaml` file you found (project or global). Use the current step names instead of inventing hardcoded ones.
|
|
21
27
|
- If no step configuration is present, use stepless tasks with scalar `status: open`.
|
|
22
28
|
- If step configuration is present, start every configured step status at `open`.
|
|
23
29
|
|
|
@@ -48,6 +54,10 @@ tasks:
|
|
|
48
54
|
review: open
|
|
49
55
|
```
|
|
50
56
|
|
|
57
|
+
## After Writing
|
|
58
|
+
|
|
59
|
+
Run `poe-code pipeline validate <path>` to check the plan is valid before running it.
|
|
60
|
+
|
|
51
61
|
## Notes
|
|
52
62
|
|
|
53
|
-
-
|
|
63
|
+
- Check `.poe-code/pipeline/steps.yaml` first, then `~/.poe-code/pipeline/steps.yaml`. Match the uncommented step names and order from whichever file you find.
|
|
@@ -2,6 +2,7 @@
|
|
|
2
2
|
# Leave it comment-only to keep the default no-step behavior.
|
|
3
3
|
# Uncomment and change the example below when you want stepped tasks.
|
|
4
4
|
# Add `mode` only when you want to override the default `yolo`.
|
|
5
|
+
# Add `agent` and/or `model` to override the pipeline-level defaults per step.
|
|
5
6
|
#
|
|
6
7
|
# steps:
|
|
7
8
|
# implement:
|
|
@@ -10,6 +11,8 @@
|
|
|
10
11
|
#
|
|
11
12
|
# Implement
|
|
12
13
|
# {{prompt}}
|
|
14
|
+
# # agent: codex
|
|
15
|
+
# # model: o3
|
|
13
16
|
#
|
|
14
17
|
# refactor:
|
|
15
18
|
# instruction: |
|