tlc-claude-code 0.6.0

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/verify.md ADDED
@@ -0,0 +1,159 @@
1
+ # /tlc:verify - Human Acceptance Testing
2
+
3
+ Verify the phase works as expected — with your own eyes.
4
+
5
+ ## What This Does
6
+
7
+ 1. Runs tests to confirm code works
8
+ 2. Walks you through each deliverable
9
+ 3. Captures issues for fixing
10
+ 4. Marks phase as verified when done
11
+
12
+ ## Usage
13
+
14
+ ```
15
+ /tlc:verify [phase_number]
16
+ ```
17
+
18
+ If no phase number, auto-detect current phase.
19
+
20
+ ## Process
21
+
22
+ ### Step 1: Run Tests
23
+
24
+ ```bash
25
+ npm test # or pytest, go test, etc.
26
+ ```
27
+
28
+ - ✅ All pass → Continue to human verification
29
+ - ❌ Some fail → Report failures, suggest fixing first
30
+
31
+ ### Step 2: Load Phase Deliverables
32
+
33
+ Read from `.planning/phases/{N}-PLAN.md`:
34
+ - Extract acceptance criteria from each task
35
+ - Build verification checklist
36
+
37
+ ### Step 3: Walk Through Each Deliverable
38
+
39
+ For each testable feature:
40
+
41
+ ```
42
+ Phase 1: Authentication
43
+
44
+ Verifying 3 deliverables:
45
+
46
+ [1/3] User login with email/password
47
+
48
+ Can you:
49
+ 1. Go to /login
50
+ 2. Enter valid credentials
51
+ 3. Get redirected to dashboard
52
+
53
+ Works as expected? (Y/n/describe issue)
54
+ >
55
+ ```
56
+
57
+ ### Step 4: Handle Issues
58
+
59
+ If user reports issue:
60
+ ```
61
+ > n - login works but no error message for wrong password
62
+
63
+ Got it. Creating fix task:
64
+
65
+ Issue: No error message for wrong password
66
+ Location: Login form
67
+ Expected: Show "Invalid credentials" message
68
+
69
+ Add to current phase as fix task? (Y/n)
70
+ ```
71
+
72
+ ### Step 5: Mark Verified or Loop
73
+
74
+ **All verified:**
75
+ ```
76
+ ✅ Phase 1 verified
77
+
78
+ All 3 deliverables confirmed working.
79
+
80
+ Creating .planning/phases/1-VERIFIED.md
81
+
82
+ Ready for next phase? (Y/n)
83
+ ```
84
+
85
+ **Issues found:**
86
+ ```
87
+ Phase 1 verification incomplete
88
+
89
+ Issues found:
90
+ 1. No error message for wrong password
91
+ 2. Session doesn't persist on refresh
92
+
93
+ Fix tasks added to phase. Run /tlc:build 1 to implement fixes.
94
+ ```
95
+
96
+ ### Step 6: Create Verification Record
97
+
98
+ Save to `.planning/phases/{N}-VERIFIED.md`:
99
+
100
+ ```markdown
101
+ # Phase {N}: {Name} - Verification
102
+
103
+ Verified: {date}
104
+
105
+ ## Deliverables
106
+
107
+ - [x] User login with email/password
108
+ - [x] Session persistence
109
+ - [x] Logout functionality
110
+
111
+ ## Issues Found & Fixed
112
+
113
+ - Login error message (fixed in commit abc123)
114
+ - Session refresh (fixed in commit def456)
115
+
116
+ ## Notes
117
+
118
+ {Any additional observations}
119
+ ```
120
+
121
+ ## Why Human Verification?
122
+
123
+ **Tests verify code works.**
124
+ **You verify it works the way you wanted.**
125
+
126
+ Tests catch:
127
+ - Logic errors
128
+ - Regressions
129
+ - Edge cases
130
+
131
+ You catch:
132
+ - "Technically correct but wrong layout"
133
+ - "Works but confusing UX"
134
+ - "Missing something I forgot to specify"
135
+
136
+ Both matter.
137
+
138
+ ## Example
139
+
140
+ ```
141
+ > /tlc:verify 1
142
+
143
+ Running tests... ✅ 11 passing
144
+
145
+ Phase 1: Authentication
146
+
147
+ [1/3] Login with email/password
148
+ Works? (Y/n) > y
149
+
150
+ [2/3] Session persists across page refresh
151
+ Works? (Y/n) > y
152
+
153
+ [3/3] Logout clears session
154
+ Works? (Y/n) > y
155
+
156
+ ✅ Phase 1 verified!
157
+
158
+ Moving to Phase 2: Dashboard
159
+ ```