tlc-claude-code 1.2.12 → 1.2.14

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/claim.md CHANGED
@@ -10,6 +10,22 @@ Reserve a task so teammates know you're working on it.
10
10
 
11
11
  ## Process
12
12
 
13
+ ### Step 0: Check Team Mode
14
+
15
+ Verify team coordination is enabled:
16
+
17
+ ```bash
18
+ teamEnabled=$(jq -r '.team.enabled // false' .tlc.json 2>/dev/null)
19
+
20
+ if [ "$teamEnabled" != "true" ]; then
21
+ echo "Team coordination not enabled."
22
+ echo ""
23
+ echo "Enable it with: /tlc:deploy setup"
24
+ echo "Or add to .tlc.json: { \"team\": { \"enabled\": true } }"
25
+ exit 1
26
+ fi
27
+ ```
28
+
13
29
  ### Step 1: Identify User
14
30
 
15
31
  Get current user identity:
package/deploy.md CHANGED
@@ -88,11 +88,120 @@ Config saved to .tlc.json
88
88
 
89
89
  ### Process
90
90
 
91
- 1. **Read project info** from `.tlc.json` or `package.json`
91
+ 1. **Detect project state**:
92
+ - New project? Use info from `/tlc:new-project` or `/tlc:init`
93
+ - Existing TLC project? Read from `.tlc.json`
94
+ - Legacy project? Read from `package.json` + git remote
92
95
  2. **Ask for domain** if not configured
93
96
  3. **Generate webhook secret** (random 16 chars)
94
97
  4. **Output setup command** with all config embedded
95
- 5. **Save config** to `.tlc.json`
98
+ 5. **Save/update config** in `.tlc.json`
99
+
100
+ ### Upgrading Existing Projects
101
+
102
+ For projects already using TLC but without team features:
103
+
104
+ ```
105
+ > /tlc:deploy setup
106
+
107
+ TLC Dev Server Setup
108
+ ════════════════════════════════════════════════════════════════════
109
+
110
+ Detected existing TLC project: my-awesome-app
111
+ ✓ .tlc.json found
112
+ ✓ .planning/ directory exists
113
+ ✗ No deploy config yet
114
+
115
+ Adding team collaboration features...
116
+
117
+ Project: my-awesome-app
118
+ Repo: git@github.com:myorg/my-awesome-app.git
119
+
120
+ Enter your server domain: _
121
+ ```
122
+
123
+ The setup continues with the same flow - generates config, shows server command, DNS instructions, webhook config.
124
+
125
+ ### Enable Team Coordination
126
+
127
+ After domain setup, ask about team coordination model:
128
+
129
+ ```
130
+ ───────────────────────────────────────────────────────────────
131
+ Team Coordination
132
+ ───────────────────────────────────────────────────────────────
133
+
134
+ Enable task claiming and multi-user coordination?
135
+
136
+ This adds:
137
+ • Task markers: [ ], [>@alice], [x@bob]
138
+ • /tlc:claim - reserve a task before working
139
+ • /tlc:release - release a task if blocked
140
+ • /tlc:who - see who's working on what
141
+ • Git-based sync (push/pull shares claims)
142
+
143
+ Enable team coordination? [Y/n]: _
144
+ ```
145
+
146
+ **If Yes:**
147
+
148
+ 1. Add team config to `.tlc.json`
149
+ 2. Migrate existing PLAN.md files to add `[ ]` markers
150
+ 3. Show coordination workflow
151
+
152
+ ```
153
+ ✓ Team coordination enabled
154
+
155
+ Existing plans updated:
156
+ .planning/phases/1-PLAN.md - 3 tasks marked as available
157
+ .planning/phases/2-PLAN.md - 4 tasks marked as available
158
+
159
+ Team Workflow:
160
+ ───────────────────────────────────────────────────────────────
161
+ 1. git pull ← Get latest claims
162
+ 2. /tlc:claim ← Reserve your task
163
+ 3. git push ← Share your claim
164
+ 4. ... work on task ...
165
+ 5. git commit & push ← Task auto-marked complete
166
+ ───────────────────────────────────────────────────────────────
167
+ ```
168
+
169
+ ### Plan Migration
170
+
171
+ Existing task headings are updated:
172
+
173
+ **Before:**
174
+ ```markdown
175
+ ### Task 1: Create user schema
176
+ ### Task 2: Add validation
177
+ ```
178
+
179
+ **After:**
180
+ ```markdown
181
+ ### Task 1: Create user schema [ ]
182
+ ### Task 2: Add validation [ ]
183
+ ```
184
+
185
+ This makes tasks claimable without changing any other content.
186
+
187
+ **What gets added to .tlc.json:**
188
+
189
+ ```json
190
+ {
191
+ "project": "my-awesome-app",
192
+ "testFrameworks": { ... }, // existing config preserved
193
+ "team": { // NEW: team coordination
194
+ "enabled": true,
195
+ "model": "git-based"
196
+ },
197
+ "deploy": { // NEW: dev server
198
+ "domain": "myapp.example.com",
199
+ "webhookSecret": "x7k9m2p4q8r1s5t3",
200
+ "dashboardUrl": "https://dashboard.myapp.example.com",
201
+ "configured": false
202
+ }
203
+ }
204
+ ```
96
205
 
