wogiflow 1.0.24 → 1.0.25
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.
- package/.claude/commands/wogi-compact.md +1 -23
- package/.claude/commands/wogi-extract-review.md +175 -0
- package/.claude/commands/wogi-init.md +3 -0
- package/package.json +1 -1
- package/scripts/flow-extraction-review.js +680 -0
- package/scripts/flow-long-input.js +171 -0
- package/scripts/flow-memory-blocks.js +0 -51
- package/scripts/flow-utils.js +0 -36
- package/scripts/flow-zero-loss-extraction.js +850 -0
- package/scripts/hooks/core/session-context.js +0 -53
|
@@ -15,21 +15,6 @@ Root (overview)
|
|
|
15
15
|
└── File changes (expandable)
|
|
16
16
|
```
|
|
17
17
|
|
|
18
|
-
## CRITICAL: Task Queue Check
|
|
19
|
-
|
|
20
|
-
**Before ANY compaction**, you MUST:
|
|
21
|
-
|
|
22
|
-
1. Read `.workflow/state/ready.json`
|
|
23
|
-
2. Note pending tasks in your summary
|
|
24
|
-
3. **NEVER claim "nothing pending" without checking ready.json**
|
|
25
|
-
|
|
26
|
-
If tasks exist:
|
|
27
|
-
- **In Progress**: List task IDs currently being worked on
|
|
28
|
-
- **Ready**: Count + list task IDs awaiting work
|
|
29
|
-
- **Blocked**: Count blocked tasks
|
|
30
|
-
|
|
31
|
-
This ensures task awareness survives context compaction.
|
|
32
|
-
|
|
33
18
|
## Before Compacting
|
|
34
19
|
|
|
35
20
|
1. **Update progress.md** with:
|
|
@@ -63,12 +48,7 @@ Provide this information for the compaction system:
|
|
|
63
48
|
- [Task/change 1]
|
|
64
49
|
- [Task/change 2]
|
|
65
50
|
|
|
66
|
-
**
|
|
67
|
-
- In Progress: [task IDs or "none"]
|
|
68
|
-
- Ready: [count] tasks - [first 5 task IDs]
|
|
69
|
-
- Blocked: [count] tasks
|
|
70
|
-
|
|
71
|
-
**In Progress (Current)**:
|
|
51
|
+
**In Progress**:
|
|
72
52
|
- TASK-XXX: [description] - [current state, what's left]
|
|
73
53
|
|
|
74
54
|
**Key Decisions**:
|
|
@@ -85,8 +65,6 @@ Provide this information for the compaction system:
|
|
|
85
65
|
|
|
86
66
|
**Context to Preserve**:
|
|
87
67
|
- [Important context that should survive compaction]
|
|
88
|
-
|
|
89
|
-
**ON RESUME**: Check `.workflow/state/ready.json` for pending work.
|
|
90
68
|
```
|
|
91
69
|
|
|
92
70
|
## Context Pressure Monitoring
|
|
@@ -0,0 +1,175 @@
|
|
|
1
|
+
# /wogi-extract-review - Zero-Loss Task Extraction with Mandatory Review
|
|
2
|
+
|
|
3
|
+
Extract tasks from long input with 100% capture rate and mandatory human review.
|
|
4
|
+
|
|
5
|
+
## Purpose
|
|
6
|
+
|
|
7
|
+
When processing transcripts, meeting notes, or long prompts, this command ensures NOTHING is missed by:
|
|
8
|
+
1. Capturing EVERY distinct statement (no filtering)
|
|
9
|
+
2. Deduplicating similar items
|
|
10
|
+
3. Requiring explicit human review and confirmation
|
|
11
|
+
4. Only proceeding when user confirms the list is complete
|
|
12
|
+
|
|
13
|
+
## Philosophy
|
|
14
|
+
|
|
15
|
+
**OLD approach (lossy):** Input → Filter → Filter → Output (70-80% lost)
|
|
16
|
+
**NEW approach (zero-loss):** Input → Capture All → Dedupe → Review → Confirm → Output (100% captured)
|
|
17
|
+
|
|
18
|
+
## Usage
|
|
19
|
+
|
|
20
|
+
```bash
|
|
21
|
+
# Start zero-loss extraction
|
|
22
|
+
flow extract-zero-loss start
|
|
23
|
+
|
|
24
|
+
# Or pipe content
|
|
25
|
+
cat transcript.txt | flow extract-zero-loss start
|
|
26
|
+
|
|
27
|
+
# Check review status
|
|
28
|
+
flow extract-zero-loss status
|
|
29
|
+
|
|
30
|
+
# View items by category
|
|
31
|
+
flow extract-zero-loss show pending
|
|
32
|
+
flow extract-zero-loss show high # High confidence items
|
|
33
|
+
flow extract-zero-loss show medium # Medium confidence
|
|
34
|
+
flow extract-zero-loss show low # Low confidence
|
|
35
|
+
flow extract-zero-loss show filler # Potential filler
|
|
36
|
+
|
|
37
|
+
# Review actions
|
|
38
|
+
flow extract-zero-loss confirm <id> # Confirm as task
|
|
39
|
+
flow extract-zero-loss remove <id> "<reason>" # Remove (reason required!)
|
|
40
|
+
flow extract-zero-loss merge <src> <target> # Merge duplicate
|
|
41
|
+
|
|
42
|
+
# Bulk actions
|
|
43
|
+
flow extract-zero-loss confirm-high # Confirm all high-confidence
|
|
44
|
+
flow extract-zero-loss dismiss-filler # Dismiss filler items
|
|
45
|
+
|
|
46
|
+
# Complete review (MANDATORY before proceeding)
|
|
47
|
+
flow extract-zero-loss complete
|
|
48
|
+
|
|
49
|
+
# Get confirmed tasks
|
|
50
|
+
flow extract-zero-loss tasks
|
|
51
|
+
```
|
|
52
|
+
|
|
53
|
+
## Review Workflow
|
|
54
|
+
|
|
55
|
+
### Step 1: Start Extraction
|
|
56
|
+
```
|
|
57
|
+
flow extract-zero-loss start < transcript.txt
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
This extracts EVERYTHING from the input using multiple strategies:
|
|
61
|
+
- Sentence boundaries
|
|
62
|
+
- Line breaks
|
|
63
|
+
- Speaker changes
|
|
64
|
+
- List items (bullets, numbers)
|
|
65
|
+
- Comma-separated items with action verbs
|
|
66
|
+
|
|
67
|
+
### Step 2: Quick Review High-Confidence Items
|
|
68
|
+
```
|
|
69
|
+
flow extract-zero-loss show high
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
These items almost certainly contain tasks. Review and confirm or adjust.
|
|
73
|
+
|
|
74
|
+
### Step 3: Review Medium-Confidence Items
|
|
75
|
+
```
|
|
76
|
+
flow extract-zero-loss show medium
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
Many valid tasks here. Review carefully.
|
|
80
|
+
|
|
81
|
+
### Step 4: Review Low-Confidence Items
|
|
82
|
+
```
|
|
83
|
+
flow extract-zero-loss show low
|
|
84
|
+
```
|
|
85
|
+
|
|
86
|
+
Some may be tasks phrased informally. Don't skip!
|
|
87
|
+
|
|
88
|
+
### Step 5: Handle Filler (Optional)
|
|
89
|
+
```
|
|
90
|
+
flow extract-zero-loss dismiss-filler
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
Dismiss conversational filler like "um", "okay", "thanks".
|
|
94
|
+
|
|
95
|
+
### Step 6: Confirm Completeness (MANDATORY)
|
|
96
|
+
```
|
|
97
|
+
flow extract-zero-loss complete
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
User must explicitly confirm the task list is complete before proceeding.
|
|
101
|
+
|
|
102
|
+
## Integration with Long-Input Processing
|
|
103
|
+
|
|
104
|
+
After zero-loss extraction and review:
|
|
105
|
+
1. Confirmed tasks become the input for topic extraction
|
|
106
|
+
2. Topics are generated from the confirmed task list
|
|
107
|
+
3. Standard 4-pass processing continues
|
|
108
|
+
|
|
109
|
+
```bash
|
|
110
|
+
# Full flow
|
|
111
|
+
cat transcript.txt | flow extract-zero-loss start
|
|
112
|
+
flow extract-zero-loss confirm-high
|
|
113
|
+
# ... manual review ...
|
|
114
|
+
flow extract-zero-loss complete
|
|
115
|
+
flow long-input topics # Now uses confirmed tasks
|
|
116
|
+
flow long-input pass2
|
|
117
|
+
flow long-input pass3
|
|
118
|
+
flow long-input pass4
|
|
119
|
+
```
|
|
120
|
+
|
|
121
|
+
## Why This Matters
|
|
122
|
+
|
|
123
|
+
> "When I work with my employees, when we have a meeting, even if it takes an hour or two, when I give a task, an employee will write it down, add a comment on Figma, add it to Jira, write it down in his notebook, but nothing is getting missed."
|
|
124
|
+
|
|
125
|
+
This system ensures:
|
|
126
|
+
- **100% capture rate** - Nothing is auto-filtered
|
|
127
|
+
- **Explicit confirmation** - User reviews everything
|
|
128
|
+
- **Audit trail** - Track what was confirmed vs removed
|
|
129
|
+
- **Reason required** - Can't remove without explanation
|
|
130
|
+
|
|
131
|
+
## Confidence Levels
|
|
132
|
+
|
|
133
|
+
Items are scored (not filtered!) by confidence:
|
|
134
|
+
|
|
135
|
+
**High Confidence** - Contains explicit requirement signals:
|
|
136
|
+
- "We need to add..."
|
|
137
|
+
- "Should display..."
|
|
138
|
+
- "Must have..."
|
|
139
|
+
- "I would like..."
|
|
140
|
+
- "Change X to Y"
|
|
141
|
+
|
|
142
|
+
**Medium Confidence** - Contains softer signals:
|
|
143
|
+
- "Maybe we could..."
|
|
144
|
+
- "What if we..."
|
|
145
|
+
- "Going to need..."
|
|
146
|
+
|
|
147
|
+
**Low Confidence** - No clear signals but may be tasks:
|
|
148
|
+
- Short statements
|
|
149
|
+
- Questions
|
|
150
|
+
- Partial sentences
|
|
151
|
+
|
|
152
|
+
**Filler** - Conversational noise (still captured!):
|
|
153
|
+
- "Um", "Okay", "Thanks"
|
|
154
|
+
- "Can you hear me?"
|
|
155
|
+
- "Makes sense"
|
|
156
|
+
|
|
157
|
+
## Files
|
|
158
|
+
|
|
159
|
+
| File | Location |
|
|
160
|
+
|------|----------|
|
|
161
|
+
| Extraction module | `scripts/flow-zero-loss-extraction.js` |
|
|
162
|
+
| Review module | `scripts/flow-extraction-review.js` |
|
|
163
|
+
| Review session | `.workflow/tmp/long-input/review-session.json` |
|
|
164
|
+
|
|
165
|
+
## For Claude
|
|
166
|
+
|
|
167
|
+
When processing long transcripts:
|
|
168
|
+
|
|
169
|
+
1. **Always use zero-loss extraction** for meeting transcripts and reviews
|
|
170
|
+
2. **Present items by confidence level** to the user
|
|
171
|
+
3. **Never skip low-confidence items** - user must explicitly dismiss
|
|
172
|
+
4. **Require completeness confirmation** before proceeding to topic extraction
|
|
173
|
+
5. **Log all confirmed tasks** for audit trail
|
|
174
|
+
|
|
175
|
+
The goal is **100% task capture rate**, not 90%.
|
|
@@ -509,6 +509,9 @@ This file tracks all changes made to the project.
|
|
|
509
509
|
**Files**: .workflow/*, .claude/*
|
|
510
510
|
```
|
|
511
511
|
|
|
512
|
+
**roadmap.md** (future work):
|
|
513
|
+
Copy from `templates/roadmap.md` to `.workflow/roadmap.md`
|
|
514
|
+
|
|
512
515
|
#### 4.4 Create Spec Files
|
|
513
516
|
|
|
514
517
|
**stack.md** in `.workflow/specs/`:
|