@tekyzinc/gsd-t 2.2.0 → 2.2.1
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/commands/gsd-t-discuss.md +30 -2
- package/package.json +1 -1
|
@@ -2,6 +2,22 @@
|
|
|
2
2
|
|
|
3
3
|
You are the lead agent exploring design decisions before committing to a plan. The goal of this phase is to produce or refine **contracts** — not just recommendations.
|
|
4
4
|
|
|
5
|
+
## IMPORTANT: Manual vs Auto-Invoked Behavior
|
|
6
|
+
|
|
7
|
+
**When manually invoked** (user typed `/user:gsd-t-discuss`):
|
|
8
|
+
- Focus on the user's specific topic from `$ARGUMENTS`
|
|
9
|
+
- Present analysis, options, and recommendations — do NOT auto-implement anything
|
|
10
|
+
- At the end, **STOP and wait for user input** — even in bypass/yolo mode
|
|
11
|
+
- The user wants to review and decide before proceeding
|
|
12
|
+
- Do NOT continue to the plan or execute phase
|
|
13
|
+
|
|
14
|
+
**When auto-invoked** (called by `gsd-t-wave` or another workflow command):
|
|
15
|
+
- Work through all open questions automatically
|
|
16
|
+
- Make recommendations and log decisions
|
|
17
|
+
- Continue to the next phase without stopping
|
|
18
|
+
|
|
19
|
+
**How to tell:** If `$ARGUMENTS` contains a specific topic or question, the user invoked this manually. If `$ARGUMENTS` is empty or contains only a milestone reference, it was auto-invoked by the workflow.
|
|
20
|
+
|
|
5
21
|
## Step 1: Load Context
|
|
6
22
|
|
|
7
23
|
Read in order:
|
|
@@ -13,7 +29,9 @@ Read in order:
|
|
|
13
29
|
|
|
14
30
|
## Step 2: Identify Open Questions
|
|
15
31
|
|
|
16
|
-
|
|
32
|
+
**If manually invoked with a topic:** Focus on THAT topic. The user's question/topic is the priority. You may surface related questions, but the user's topic comes first.
|
|
33
|
+
|
|
34
|
+
**If auto-invoked:** Based on the milestone and current contracts, identify what's unresolved:
|
|
17
35
|
- Architecture decisions not yet made
|
|
18
36
|
- Contract details that are vague or missing
|
|
19
37
|
- Technical approaches with multiple viable options
|
|
@@ -87,7 +105,7 @@ After all updates:
|
|
|
87
105
|
- [ ] Every domain's constraints reflect the decisions made
|
|
88
106
|
- [ ] Integration points are updated with any new dependencies
|
|
89
107
|
|
|
90
|
-
## Step 7: Report
|
|
108
|
+
## Step 7: Report and Stop
|
|
91
109
|
|
|
92
110
|
Present to the user:
|
|
93
111
|
1. Decisions made (with brief rationale)
|
|
@@ -97,4 +115,14 @@ Present to the user:
|
|
|
97
115
|
|
|
98
116
|
Update `.gsd-t/progress.md` status to `DISCUSSED`.
|
|
99
117
|
|
|
118
|
+
### If manually invoked:
|
|
119
|
+
**STOP HERE.** Do NOT proceed to the plan phase or any other phase. Present your findings and ask the user:
|
|
120
|
+
|
|
121
|
+
"Discussion complete. Here's what I found and recommend. Want to proceed with these decisions, revise anything, or explore further?"
|
|
122
|
+
|
|
123
|
+
This is mandatory — even in bypass permissions / yolo mode. The user invoked discuss to THINK, not to auto-pilot. Respect that.
|
|
124
|
+
|
|
125
|
+
### If auto-invoked (by wave):
|
|
126
|
+
The calling command will handle the transition. Just report completion and return control.
|
|
127
|
+
|
|
100
128
|
$ARGUMENTS
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@tekyzinc/gsd-t",
|
|
3
|
-
"version": "2.2.
|
|
3
|
+
"version": "2.2.1",
|
|
4
4
|
"description": "GSD-T: Contract-Driven Development for Claude Code — 27 slash commands with impact analysis, test sync, and milestone archival",
|
|
5
5
|
"author": "Tekyz, Inc.",
|
|
6
6
|
"license": "MIT",
|