97
206
  ```javascript
98
207
  // Config generation
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "tlc-claude-code",
3
- "version": "1.2.12",
3
+ "version": "1.2.14",
4
4
  "description": "TLC - Test Led Coding for Claude Code",
5
5
  "bin": {
6
6
  "tlc": "./bin/tlc.js",
package/release.md CHANGED
@@ -17,6 +17,18 @@ Release a task you claimed so others can work on it.
17
17
 
18
18
  ## Process
19
19
 
20
+ ### Step 0: Check Team Mode
21
+
22
+ ```bash
23
+ teamEnabled=$(jq -r '.team.enabled // false' .tlc.json 2>/dev/null)
24
+
25
+ if [ "$teamEnabled" != "true" ]; then
26
+ echo "Team coordination not enabled."
27
+ echo "Enable it with: /tlc:deploy setup"
28
+ exit 1
29
+ fi
30
+ ```
31
+
20
32
  ### Step 1: Identify User
21
33
 
22
34
  Get current user identity (same as `/tlc:claim`):
package/tlc.md CHANGED
@@ -64,6 +64,23 @@ fi
64
64
  echo "✓ Synced"
65
65
  ```
66
66
 
67
+ ### Step 0b: Check for Team Features (Existing Projects)
68
+
69
+ For projects that existed before team features, check if dev server is configured:
70
+
71
+ ```bash
72
+ # Check if deploy config exists
73
+ deployDomain=$(jq -r '.deploy.domain // ""' .tlc.json)
74
+
75
+ if [ -z "$deployDomain" ]; then
76
+ # No deploy config - this is an existing project without team setup
77
+ # Show subtle hint in header (not blocking)
78
+ teamHint="│ 💡 Team sharing available: /tlc:deploy setup"
79
+ fi
80
+ ```
81
+
82
+ This adds a non-blocking hint. Users can also access it via Quick Actions [5].
83
+
67
84
  ### Step 1: Show Phase Checklist (ALWAYS SHOW THIS)
68
85
 
69
86
  **This is the core of `/tlc` - always show the current phase status:**
@@ -102,8 +119,9 @@ Phase 2: User Dashboard
102
119
  [2] Go back and fix skipped steps
103
120
  [3] Show all commands (/tlc:help)
104
121
  [4] Full project checklist (/tlc:checklist)
122
+ [5] Enable team collaboration (/tlc:deploy setup)
105
123
 
106
- Choice [1/2/3/4]: _
124
+ Choice [1/2/3/4/5]: _
107
125
  ```
108
126
 
109
127
  ### Step 2: Detect Current Phase
package/who.md CHANGED
@@ -10,6 +10,18 @@ See who's working on what in the current phase.
10
10
 
11
11
  ## Process
12
12
 
13
+ ### Step 0: Check Team Mode
14
+
15
+ ```bash
16
+ teamEnabled=$(jq -r '.team.enabled // false' .tlc.json 2>/dev/null)
17
+
18
+ if [ "$teamEnabled" != "true" ]; then
19
+ echo "Team coordination not enabled."
20
+ echo "Enable it with: /tlc:deploy setup"
21
+ exit 1
22
+ fi
23
+ ```
24
+
13
25
  ### Step 1: Find Current Phase
14
26
 
15
27
  1. Read `.planning/ROADMAP.md`