@leeovery/claude-technical-workflows 2.1.28 → 2.1.29
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.
|
@@ -41,16 +41,17 @@ status: approved
|
|
|
41
41
|
**Goal**: Address findings from implementation analysis cycle {N}.
|
|
42
42
|
|
|
43
43
|
#### Tasks
|
|
44
|
-
| ID | Name | Edge Cases | Status |
|
|
45
|
-
|
|
46
|
-
| {topic}-{phase}-1 | {Task Title} | — | authored |
|
|
47
|
-
| {topic}-{phase}-2 | {Task Title} | — | authored |
|
|
44
|
+
| ID | Name | Edge Cases | Status | Ext ID |
|
|
45
|
+
|----|------|------------|--------|--------|
|
|
46
|
+
| {topic}-{phase}-1 | {Task Title} | — | authored | {ext-id} |
|
|
47
|
+
| {topic}-{phase}-2 | {Task Title} | — | authored | {ext-id} |
|
|
48
48
|
```
|
|
49
49
|
|
|
50
50
|
- Use `status: approved` for the phase (it's pre-approved by the user in the approval gate)
|
|
51
51
|
- Use `authored` for each task status (the task files are fully written)
|
|
52
52
|
- Use `—` for edge cases (analysis tasks don't have separate edge case annotations)
|
|
53
53
|
- Task IDs must match the IDs used in the created task files
|
|
54
|
+
- `Ext ID` must contain the external identifier for the task as exposed by the output format.
|
|
54
55
|
|
|
55
56
|
## Hard Rules
|
|
56
57
|
|
|
@@ -55,10 +55,10 @@ Phase {N}: {Phase Name}
|
|
|
55
55
|
|
|
56
56
|
```markdown
|
|
57
57
|
#### Tasks
|
|
58
|
-
| ID | Name | Edge Cases | Status |
|
|
59
|
-
|
|
60
|
-
| {topic}-{phase}-1 | {Task Name} | {list} | pending |
|
|
61
|
-
| {topic}-{phase}-2 | {Task Name} | {list} | pending |
|
|
58
|
+
| ID | Name | Edge Cases | Status | Ext ID |
|
|
59
|
+
|----|------|------------|--------|--------|
|
|
60
|
+
| {topic}-{phase}-1 | {Task Name} | {list} | pending | |
|
|
61
|
+
| {topic}-{phase}-2 | {Task Name} | {list} | pending | |
|
|
62
62
|
```
|
|
63
63
|
|
|
64
64
|
Use placeholder IDs in the format `{topic}-{phase}-{seq}`. The orchestrator will use the topic name from the Plan Index File.
|
package/package.json
CHANGED
|
@@ -86,7 +86,7 @@ Note that `author_gate_mode` should be updated to `auto` during the commit step
|
|
|
86
86
|
> **CHECKPOINT**: If `author_gate_mode: gated`, verify before logging: (1) You presented this exact content, (2) The user explicitly approved with `y`/`yes` or equivalent — not a question, comment, or "okay" in passing, (3) You are writing exactly what was approved with no modifications.
|
|
87
87
|
|
|
88
88
|
1. Write the task to the output format (format-specific — see authoring.md)
|
|
89
|
-
2. Update the task table in the Plan Index File: set `status: authored`
|
|
89
|
+
2. Update the task table in the Plan Index File: set `status: authored` and set `Ext ID` to the external identifier for the task as exposed by the output format.
|
|
90
90
|
3. Advance the `planning:` block in frontmatter to the next pending task (or next phase if this was the last task)
|
|
91
91
|
4. If user chose `auto` at this gate: update `author_gate_mode: auto` in the Plan Index File frontmatter
|
|
92
92
|
5. Commit: `planning({topic}): author task {task-id} ({task name})`
|