tlc-claude-code 1.2.13 → 1.2.15
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/README.md +1 -0
- package/claim.md +16 -0
- package/deploy.md +67 -1
- package/package.json +1 -1
- package/release.md +12 -0
- package/tlc.md +60 -3
- package/who.md +12 -0
package/README.md
CHANGED
|
@@ -371,6 +371,7 @@ helm install tlc tlc/tlc-server \
|
|
|
371
371
|
|
|
372
372
|
## Documentation
|
|
373
373
|
|
|
374
|
+
- **[Getting Started Guide](docs/getting-started-guide.md)** — New to coding? Start here!
|
|
374
375
|
- **[Help / All Commands](help.md)** — Complete command reference
|
|
375
376
|
- **[Team Workflow](docs/team-workflow.md)** — Guide for teams (engineers + PO + QA)
|
|
376
377
|
- **[Dev Server](docs/devserver.md)** — Deploy on Ubuntu server
|
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
|
@@ -122,13 +122,79 @@ Enter your server domain: _
|
|
|
122
122
|
|
|
123
123
|
The setup continues with the same flow - generates config, shows server command, DNS instructions, webhook config.
|
|
124
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
|
+
|
|
125
187
|
**What gets added to .tlc.json:**
|
|
126
188
|
|
|
127
189
|
```json
|
|
128
190
|
{
|
|
129
191
|
"project": "my-awesome-app",
|
|
130
192
|
"testFrameworks": { ... }, // existing config preserved
|
|
131
|
-
"
|
|
193
|
+
"team": { // NEW: team coordination
|
|
194
|
+
"enabled": true,
|
|
195
|
+
"model": "git-based"
|
|
196
|
+
},
|
|
197
|
+
"deploy": { // NEW: dev server
|
|
132
198
|
"domain": "myapp.example.com",
|
|
133
199
|
"webhookSecret": "x7k9m2p4q8r1s5t3",
|
|
134
200
|
"dashboardUrl": "https://dashboard.myapp.example.com",
|
package/package.json
CHANGED
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,7 +64,64 @@ fi
|
|
|
64
64
|
echo "✓ Synced"
|
|
65
65
|
```
|
|
66
66
|
|
|
67
|
-
### Step 0b: Check
|
|
67
|
+
### Step 0b: Check Team Identity (First Time on Team Project)
|
|
68
|
+
|
|
69
|
+
When joining a team project (team.enabled = true), check if user is identified:
|
|
70
|
+
|
|
71
|
+
```bash
|
|
72
|
+
# Check if team mode is enabled
|
|
73
|
+
teamEnabled=$(jq -r '.team.enabled // false' .tlc.json)
|
|
74
|
+
|
|
75
|
+
if [ "$teamEnabled" = "true" ]; then
|
|
76
|
+
# Check for user identity
|
|
77
|
+
if [ -z "$TLC_USER" ]; then
|
|
78
|
+
# No TLC_USER set, prompt for identity
|
|
79
|
+
gitUser=$(git config user.name)
|
|
80
|
+
|
|
81
|
+
echo "═══════════════════════════════════════════════════════════════"
|
|
82
|
+
echo "Team Project Detected"
|
|
83
|
+
echo "═══════════════════════════════════════════════════════════════"
|
|
84
|
+
echo ""
|
|
85
|
+
echo "This project uses team coordination."
|
|
86
|
+
echo "Please identify yourself for task claiming."
|
|
87
|
+
echo ""
|
|
88
|
+
echo "Your git name: $gitUser"
|
|
89
|
+
echo ""
|
|
90
|
+
echo "Use this name? [Y/n/other]: _"
|
|
91
|
+
|
|
92
|
+
# If Y → Set TLC_USER=$gitUser (normalized)
|
|
93
|
+
# If n → Ask for name
|
|
94
|
+
# Save to shell profile: export TLC_USER="username"
|
|
95
|
+
fi
|
|
96
|
+
fi
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
**On first run, show team onboarding:**
|
|
100
|
+
|
|
101
|
+
```
|
|
102
|
+
═══════════════════════════════════════════════════════════════
|
|
103
|
+
Welcome to the Team!
|
|
104
|
+
═══════════════════════════════════════════════════════════════
|
|
105
|
+
|
|
106
|
+
Project: my-awesome-app
|
|
107
|
+
Team coordination: enabled
|
|
108
|
+
|
|
109
|
+
You'll be identified as: @alice
|
|
110
|
+
|
|
111
|
+
How it works:
|
|
112
|
+
1. /tlc:claim ← Reserve a task before working
|
|
113
|
+
2. git push ← Share your claim with team
|
|
114
|
+
3. Work on task
|
|
115
|
+
4. git commit ← Task auto-marked complete
|
|
116
|
+
|
|
117
|
+
Current team activity:
|
|
118
|
+
@bob is working on: Task 2 - Add validation
|
|
119
|
+
@carol completed: Task 1 - Create schema
|
|
120
|
+
|
|
121
|
+
Press Enter to continue...
|
|
122
|
+
```
|
|
123
|
+
|
|
124
|
+
### Step 0c: Check for Team Features (Upgrade Hint)
|
|
68
125
|
|
|
69
126
|
For projects that existed before team features, check if dev server is configured:
|
|
70
127
|
|
|
@@ -72,7 +129,7 @@ For projects that existed before team features, check if dev server is configure
|
|
|
72
129
|
# Check if deploy config exists
|
|
73
130
|
deployDomain=$(jq -r '.deploy.domain // ""' .tlc.json)
|
|
74
131
|
|
|
75
|
-
if [ -z "$deployDomain" ]; then
|
|
132
|
+
if [ -z "$deployDomain" ] && [ "$teamEnabled" != "true" ]; then
|
|
76
133
|
# No deploy config - this is an existing project without team setup
|
|
77
134
|
# Show subtle hint in header (not blocking)
|
|
78
135
|
teamHint="│ 💡 Team sharing available: /tlc:deploy setup"
|
|
@@ -119,7 +176,7 @@ Phase 2: User Dashboard
|
|
|
119
176
|
[2] Go back and fix skipped steps
|
|
120
177
|
[3] Show all commands (/tlc:help)
|
|
121
178
|
[4] Full project checklist (/tlc:checklist)
|
|
122
|
-
[5]
|
|
179
|
+
[5] Enable team collaboration (/tlc:deploy setup)
|
|
123
180
|
|
|
124
181
|
Choice [1/2/3/4/5]: _
|
|
125
182
|
```
|
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`
|