speccrew 0.7.45 → 0.7.46
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/.speccrew/agents/speccrew-team-leader.md +6 -6
- package/README.ar.md +5 -17
- package/README.de.md +5 -17
- package/README.en.md +5 -17
- package/README.es.md +5 -17
- package/README.fr.md +5 -17
- package/README.hi.md +384 -0
- package/README.ja.md +5 -17
- package/README.md +5 -17
- package/README.pt-BR.md +5 -17
- package/README.ru.md +5 -17
- package/docs/GETTING-STARTED.ar.md +39 -40
- package/docs/GETTING-STARTED.de.md +39 -40
- package/docs/GETTING-STARTED.en.md +39 -40
- package/docs/GETTING-STARTED.es.md +39 -40
- package/docs/GETTING-STARTED.fr.md +39 -40
- package/docs/GETTING-STARTED.hi.md +636 -0
- package/docs/GETTING-STARTED.ja.md +39 -40
- package/docs/GETTING-STARTED.md +39 -40
- package/docs/GETTING-STARTED.pt-BR.md +25 -26
- package/docs/GETTING-STARTED.ru.md +37 -38
- package/lib/commands/init.js +3 -3
- package/package.json +1 -1
- package/README.bn.md +0 -174
- package/README.bs.md +0 -394
- package/README.da.md +0 -394
- package/README.el.md +0 -174
- package/README.it.md +0 -394
- package/README.ko.md +0 -394
- package/README.no.md +0 -394
- package/README.pl.md +0 -394
- package/README.th.md +0 -311
- package/README.tr.md +0 -306
- package/README.uk.md +0 -306
- package/README.vi.md +0 -174
- package/README.zh-TW.md +0 -394
- package/docs/GETTING-STARTED.bn.md +0 -219
- package/docs/GETTING-STARTED.bs.md +0 -219
- package/docs/GETTING-STARTED.da.md +0 -637
- package/docs/GETTING-STARTED.el.md +0 -633
- package/docs/GETTING-STARTED.it.md +0 -639
- package/docs/GETTING-STARTED.ko.md +0 -639
- package/docs/GETTING-STARTED.no.md +0 -563
- package/docs/GETTING-STARTED.pl.md +0 -597
- package/docs/GETTING-STARTED.th.md +0 -219
- package/docs/GETTING-STARTED.tr.md +0 -597
- package/docs/GETTING-STARTED.uk.md +0 -597
- package/docs/GETTING-STARTED.vi.md +0 -217
- package/docs/GETTING-STARTED.zh-TW.md +0 -639
|
@@ -1,17 +1,16 @@
|
|
|
1
|
-
# SpecCrew Quick Start Guide
|
|
1
|
+
# SpecCrew Quick Start Guide
|
|
2
2
|
|
|
3
3
|
<p align="center">
|
|
4
4
|
<a href="./GETTING-STARTED.md">简体中文</a> |
|
|
5
|
-
<a href="./GETTING-STARTED.zh-TW.md">繁體中文</a> |
|
|
6
5
|
<a href="./GETTING-STARTED.en.md">English</a> |
|
|
7
|
-
<a href="./GETTING-STARTED.
|
|
8
|
-
<a href="./GETTING-STARTED.
|
|
6
|
+
<a href="./GETTING-STARTED.ja.md">日本語</a> |
|
|
7
|
+
<a href="./GETTING-STARTED.ru.md">Русский</a> |
|
|
9
8
|
<a href="./GETTING-STARTED.es.md">Español</a> |
|
|
9
|
+
<a href="./GETTING-STARTED.de.md">Deutsch</a> |
|
|
10
10
|
<a href="./GETTING-STARTED.fr.md">Français</a> |
|
|
11
|
-
<a href="./GETTING-STARTED.
|
|
12
|
-
<a href="./GETTING-STARTED.
|
|
13
|
-
<a href="./GETTING-STARTED.
|
|
14
|
-
<a href="./GETTING-STARTED.ar.md">العربية</a>
|
|
11
|
+
<a href="./GETTING-STARTED.pt-BR.md">Português (Brasil)</a> |
|
|
12
|
+
<a href="./GETTING-STARTED.ar.md">العربية</a> |
|
|
13
|
+
<a href="./GETTING-STARTED.hi.md">हिन्दी</a>
|
|
15
14
|
</p>
|
|
16
15
|
|
|
17
16
|
This document helps you quickly understand how to use SpecCrew's Agent team to complete the full development cycle from requirements to delivery following standard engineering processes.
|
|
@@ -80,22 +79,22 @@ After running `speccrew init`, follow these steps to get productive immediately:
|
|
|
80
79
|
For existing projects, initialize knowledge base first so agents understand your codebase:
|
|
81
80
|
|
|
82
81
|
```
|
|
83
|
-
|
|
82
|
+
/speccrew-team-leader Initialize technical knowledge base
|
|
84
83
|
```
|
|
85
84
|
|
|
86
85
|
Then:
|
|
87
86
|
|
|
88
87
|
```
|
|
89
|
-
|
|
88
|
+
/speccrew-team-leader Initialize business knowledge base
|
|
90
89
|
```
|
|
91
90
|
|
|
92
91
|
### Step 3: Start Your First Task
|
|
93
92
|
|
|
94
93
|
```
|
|
95
|
-
|
|
94
|
+
/speccrew-product-manager I have a new requirement: [describe your feature]
|
|
96
95
|
```
|
|
97
96
|
|
|
98
|
-
> **Tip**: If unsure what to do, just say
|
|
97
|
+
> **Tip**: If unsure what to do, just say `/speccrew-team-leader Help me get started` — the Team Leader will auto-detect your project status and guide you.
|
|
99
98
|
|
|
100
99
|
---
|
|
101
100
|
|
|
@@ -104,20 +103,20 @@ Then:
|
|
|
104
103
|
Not sure what to do? Find your scenario below:
|
|
105
104
|
|
|
106
105
|
- **I have a new feature requirement**
|
|
107
|
-
→
|
|
106
|
+
→ `/speccrew-product-manager I have a new requirement: [describe your feature]`
|
|
108
107
|
|
|
109
108
|
- **I want to scan existing project knowledge**
|
|
110
|
-
→
|
|
111
|
-
→ Then:
|
|
109
|
+
→ `/speccrew-team-leader initialize technical knowledge base`
|
|
110
|
+
→ Then: `/speccrew-team-leader initialize business knowledge base`
|
|
112
111
|
|
|
113
112
|
- **I want to continue previous work**
|
|
114
|
-
→
|
|
113
|
+
→ `/speccrew-team-leader what is the current progress?`
|
|
115
114
|
|
|
116
115
|
- **I want to check system health**
|
|
117
116
|
→ Run in terminal: `speccrew doctor`
|
|
118
117
|
|
|
119
118
|
- **I'm not sure what to do**
|
|
120
|
-
→
|
|
119
|
+
→ `/speccrew-team-leader help me get started`
|
|
121
120
|
→ Team Leader will auto-detect your project status and guide you
|
|
122
121
|
|
|
123
122
|
---
|
|
@@ -126,14 +125,14 @@ Not sure what to do? Find your scenario below:
|
|
|
126
125
|
|
|
127
126
|
| Role | Agent | Responsibilities | Example Command |
|
|
128
127
|
|------|-------|-----------------|-----------------|
|
|
129
|
-
| Team Leader |
|
|
130
|
-
| Product Manager |
|
|
131
|
-
| Feature Designer |
|
|
132
|
-
| System Designer |
|
|
133
|
-
| System Developer |
|
|
134
|
-
| Test Manager |
|
|
128
|
+
| Team Leader | `/speccrew-team-leader` | Project navigation, knowledge init, status check | "Help me get started" |
|
|
129
|
+
| Product Manager | `/speccrew-product-manager` | Requirements analysis, PRD generation | "I have a new requirement: ..." |
|
|
130
|
+
| Feature Designer | `/speccrew-feature-designer` | Feature analysis, spec design, API contracts | "Start feature design for iteration X" |
|
|
131
|
+
| System Designer | `/speccrew-system-designer` | Architecture design, platform-specific design | "Start system design for iteration X" |
|
|
132
|
+
| System Developer | `/speccrew-system-developer` | Development coordination, code generation | "Start development for iteration X" |
|
|
133
|
+
| Test Manager | `/speccrew-test-manager` | Test planning, case design, execution | "Start testing for iteration X" |
|
|
135
134
|
|
|
136
|
-
> **Note**: You don't need to remember all agents. Just talk to
|
|
135
|
+
> **Note**: You don't need to remember all agents. Just talk to `/speccrew-team-leader` and it will route your request to the right agent.
|
|
137
136
|
|
|
138
137
|
---
|
|
139
138
|
|
|
@@ -174,7 +173,7 @@ Before starting the formal engineering process, you need to initialize the proje
|
|
|
174
173
|
|
|
175
174
|
**Conversation Example**:
|
|
176
175
|
```
|
|
177
|
-
|
|
176
|
+
/speccrew-team-leader initialize technical knowledge base
|
|
178
177
|
```
|
|
179
178
|
|
|
180
179
|
**Three-Phase Process**:
|
|
@@ -196,7 +195,7 @@ speccrew-workspace/knowledges/techs/{platform-id}/
|
|
|
196
195
|
|
|
197
196
|
**Conversation Example**:
|
|
198
197
|
```
|
|
199
|
-
|
|
198
|
+
/speccrew-team-leader initialize business knowledge base
|
|
200
199
|
```
|
|
201
200
|
|
|
202
201
|
**Four-Phase Process**:
|
|
@@ -222,7 +221,7 @@ speccrew-workspace/knowledges/bizs/
|
|
|
222
221
|
|
|
223
222
|
**How to Start**:
|
|
224
223
|
```
|
|
225
|
-
|
|
224
|
+
/speccrew-product-manager I have a new requirement: [describe your requirement]
|
|
226
225
|
```
|
|
227
226
|
|
|
228
227
|
**Agent Workflow**:
|
|
@@ -249,7 +248,7 @@ iterations/{number}-{type}-{name}/01.product-requirement/
|
|
|
249
248
|
|
|
250
249
|
**How to Start**:
|
|
251
250
|
```
|
|
252
|
-
|
|
251
|
+
/speccrew-feature-designer start feature design
|
|
253
252
|
```
|
|
254
253
|
|
|
255
254
|
**Agent Workflow**:
|
|
@@ -276,7 +275,7 @@ iterations/{iter}/02.feature-design/
|
|
|
276
275
|
|
|
277
276
|
**How to Start**:
|
|
278
277
|
```
|
|
279
|
-
|
|
278
|
+
/speccrew-system-designer start system design
|
|
280
279
|
```
|
|
281
280
|
|
|
282
281
|
**Agent Workflow**:
|
|
@@ -307,7 +306,7 @@ iterations/{iter}/03.system-design/
|
|
|
307
306
|
|
|
308
307
|
**How to Start**:
|
|
309
308
|
```
|
|
310
|
-
|
|
309
|
+
/speccrew-system-developer start development
|
|
311
310
|
```
|
|
312
311
|
|
|
313
312
|
**Agent Workflow**:
|
|
@@ -338,7 +337,7 @@ iterations/{iter}/04.development/
|
|
|
338
337
|
|
|
339
338
|
**How to Start**:
|
|
340
339
|
```
|
|
341
|
-
|
|
340
|
+
/speccrew-system-deployer start deployment
|
|
342
341
|
```
|
|
343
342
|
|
|
344
343
|
**Agent Workflow**:
|
|
@@ -371,7 +370,7 @@ iterations/{iter}/05.deployment/
|
|
|
371
370
|
|
|
372
371
|
**How to Start**:
|
|
373
372
|
```
|
|
374
|
-
|
|
373
|
+
/speccrew-test-manager start testing
|
|
375
374
|
```
|
|
376
375
|
|
|
377
376
|
**Three-Phase Testing Process**:
|
|
@@ -494,7 +493,7 @@ When restarting an Agent for a phase:
|
|
|
494
493
|
View the pipeline panorama status through the Team Leader Agent:
|
|
495
494
|
|
|
496
495
|
```
|
|
497
|
-
|
|
496
|
+
/speccrew-team-leader view current iteration progress
|
|
498
497
|
```
|
|
499
498
|
|
|
500
499
|
The Team Leader will read the progress files and display a status overview similar to:
|
|
@@ -597,13 +596,13 @@ Re-initialization is required in the following situations:
|
|
|
597
596
|
|
|
598
597
|
| Phase | Agent | Start Conversation |
|
|
599
598
|
|-------|-------|-------------------|
|
|
600
|
-
| Initialization | Team Leader |
|
|
601
|
-
| Requirements Analysis | Product Manager |
|
|
602
|
-
| Feature Design | Feature Designer |
|
|
603
|
-
| System Design | System Designer |
|
|
604
|
-
| Development | System Developer |
|
|
605
|
-
| Deployment | System Deployer |
|
|
606
|
-
| System Testing | Test Manager |
|
|
599
|
+
| Initialization | Team Leader | `/speccrew-team-leader initialize technical knowledge base` |
|
|
600
|
+
| Requirements Analysis | Product Manager | `/speccrew-product-manager I have a new requirement: [description]` |
|
|
601
|
+
| Feature Design | Feature Designer | `/speccrew-feature-designer start feature design` |
|
|
602
|
+
| System Design | System Designer | `/speccrew-system-designer start system design` |
|
|
603
|
+
| Development | System Developer | `/speccrew-system-developer start development` |
|
|
604
|
+
| Deployment | System Deployer | `/speccrew-system-deployer start deployment` |
|
|
605
|
+
| System Testing | Test Manager | `/speccrew-test-manager start testing` |
|
|
607
606
|
|
|
608
607
|
### Checkpoint Checklist
|
|
609
608
|
|
|
@@ -1,17 +1,16 @@
|
|
|
1
|
-
# Guía de Inicio Rápido de SpecCrew
|
|
1
|
+
# Guía de Inicio Rápido de SpecCrew
|
|
2
2
|
|
|
3
3
|
<p align="center">
|
|
4
4
|
<a href="./GETTING-STARTED.md">简体中文</a> |
|
|
5
|
-
<a href="./GETTING-STARTED.zh-TW.md">繁體中文</a> |
|
|
6
5
|
<a href="./GETTING-STARTED.en.md">English</a> |
|
|
7
|
-
<a href="./GETTING-STARTED.
|
|
8
|
-
<a href="./GETTING-STARTED.
|
|
6
|
+
<a href="./GETTING-STARTED.ja.md">日本語</a> |
|
|
7
|
+
<a href="./GETTING-STARTED.ru.md">Русский</a> |
|
|
9
8
|
<a href="./GETTING-STARTED.es.md">Español</a> |
|
|
9
|
+
<a href="./GETTING-STARTED.de.md">Deutsch</a> |
|
|
10
10
|
<a href="./GETTING-STARTED.fr.md">Français</a> |
|
|
11
|
-
<a href="./GETTING-STARTED.
|
|
12
|
-
<a href="./GETTING-STARTED.
|
|
13
|
-
<a href="./GETTING-STARTED.
|
|
14
|
-
<a href="./GETTING-STARTED.ar.md">العربية</a>
|
|
11
|
+
<a href="./GETTING-STARTED.pt-BR.md">Português (Brasil)</a> |
|
|
12
|
+
<a href="./GETTING-STARTED.ar.md">العربية</a> |
|
|
13
|
+
<a href="./GETTING-STARTED.hi.md">हिन्दी</a>
|
|
15
14
|
</p>
|
|
16
15
|
|
|
17
16
|
Este documento le ayuda a comprender rápidamente cómo usar el equipo de Agentes de SpecCrew para completar el desarrollo completo desde los requisitos hasta la entrega siguiendo procesos de ingeniería estándar.
|
|
@@ -80,22 +79,22 @@ Después de ejecutar `speccrew init`, siga estos pasos para entrar rápidamente
|
|
|
80
79
|
Para proyectos con código fuente existente, se recomienda inicializar primero la base de conocimientos para que los agentes comprendan su base de código:
|
|
81
80
|
|
|
82
81
|
```
|
|
83
|
-
|
|
82
|
+
/speccrew-team-leader inicializar base de conocimientos técnica
|
|
84
83
|
```
|
|
85
84
|
|
|
86
85
|
Luego:
|
|
87
86
|
|
|
88
87
|
```
|
|
89
|
-
|
|
88
|
+
/speccrew-team-leader inicializar base de conocimientos de negocio
|
|
90
89
|
```
|
|
91
90
|
|
|
92
91
|
### Paso 3: Comience Su Primera Tarea
|
|
93
92
|
|
|
94
93
|
```
|
|
95
|
-
|
|
94
|
+
/speccrew-product-manager Tengo un nuevo requisito: [describa su requisito funcional]
|
|
96
95
|
```
|
|
97
96
|
|
|
98
|
-
> **Consejo**: Si no está seguro de qué hacer, simplemente diga
|
|
97
|
+
> **Consejo**: Si no está seguro de qué hacer, simplemente diga `/speccrew-team-leader ayúdame a comenzar` — el Team Leader detectará automáticamente el estado de su proyecto y lo guiará.
|
|
99
98
|
|
|
100
99
|
---
|
|
101
100
|
|
|
@@ -104,20 +103,20 @@ Luego:
|
|
|
104
103
|
¿No está seguro de qué hacer? Encuentre su escenario a continuación:
|
|
105
104
|
|
|
106
105
|
- **Tengo un nuevo requisito funcional**
|
|
107
|
-
→
|
|
106
|
+
→ `/speccrew-product-manager Tengo un nuevo requisito: [describa su requisito funcional]`
|
|
108
107
|
|
|
109
108
|
- **Quiero escanear el conocimiento del proyecto existente**
|
|
110
|
-
→
|
|
111
|
-
→ Luego:
|
|
109
|
+
→ `/speccrew-team-leader inicializar base de conocimientos técnica`
|
|
110
|
+
→ Luego: `/speccrew-team-leader inicializar base de conocimientos de negocio`
|
|
112
111
|
|
|
113
112
|
- **Quiero continuar el trabajo anterior**
|
|
114
|
-
→
|
|
113
|
+
→ `/speccrew-team-leader ¿cuál es el progreso actual?`
|
|
115
114
|
|
|
116
115
|
- **Quiero verificar el estado de salud del sistema**
|
|
117
116
|
→ Ejecutar en terminal: `speccrew doctor`
|
|
118
117
|
|
|
119
118
|
- **No estoy seguro de qué hacer**
|
|
120
|
-
→
|
|
119
|
+
→ `/speccrew-team-leader ayúdame a comenzar`
|
|
121
120
|
→ El Team Leader detectará automáticamente el estado de su proyecto y lo guiará
|
|
122
121
|
|
|
123
122
|
---
|
|
@@ -126,14 +125,14 @@ Luego:
|
|
|
126
125
|
|
|
127
126
|
| Rol | Agente | Responsabilidades | Ejemplo de Comando |
|
|
128
127
|
|------|-------|-----------------|-----------------|
|
|
129
|
-
| Líder de Equipo |
|
|
130
|
-
| Gerente de Producto |
|
|
131
|
-
| Diseñador de Funcionalidades |
|
|
132
|
-
| Diseñador de Sistema |
|
|
133
|
-
| Desarrollador de Sistema |
|
|
134
|
-
| Gerente de Pruebas |
|
|
128
|
+
| Líder de Equipo | `/speccrew-team-leader` | Navegación del proyecto, inicialización de base de conocimientos, verificación de estado | "Ayúdame a comenzar" |
|
|
129
|
+
| Gerente de Producto | `/speccrew-product-manager` | Análisis de requisitos, generación de PRD | "Tengo un nuevo requisito: ..." |
|
|
130
|
+
| Diseñador de Funcionalidades | `/speccrew-feature-designer` | Análisis funcional, diseño de especificaciones, contratos API | "Iniciar diseño de funcionalidades para iteración X" |
|
|
131
|
+
| Diseñador de Sistema | `/speccrew-system-designer` | Diseño de arquitectura, diseño detallado por plataforma | "Iniciar diseño de sistema para iteración X" |
|
|
132
|
+
| Desarrollador de Sistema | `/speccrew-system-developer` | Coordinación de desarrollo, generación de código | "Iniciar desarrollo para iteración X" |
|
|
133
|
+
| Gerente de Pruebas | `/speccrew-test-manager` | Planificación de pruebas, diseño de casos, ejecución | "Iniciar pruebas para iteración X" |
|
|
135
134
|
|
|
136
|
-
> **Nota**: No necesita recordar todos los agentes. Simplemente hable con
|
|
135
|
+
> **Nota**: No necesita recordar todos los agentes. Simplemente hable con `/speccrew-team-leader` y él enrutará su solicitud al agente correcto.
|
|
137
136
|
|
|
138
137
|
---
|
|
139
138
|
|
|
@@ -174,7 +173,7 @@ Antes de comenzar el proceso formal de ingeniería, necesita inicializar la base
|
|
|
174
173
|
|
|
175
174
|
**Ejemplo de Conversación**:
|
|
176
175
|
```
|
|
177
|
-
|
|
176
|
+
/speccrew-team-leader inicializar base de conocimientos técnica
|
|
178
177
|
```
|
|
179
178
|
|
|
180
179
|
**Proceso de Tres Fases**:
|
|
@@ -196,7 +195,7 @@ speccrew-workspace/knowledges/techs/{platform-id}/
|
|
|
196
195
|
|
|
197
196
|
**Ejemplo de Conversación**:
|
|
198
197
|
```
|
|
199
|
-
|
|
198
|
+
/speccrew-team-leader inicializar base de conocimientos de negocio
|
|
200
199
|
```
|
|
201
200
|
|
|
202
201
|
**Proceso de Cuatro Fases**:
|
|
@@ -222,7 +221,7 @@ speccrew-workspace/knowledges/bizs/
|
|
|
222
221
|
|
|
223
222
|
**Cómo Iniciar**:
|
|
224
223
|
```
|
|
225
|
-
|
|
224
|
+
/speccrew-product-manager Tengo un nuevo requisito: [describa su requisito]
|
|
226
225
|
```
|
|
227
226
|
|
|
228
227
|
**Flujo de Trabajo del Agente**:
|
|
@@ -249,7 +248,7 @@ iterations/{número}-{tipo}-{nombre}/01.product-requirement/
|
|
|
249
248
|
|
|
250
249
|
**Cómo Iniciar**:
|
|
251
250
|
```
|
|
252
|
-
|
|
251
|
+
/speccrew-feature-designer iniciar diseño de funcionalidades
|
|
253
252
|
```
|
|
254
253
|
|
|
255
254
|
**Flujo de Trabajo del Agente**:
|
|
@@ -276,7 +275,7 @@ iterations/{iter}/02.feature-design/
|
|
|
276
275
|
|
|
277
276
|
**Cómo Iniciar**:
|
|
278
277
|
```
|
|
279
|
-
|
|
278
|
+
/speccrew-system-designer iniciar diseño del sistema
|
|
280
279
|
```
|
|
281
280
|
|
|
282
281
|
**Flujo de Trabajo del Agente**:
|
|
@@ -307,7 +306,7 @@ iterations/{iter}/03.system-design/
|
|
|
307
306
|
|
|
308
307
|
**Cómo Iniciar**:
|
|
309
308
|
```
|
|
310
|
-
|
|
309
|
+
/speccrew-system-developer iniciar desarrollo
|
|
311
310
|
```
|
|
312
311
|
|
|
313
312
|
**Flujo de Trabajo del Agente**:
|
|
@@ -338,7 +337,7 @@ iterations/{iter}/04.development/
|
|
|
338
337
|
|
|
339
338
|
**Cómo Iniciar**:
|
|
340
339
|
```
|
|
341
|
-
|
|
340
|
+
/speccrew-system-deployer iniciar despliegue
|
|
342
341
|
```
|
|
343
342
|
|
|
344
343
|
**Flujo de Trabajo del Agente**:
|
|
@@ -371,7 +370,7 @@ iterations/{iter}/05.deployment/
|
|
|
371
370
|
|
|
372
371
|
**Cómo Iniciar**:
|
|
373
372
|
```
|
|
374
|
-
|
|
373
|
+
/speccrew-test-manager iniciar pruebas
|
|
375
374
|
```
|
|
376
375
|
|
|
377
376
|
**Proceso de Pruebas en Tres Fases**:
|
|
@@ -494,7 +493,7 @@ Al reiniciar un Agente para una fase:
|
|
|
494
493
|
Ver el estado panorámico del pipeline a través del Agente Team Leader:
|
|
495
494
|
|
|
496
495
|
```
|
|
497
|
-
|
|
496
|
+
/speccrew-team-leader ver progreso actual de la iteración
|
|
498
497
|
```
|
|
499
498
|
|
|
500
499
|
El Team Leader leerá los archivos de progreso y mostrará una visión general del estado similar a:
|
|
@@ -597,13 +596,13 @@ Se requiere re-inicialización en las siguientes situaciones:
|
|
|
597
596
|
|
|
598
597
|
| Fase | Agente | Conversación de Inicio |
|
|
599
598
|
|-------|-------|-------------------|
|
|
600
|
-
| Inicialización | Team Leader |
|
|
601
|
-
| Análisis de Requisitos | Product Manager |
|
|
602
|
-
| Diseño de Funcionalidades | Feature Designer |
|
|
603
|
-
| Diseño del Sistema | System Designer |
|
|
604
|
-
| Desarrollo | System Developer |
|
|
605
|
-
| Despliegue | System Deployer |
|
|
606
|
-
| Pruebas del Sistema | Test Manager |
|
|
599
|
+
| Inicialización | Team Leader | `/speccrew-team-leader inicializar base de conocimientos técnica` |
|
|
600
|
+
| Análisis de Requisitos | Product Manager | `/speccrew-product-manager Tengo un nuevo requisito: [descripción]` |
|
|
601
|
+
| Diseño de Funcionalidades | Feature Designer | `/speccrew-feature-designer iniciar diseño de funcionalidades` |
|
|
602
|
+
| Diseño del Sistema | System Designer | `/speccrew-system-designer iniciar diseño del sistema` |
|
|
603
|
+
| Desarrollo | System Developer | `/speccrew-system-developer iniciar desarrollo` |
|
|
604
|
+
| Despliegue | System Deployer | `/speccrew-system-deployer iniciar despliegue` |
|
|
605
|
+
| Pruebas del Sistema | Test Manager | `/speccrew-test-manager iniciar pruebas` |
|
|
607
606
|
|
|
608
607
|
### Lista de Verificación de Checkpoints
|
|
609
608
|
|
|
@@ -1,17 +1,16 @@
|
|
|
1
|
-
# Guide de Démarrage Rapide SpecCrew
|
|
1
|
+
# Guide de Démarrage Rapide SpecCrew
|
|
2
2
|
|
|
3
3
|
<p align="center">
|
|
4
4
|
<a href="./GETTING-STARTED.md">简体中文</a> |
|
|
5
|
-
<a href="./GETTING-STARTED.zh-TW.md">繁體中文</a> |
|
|
6
5
|
<a href="./GETTING-STARTED.en.md">English</a> |
|
|
7
|
-
<a href="./GETTING-STARTED.
|
|
8
|
-
<a href="./GETTING-STARTED.
|
|
6
|
+
<a href="./GETTING-STARTED.ja.md">日本語</a> |
|
|
7
|
+
<a href="./GETTING-STARTED.ru.md">Русский</a> |
|
|
9
8
|
<a href="./GETTING-STARTED.es.md">Español</a> |
|
|
9
|
+
<a href="./GETTING-STARTED.de.md">Deutsch</a> |
|
|
10
10
|
<a href="./GETTING-STARTED.fr.md">Français</a> |
|
|
11
|
-
<a href="./GETTING-STARTED.
|
|
12
|
-
<a href="./GETTING-STARTED.
|
|
13
|
-
<a href="./GETTING-STARTED.
|
|
14
|
-
<a href="./GETTING-STARTED.ar.md">العربية</a>
|
|
11
|
+
<a href="./GETTING-STARTED.pt-BR.md">Português (Brasil)</a> |
|
|
12
|
+
<a href="./GETTING-STARTED.ar.md">العربية</a> |
|
|
13
|
+
<a href="./GETTING-STARTED.hi.md">हिन्दी</a>
|
|
15
14
|
</p>
|
|
16
15
|
|
|
17
16
|
Ce document vous aide à comprendre rapidement comment utiliser l'équipe Agent de SpecCrew pour compléter le développement complet des exigences à la livraison selon des processus d'ingénierie standard.
|
|
@@ -80,22 +79,22 @@ Après avoir exécuté `speccrew init`, suivez ces étapes pour entrer rapidemen
|
|
|
80
79
|
Pour les projets avec du code source existant, il est recommandé d'initialiser d'abord la base de connaissances pour que les agents comprennent votre base de code :
|
|
81
80
|
|
|
82
81
|
```
|
|
83
|
-
|
|
82
|
+
/speccrew-team-leader initialiser la base de connaissances techniques
|
|
84
83
|
```
|
|
85
84
|
|
|
86
85
|
Puis :
|
|
87
86
|
|
|
88
87
|
```
|
|
89
|
-
|
|
88
|
+
/speccrew-team-leader initialiser la base de connaissances métier
|
|
90
89
|
```
|
|
91
90
|
|
|
92
91
|
### Étape 3 : Commencez Votre Première Tâche
|
|
93
92
|
|
|
94
93
|
```
|
|
95
|
-
|
|
94
|
+
/speccrew-product-manager J'ai une nouvelle exigence : [décrivez votre exigence fonctionnelle]
|
|
96
95
|
```
|
|
97
96
|
|
|
98
|
-
> **Astuce** : Si vous ne savez pas quoi faire, dites simplement
|
|
97
|
+
> **Astuce** : Si vous ne savez pas quoi faire, dites simplement `/speccrew-team-leader aidez-moi à démarrer` — le Team Leader détectera automatiquement l'état de votre projet et vous guidera.
|
|
99
98
|
|
|
100
99
|
---
|
|
101
100
|
|
|
@@ -104,20 +103,20 @@ Puis :
|
|
|
104
103
|
Vous ne savez pas quoi faire ? Trouvez votre scénario ci-dessous :
|
|
105
104
|
|
|
106
105
|
- **J'ai une nouvelle exigence fonctionnelle**
|
|
107
|
-
→
|
|
106
|
+
→ `/speccrew-product-manager J'ai une nouvelle exigence : [décrivez votre exigence fonctionnelle]`
|
|
108
107
|
|
|
109
108
|
- **Je veux scanner les connaissances du projet existant**
|
|
110
|
-
→
|
|
111
|
-
→ Puis :
|
|
109
|
+
→ `/speccrew-team-leader initialiser la base de connaissances techniques`
|
|
110
|
+
→ Puis : `/speccrew-team-leader initialiser la base de connaissances métier`
|
|
112
111
|
|
|
113
112
|
- **Je veux continuer le travail précédent**
|
|
114
|
-
→
|
|
113
|
+
→ `/speccrew-team-leader quelle est la progression actuelle ?`
|
|
115
114
|
|
|
116
115
|
- **Je veux vérifier l'état de santé du système**
|
|
117
116
|
→ Exécuter dans le terminal : `speccrew doctor`
|
|
118
117
|
|
|
119
118
|
- **Je ne sais pas quoi faire**
|
|
120
|
-
→
|
|
119
|
+
→ `/speccrew-team-leader aidez-moi à démarrer`
|
|
121
120
|
→ Le Team Leader détectera automatiquement l'état de votre projet et vous guidera
|
|
122
121
|
|
|
123
122
|
---
|
|
@@ -126,14 +125,14 @@ Vous ne savez pas quoi faire ? Trouvez votre scénario ci-dessous :
|
|
|
126
125
|
|
|
127
126
|
| Rôle | Agent | Responsabilités | Exemple de Commande |
|
|
128
127
|
|------|-------|-----------------|-----------------|
|
|
129
|
-
| Chef d'Équipe |
|
|
130
|
-
| Chef de Produit |
|
|
131
|
-
| Concepteur de Fonctionnalités |
|
|
132
|
-
| Concepteur Système |
|
|
133
|
-
| Développeur Système |
|
|
134
|
-
| Responsable Test |
|
|
128
|
+
| Chef d'Équipe | `/speccrew-team-leader` | Navigation projet, initialisation base de connaissances, vérification statut | "Aidez-moi à démarrer" |
|
|
129
|
+
| Chef de Produit | `/speccrew-product-manager` | Analyse des exigences, génération PRD | "J'ai une nouvelle exigence : ..." |
|
|
130
|
+
| Concepteur de Fonctionnalités | `/speccrew-feature-designer` | Analyse fonctionnelle, conception de spécifications, contrats API | "Démarrer la conception de fonctionnalités pour l'itération X" |
|
|
131
|
+
| Concepteur Système | `/speccrew-system-designer` | Conception d'architecture, conception détaillée par plateforme | "Démarrer la conception système pour l'itération X" |
|
|
132
|
+
| Développeur Système | `/speccrew-system-developer` | Coordination développement, génération de code | "Démarrer le développement pour l'itération X" |
|
|
133
|
+
| Responsable Test | `/speccrew-test-manager` | Planification test, conception de cas, exécution | "Démarrer les tests pour l'itération X" |
|
|
135
134
|
|
|
136
|
-
> **Note** : Vous n'avez pas besoin de mémoriser tous les agents. Parlez simplement à
|
|
135
|
+
> **Note** : Vous n'avez pas besoin de mémoriser tous les agents. Parlez simplement à `/speccrew-team-leader` et il routera votre demande vers le bon agent.
|
|
137
136
|
|
|
138
137
|
---
|
|
139
138
|
|
|
@@ -174,7 +173,7 @@ Avant de commencer le processus d'ingénierie formel, vous devez initialiser la
|
|
|
174
173
|
|
|
175
174
|
**Exemple de Conversation** :
|
|
176
175
|
```
|
|
177
|
-
|
|
176
|
+
/speccrew-team-leader initialiser la base de connaissances techniques
|
|
178
177
|
```
|
|
179
178
|
|
|
180
179
|
**Processus en Trois Phases** :
|
|
@@ -196,7 +195,7 @@ speccrew-workspace/knowledges/techs/{platform-id}/
|
|
|
196
195
|
|
|
197
196
|
**Exemple de Conversation** :
|
|
198
197
|
```
|
|
199
|
-
|
|
198
|
+
/speccrew-team-leader initialiser la base de connaissances métier
|
|
200
199
|
```
|
|
201
200
|
|
|
202
201
|
**Processus en Quatre Phases** :
|
|
@@ -222,7 +221,7 @@ speccrew-workspace/knowledges/bizs/
|
|
|
222
221
|
|
|
223
222
|
**Comment Démarrer** :
|
|
224
223
|
```
|
|
225
|
-
|
|
224
|
+
/speccrew-product-manager J'ai une nouvelle exigence : [décrivez votre exigence]
|
|
226
225
|
```
|
|
227
226
|
|
|
228
227
|
**Flux de Travail de l'Agent** :
|
|
@@ -249,7 +248,7 @@ iterations/{numéro}-{type}-{nom}/01.product-requirement/
|
|
|
249
248
|
|
|
250
249
|
**Comment Démarrer** :
|
|
251
250
|
```
|
|
252
|
-
|
|
251
|
+
/speccrew-feature-designer démarrer la conception de fonctionnalités
|
|
253
252
|
```
|
|
254
253
|
|
|
255
254
|
**Flux de Travail de l'Agent** :
|
|
@@ -276,7 +275,7 @@ iterations/{iter}/02.feature-design/
|
|
|
276
275
|
|
|
277
276
|
**Comment Démarrer** :
|
|
278
277
|
```
|
|
279
|
-
|
|
278
|
+
/speccrew-system-designer démarrer la conception système
|
|
280
279
|
```
|
|
281
280
|
|
|
282
281
|
**Flux de Travail de l'Agent** :
|
|
@@ -307,7 +306,7 @@ iterations/{iter}/03.system-design/
|
|
|
307
306
|
|
|
308
307
|
**Comment Démarrer** :
|
|
309
308
|
```
|
|
310
|
-
|
|
309
|
+
/speccrew-system-developer démarrer le développement
|
|
311
310
|
```
|
|
312
311
|
|
|
313
312
|
**Flux de Travail de l'Agent** :
|
|
@@ -338,7 +337,7 @@ iterations/{iter}/04.development/
|
|
|
338
337
|
|
|
339
338
|
**Comment Démarrer** :
|
|
340
339
|
```
|
|
341
|
-
|
|
340
|
+
/speccrew-system-deployer démarrer le déploiement
|
|
342
341
|
```
|
|
343
342
|
|
|
344
343
|
**Flux de Travail de l'Agent** :
|
|
@@ -371,7 +370,7 @@ iterations/{iter}/05.deployment/
|
|
|
371
370
|
|
|
372
371
|
**Comment Démarrer** :
|
|
373
372
|
```
|
|
374
|
-
|
|
373
|
+
/speccrew-test-manager démarrer les tests
|
|
375
374
|
```
|
|
376
375
|
|
|
377
376
|
**Processus de Test en Trois Phases** :
|
|
@@ -494,7 +493,7 @@ Lors du redémarrage d'un Agent pour une phase :
|
|
|
494
493
|
Voir le statut panoramique du pipeline via l'Agent Team Leader :
|
|
495
494
|
|
|
496
495
|
```
|
|
497
|
-
|
|
496
|
+
/speccrew-team-leader voir la progression actuelle de l'itération
|
|
498
497
|
```
|
|
499
498
|
|
|
500
499
|
Le Team Leader lira les fichiers de progression et affichera un aperçu du statut similaire à :
|
|
@@ -597,13 +596,13 @@ Une ré-initialisation est requise dans les situations suivantes :
|
|
|
597
596
|
|
|
598
597
|
| Phase | Agent | Conversation de Démarrage |
|
|
599
598
|
|-------|-------|-------------------|
|
|
600
|
-
| Initialisation | Team Leader |
|
|
601
|
-
| Analyse des Exigences | Product Manager |
|
|
602
|
-
| Feature Design | Feature Designer |
|
|
603
|
-
| Conception Système | System Designer |
|
|
604
|
-
| Développement | System Developer |
|
|
605
|
-
| Déploiement | System Deployer |
|
|
606
|
-
| Test Système | Test Manager |
|
|
599
|
+
| Initialisation | Team Leader | `/speccrew-team-leader initialiser la base de connaissances techniques` |
|
|
600
|
+
| Analyse des Exigences | Product Manager | `/speccrew-product-manager J'ai une nouvelle exigence : [description]` |
|
|
601
|
+
| Feature Design | Feature Designer | `/speccrew-feature-designer démarrer la conception de fonctionnalités` |
|
|
602
|
+
| Conception Système | System Designer | `/speccrew-system-designer démarrer la conception système` |
|
|
603
|
+
| Développement | System Developer | `/speccrew-system-developer démarrer le développement` |
|
|
604
|
+
| Déploiement | System Deployer | `/speccrew-system-deployer démarrer le déploiement` |
|
|
605
|
+
| Test Système | Test Manager | `/speccrew-test-manager démarrer les tests` |
|
|
607
606
|
|
|
608
607
|
### Liste de Vérification des Checkpoints
|
|
609
608
|
|