speccrew 0.1.11 → 0.2.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/.speccrew/agents/speccrew-feature-designer.md +120 -0
- package/.speccrew/agents/speccrew-product-manager.md +54 -0
- package/.speccrew/agents/speccrew-system-designer.md +163 -25
- package/.speccrew/agents/speccrew-system-developer.md +357 -52
- package/.speccrew/agents/speccrew-task-worker.md +43 -0
- package/.speccrew/agents/speccrew-team-leader.md +108 -11
- package/.speccrew/agents/speccrew-test-manager.md +285 -9
- package/.speccrew/skills/speccrew-dev-backend/SKILL.md +47 -1
- package/.speccrew/skills/speccrew-dev-desktop/SKILL.md +51 -6
- package/.speccrew/skills/speccrew-dev-frontend/SKILL.md +49 -3
- package/.speccrew/skills/speccrew-dev-mobile/SKILL.md +50 -5
- package/.speccrew/skills/speccrew-fd-api-contract/SKILL.md +70 -0
- package/.speccrew/skills/speccrew-fd-feature-design/SKILL.md +158 -0
- package/.speccrew/skills/speccrew-pm-requirement-analysis/SKILL.md +65 -0
- package/.speccrew/skills/speccrew-sd-backend/SKILL.md +38 -0
- package/.speccrew/skills/speccrew-sd-desktop/SKILL.md +38 -0
- package/.speccrew/skills/speccrew-sd-frontend/SKILL.md +38 -0
- package/.speccrew/skills/speccrew-sd-mobile/SKILL.md +38 -0
- package/.speccrew/skills/speccrew-test-case-design/SKILL.md +33 -0
- package/.speccrew/skills/speccrew-test-code-gen/SKILL.md +34 -0
- package/.speccrew/skills/speccrew-test-execute/SKILL.md +34 -0
- package/README.ar.md +70 -3
- package/README.bn.md +52 -0
- package/README.bs.md +70 -3
- package/README.da.md +70 -3
- package/README.de.md +70 -3
- package/README.el.md +52 -0
- package/README.en.md +69 -2
- package/README.es.md +70 -3
- package/README.fr.md +70 -3
- package/README.it.md +70 -3
- package/README.ja.md +70 -3
- package/README.ko.md +70 -3
- package/README.md +69 -2
- package/README.no.md +70 -3
- package/README.pl.md +70 -3
- package/README.pt-BR.md +70 -3
- package/README.ru.md +70 -3
- package/README.th.md +69 -2
- package/README.tr.md +69 -2
- package/README.uk.md +69 -2
- package/README.vi.md +52 -0
- package/README.zh-TW.md +70 -3
- package/docs/GETTING-STARTED.ar.md +78 -4
- package/docs/GETTING-STARTED.bn.md +78 -4
- package/docs/GETTING-STARTED.bs.md +78 -4
- package/docs/GETTING-STARTED.da.md +78 -4
- package/docs/GETTING-STARTED.de.md +78 -4
- package/docs/GETTING-STARTED.el.md +78 -4
- package/docs/GETTING-STARTED.en.md +78 -4
- package/docs/GETTING-STARTED.es.md +78 -4
- package/docs/GETTING-STARTED.fr.md +78 -4
- package/docs/GETTING-STARTED.it.md +78 -4
- package/docs/GETTING-STARTED.ja.md +79 -5
- package/docs/GETTING-STARTED.ko.md +79 -5
- package/docs/GETTING-STARTED.md +78 -4
- package/docs/GETTING-STARTED.no.md +78 -4
- package/docs/GETTING-STARTED.pl.md +78 -4
- package/docs/GETTING-STARTED.pt-BR.md +78 -4
- package/docs/GETTING-STARTED.ru.md +78 -4
- package/docs/GETTING-STARTED.th.md +79 -5
- package/docs/GETTING-STARTED.tr.md +78 -4
- package/docs/GETTING-STARTED.uk.md +78 -4
- package/docs/GETTING-STARTED.vi.md +79 -5
- package/docs/GETTING-STARTED.zh-TW.md +79 -5
- package/package.json +1 -1
- package/.speccrew/skills/speccrew-create-agents/SKILL.md +0 -98
- package/.speccrew/skills/speccrew-create-agents/templates/agents/designer-agent.md +0 -54
- package/.speccrew/skills/speccrew-create-agents/templates/agents/dev-agent.md +0 -79
- package/.speccrew/skills/speccrew-create-agents/templates/agents/test-agent.md +0 -80
- package/.speccrew/skills/speccrew-project-diagnosis/SKILL.md +0 -233
- package/.speccrew/skills/speccrew-project-diagnosis/templates/DIAGNOSIS-REPORT-TEMPLATE.md +0 -202
- package/.speccrew/skills/speccrew-workflow-diagnose/SKILL.md +0 -155
- package/workspace-template/docs/solutions/Agent/346/212/200/350/203/275/345/256/232/344/271/211+/351/234/200/346/261/202/346/226/207/346/241/243+UML/344/275/277/347/224/250/346/250/241/346/235/277/357/274/210ISA-95/345/205/255/346/256/265/345/274/217/350/236/215/345/220/210/347/211/210/357/274/211.md +0 -586
- package/workspace-template/docs/solutions/harness.md +0 -410
package/README.no.md
CHANGED
|
@@ -41,6 +41,58 @@ Ved å integrere Agenter og Skills i eksisterende prosjekter, kan team raskt ini
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ Nøkkelfunksjoner
|
|
45
|
+
|
|
46
|
+
### 🏭 Virtuelt Programvareteam
|
|
47
|
+
Ett-klikks generering av **7 profesjonelle Agent-roller** + **30+ Skill-arbeidsflyter**, bygging av et komplett virtuelt programvareteam:
|
|
48
|
+
- **Team Leader** - Global planlegging og iterasjonshåndtering
|
|
49
|
+
- **Product Manager** - Kravanalyse og PRD-utdata
|
|
50
|
+
- **Feature Designer** - Funksjonsdesign + API-kontrakter
|
|
51
|
+
- **System Designer** - Systemdesign for Frontend/Backend/Mobil/Desktop
|
|
52
|
+
- **System Developer** - Multiplattform parallellutvikling
|
|
53
|
+
- **Test Manager** - Trefaset testkoordinering
|
|
54
|
+
- **Task Worker** - Parallell underoppgaveutførelse
|
|
55
|
+
|
|
56
|
+
### 📐 ISA-95 Sekstrinns Modellering
|
|
57
|
+
Basert på internasjonal **ISA-95** modelleringsmetodikk, standardisering av transformasjonen fra forretningskrav til programvaresystemer:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- Hvert trinn tilsvarer spesifikke UML-diagrammer (use case, sekvens, klassediagrammer)
|
|
64
|
+
- Forretningskrav "foredles trinn for trinn" uten informasjonstap
|
|
65
|
+
- Uttak er direkte brukbar for utvikling
|
|
66
|
+
|
|
67
|
+
### 📚 Kunnskapsbasesystem
|
|
68
|
+
Trenivå kunnskapsbasearkitektur som sikrer at AI alltid jobber basert på "den eneste sannhetskilden":
|
|
69
|
+
|
|
70
|
+
| Nivå | Katalog | Innhold | Formål |
|
|
71
|
+
|------|---------|---------|--------|
|
|
72
|
+
| L1 Systemkunnskap | `knowledge/techs/` | Tech-stack, arkitektur, konvensjoner | AI forstår prosjektets tekniske grenser |
|
|
73
|
+
| L2 Forretningskunnskap | `knowledge/bizs/` | Modulfunksjoner, forretningsflyter, enheter | AI forstår forretningslogikk |
|
|
74
|
+
| L3 Iterasjonsartefakter | `iterations/iXXX/` | PRD, designdokumenter, testrapporter | Full sporbarhetskjede for gjeldende krav |
|
|
75
|
+
|
|
76
|
+
### 🔄 Firetrinns Kunnskapspipeline
|
|
77
|
+
**Automatisert kunnskapsproduksjonsarkitektur**, automatisk generering av forretnings/teknisk dokumentasjon fra kildekode:
|
|
78
|
+
```
|
|
79
|
+
Trinn 1: Skann kildekode → Generer modulliste
|
|
80
|
+
Trinn 2: Parallell analyse → Trekk ut funksjoner (multi-Worker parallelt)
|
|
81
|
+
Trinn 3: Parallell oppsummering → Fullfør moduloversikter (multi-Worker parallelt)
|
|
82
|
+
Trinn 4: Systemaggregering → Generer systempanorama
|
|
83
|
+
```
|
|
84
|
+
- Støtter **full synkronisering** og **inkrementell synkronisering** (basert på Git diff)
|
|
85
|
+
- En person optimaliserer, team deler
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness Praktisk Implementeringsrammeverk
|
|
88
|
+
**Standardisert utførelsesrammeverk**, sikrer at designdokumenter presist transformeres til kjørbare utviklingsinstruksjoner:
|
|
89
|
+
- **Driftshåndbok-prinsipp**: Skill er SOP, trinn er klare, sammenhengende og selvstendige
|
|
90
|
+
- **Inn- og utdatakontrakt**: Tydelig definerte grensesnitt, utføres like strengt som pseudokode
|
|
91
|
+
- **Progressiv avsløringsarkitektur**: Informasjon lastes lagvis, unngår engangskontekst-overbelastning
|
|
92
|
+
- **Sub-Agent-delegering**: Komplekse oppgaver deles automatisk, parallell utførelse sikrer kvalitet
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## 8 Kjerne-problemer Løst
|
|
45
97
|
|
|
46
98
|
### 1. AI Ignorerer Eksisterende Prosjektdokumentasjon (Kunnskapshull)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
Etter initialisering vil følgende bli generert i prosjektet ditt:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — 7 Agent-rolledefinisjoner
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` —
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — 30+ Skill-arbeidsflyter
|
|
193
245
|
- `speccrew-workspace/` — Arbeidsområde (iterasjonskataloger, kunnskapsbase, dokumentmaler)
|
|
194
246
|
- `.speccrewrc` — SpecCrew-konfigurasjonsfil
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ Følg standard ingeniørarbeidsflyt trinn for trinn:
|
|
|
213
265
|
|
|
214
266
|
> Hver fases leveranser krever menneskelig bekreftelse før fortsettelse til neste fase.
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. Oppdater SpecCrew
|
|
269
|
+
|
|
270
|
+
Når en ny versjon av SpecCrew slippes, fullfør oppdateringen i to trinn:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **Merk**: `npm install -g speccrew@latest` oppdaterer selve CLI-verktøyet, mens `speccrew update` oppdaterer Agent- og Skill-definisjonsfilene i prosjektet ditt. Begge trinnene er nødvendige for en fullstendig oppdatering.
|
|
282
|
+
|
|
283
|
+
### 5. Andre CLI-kommandoer
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # List opp installerte agenter og skills
|
|
@@ -239,7 +306,7 @@ your-project/
|
|
|
239
306
|
│ │ ├── speccrew-system-developer.md # System Utvikler: Parallell utvikling per plattform
|
|
240
307
|
│ │ ├── speccrew-test-manager.md # Testleder: Trefase-testkoordinering
|
|
241
308
|
│ │ └── speccrew-task-worker.md # Oppgave-arbeider: Parallell underoppgave-utførelse
|
|
242
|
-
│ └── skills/ #
|
|
309
|
+
│ └── skills/ # 30+ Skills (gruppert etter funksjon)
|
|
243
310
|
│ ├── speccrew-pm-*/ # Produktstyring (kravanalyse, evaluering)
|
|
244
311
|
│ ├── speccrew-fd-*/ # Feature Design (Feature Design, API Kontrakt)
|
|
245
312
|
│ ├── speccrew-sd-*/ # System Design (frontend/backend/mobil/desktop)
|
package/README.pl.md
CHANGED
|
@@ -41,6 +41,58 @@ Poprzez integrację Agentów i Skilli z istniejącymi projektami, zespoły mogą
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ Kluczowe Cechy
|
|
45
|
+
|
|
46
|
+
### 🏭 Wirtualny Zespół Software'owy
|
|
47
|
+
Jednoklikowe generowanie **7 profesjonalnych ról Agentów** + **30+ workflowów Skilli**, budowanie kompletnego wirtualnego zespołu software'owego:
|
|
48
|
+
- **Team Leader** - Globalne planowanie i zarządzanie iteracjami
|
|
49
|
+
- **Product Manager** - Analiza wymagań i generowanie PRD
|
|
50
|
+
- **Feature Designer** - Projektowanie funkcji + kontrakty API
|
|
51
|
+
- **System Designer** - Projektowanie systemów Frontend/Backend/Mobilny/Desktop
|
|
52
|
+
- **System Developer** - Równoległy rozwój multiplatformowy
|
|
53
|
+
- **Test Manager** - Koordynacja testów w trzech fazach
|
|
54
|
+
- **Task Worker** - Równoległe wykonywanie podzadań
|
|
55
|
+
|
|
56
|
+
### 📐 Modelowanie ISA-95 Sześciostopniowe
|
|
57
|
+
Oparte na międzynarodowej metodyce modelowania **ISA-95**, standaryzacja transformacji wymagań biznesowych w systemy software'owe:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- Każdy stopień odpowiada określonym diagramom UML (przypadki użycia, sekwencje, diagramy klas)
|
|
64
|
+
- Wymagania biznesowe są "udokładniane krok po kroku", bez utraty informacji
|
|
65
|
+
- Wyniki są bezpośrednio użyteczne do rozwoju
|
|
66
|
+
|
|
67
|
+
### 📚 System Bazy Wiedzy
|
|
68
|
+
Trójpoziomowa architektura bazy wiedzy zapewniająca, że AI zawsze pracuje w oparciu o "pojedyncze źródło prawdy":
|
|
69
|
+
|
|
70
|
+
| Poziom | Katalog | Zawartość | Cel |
|
|
71
|
+
|--------|---------|-----------|------|
|
|
72
|
+
| L1 Wiedza Systemowa | `knowledge/techs/` | Stack technologiczny, architektura, konwencje | AI rozumie granice techniczne projektu |
|
|
73
|
+
| L2 Wiedza Biznesowa | `knowledge/bizs/` | Funkcje modułów, przepływy biznesowe, encje | AI rozumie logikę biznesową |
|
|
74
|
+
| L3 Artefakty Iteracji | `iterations/iXXX/` | PRD, dokumenty projektowe, raporty testowe | Pełny łańcuch śledzenia dla bieżących wymagań |
|
|
75
|
+
|
|
76
|
+
### 🔄 Czterostopniowy Pipeline Wiedzy
|
|
77
|
+
**Zautomatyzowana architektura generowania wiedzy**, automatyczne generowanie dokumentacji biznesowej/technicznej z kodu źródłowego:
|
|
78
|
+
```
|
|
79
|
+
Stopień 1: Skanowanie kodu źródłowego → Generowanie listy modułów
|
|
80
|
+
Stopień 2: Analiza równoległa → Ekstrakcja funkcji (wielu Workerów równolegle)
|
|
81
|
+
Stopień 3: Podsumowanie równoległe → Uzupełnienie przeglądów modułów (wielu Workerów równolegle)
|
|
82
|
+
Stopień 4: Agregacja systemu → Generowanie panoramy systemu
|
|
83
|
+
```
|
|
84
|
+
- Obsługuje **pełną synchronizację** i **synchronizację inkrementalną** (opartą na Git diff)
|
|
85
|
+
- Jedna osoba optymalizuje, zespół dzieli się
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness Praktyczne Ramy Wdrożeniowe
|
|
88
|
+
**Zestandaryzowane ramy wykonawcze**, zapewniające precyzyjną transformację dokumentów projektowych w wykonywalne instrukcje deweloperskie:
|
|
89
|
+
- **Zasada podręcznika operacyjnego**: Skill to SOP, kroki są jasne, ciągłe i samowystarczalne
|
|
90
|
+
- **Kontrakt wejścia-wyjścia**: Jasno zdefiniowane interfejsy, wykonywane tak rygorystycznie jak pseudokod
|
|
91
|
+
- **Architektura progresywnego ujawniania**: Informacje ładowane warstwowo, unikanie jednorazowego przeciążenia kontekstu
|
|
92
|
+
- **Delegowanie sub-Agentów**: Złożone zadania automatycznie podzielone, równoległe wykonanie zapewnia jakość
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## 8 Rozwiązanych Problemów Rdzeniowych
|
|
45
97
|
|
|
46
98
|
### 1. AI Ignoruje Istniejącą Dokumentację Projektu (Luka Wiedzy)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
Po inicjalizacji w projekcie zostaną wygenerowane:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — 7 definicji ról Agentów
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` —
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — 30+ workflow Skilli
|
|
193
245
|
- `speccrew-workspace/` — Przestrzeń robocza (katalogi iteracji, baza wiedzy, szablony dokumentów)
|
|
194
246
|
- `.speccrewrc` — Plik konfiguracyjny SpecCrew
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ Podążaj za standardowym workflow inżynieryjnym krok po kroku:
|
|
|
213
265
|
|
|
214
266
|
> Deliverable każdej fazy wymaga ludzkiego potwierdzenia przed przejściem do następnej fazy.
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. Zaktualizuj SpecCrew
|
|
269
|
+
|
|
270
|
+
Gdy zostanie wydana nowa wersja SpecCrew, ukończ aktualizację w dwóch krokach:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **Uwaga**: `npm install -g speccrew@latest` aktualizuje samo narzędzie CLI, podczas gdy `speccrew update` aktualizuje pliki definicji Agentów i Skilli w Twoim projekcie. Oba kroki są wymagane dla pełnej aktualizacji.
|
|
282
|
+
|
|
283
|
+
### 5. Inne Komendy CLI
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # Wylistuj zainstalowane agenty i skille
|
|
@@ -239,7 +306,7 @@ your-project/
|
|
|
239
306
|
│ │ ├── speccrew-system-developer.md # System Developer: Równoległy rozwój według platformy
|
|
240
307
|
│ │ ├── speccrew-test-manager.md # Test Manager: Koordynacja testów trójfazowych
|
|
241
308
|
│ │ └── speccrew-task-worker.md # Task Worker: Równoległa egzekucja podzadań
|
|
242
|
-
│ └── skills/ #
|
|
309
|
+
│ └── skills/ # 30+ Skilli (zgrupowane według funkcji)
|
|
243
310
|
│ ├── speccrew-pm-*/ # Zarządzanie Produktem (analiza wymagań, ewaluacja)
|
|
244
311
|
│ ├── speccrew-fd-*/ # Feature Design (Feature Design, Kontrakt API)
|
|
245
312
|
│ ├── speccrew-sd-*/ # System Design (frontend/backend/mobile/desktop)
|
package/README.pt-BR.md
CHANGED
|
@@ -41,6 +41,58 @@ Ao integrar Agents e Skills em projetos existentes, as equipes podem inicializar
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ Destaques Principais
|
|
45
|
+
|
|
46
|
+
### 🏭 Equipe de Software Virtual
|
|
47
|
+
Geração com um clique de **7 papéis de Agentes profissionais** + **30+ fluxos de trabalho de Skills**, construindo uma equipe de software virtual completa:
|
|
48
|
+
- **Team Leader** - Planejamento global e gerenciamento de iterações
|
|
49
|
+
- **Product Manager** - Análise de requisitos e geração de PRD
|
|
50
|
+
- **Feature Designer** - Design de funcionalidades + contratos API
|
|
51
|
+
- **System Designer** - Design de sistemas Frontend/Backend/Mobile/Desktop
|
|
52
|
+
- **System Developer** - Desenvolvimento paralelo multiplataforma
|
|
53
|
+
- **Test Manager** - Coordenação de testes em três fases
|
|
54
|
+
- **Task Worker** - Execução paralela de subtarefas
|
|
55
|
+
|
|
56
|
+
### 📐 Modelagem ISA-95 de Seis Estágios
|
|
57
|
+
Baseado na metodologia de modelagem internacional **ISA-95**, padronizando a transformação de requisitos de negócio em sistemas de software:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- Cada estágio corresponde a diagramas UML específicos (casos de uso, sequência, classes)
|
|
64
|
+
- Requisitos de negócio são "refinados passo a passo", sem perda de informação
|
|
65
|
+
- Saídas são diretamente utilizáveis para desenvolvimento
|
|
66
|
+
|
|
67
|
+
### 📚 Sistema de Base de Conhecimento
|
|
68
|
+
Arquitetura de base de conhecimento de três níveis garantindo que a IA sempre trabalhe baseada na "fonte única da verdade":
|
|
69
|
+
|
|
70
|
+
| Nível | Diretório | Conteúdo | Propósito |
|
|
71
|
+
|-------|-----------|----------|-----------|
|
|
72
|
+
| L1 Conhecimento do Sistema | `knowledge/techs/` | Stack tecnológico, arquitetura, convenções | IA entende limites técnicos do projeto |
|
|
73
|
+
| L2 Conhecimento de Negócio | `knowledge/bizs/` | Funcionalidades de módulos, fluxos de negócio, entidades | IA entende lógica de negócio |
|
|
74
|
+
| L3 Artefatos de Iteração | `iterations/iXXX/` | PRD, documentos de design, relatórios de teste | Cadeia completa de rastreabilidade para requisitos atuais |
|
|
75
|
+
|
|
76
|
+
### 🔄 Pipeline de Conhecimento de Quatro Estágios
|
|
77
|
+
**Arquitetura de geração automatizada de conhecimento**, geração automática de documentação de negócio/técnica a partir do código-fonte:
|
|
78
|
+
```
|
|
79
|
+
Estágio 1: Escanear código-fonte → Gerar lista de módulos
|
|
80
|
+
Estágio 2: Análise paralela → Extrair funcionalidades (multi-Worker paralelo)
|
|
81
|
+
Estágio 3: Resumo paralelo → Completar visões gerais de módulos (multi-Worker paralelo)
|
|
82
|
+
Estágio 4: Agregação do sistema → Gerar panorama do sistema
|
|
83
|
+
```
|
|
84
|
+
- Suporta **sincronização completa** e **sincronização incremental** (baseado em Git diff)
|
|
85
|
+
- Uma pessoa otimiza, equipe compartilha
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness Framework de Implementação Prática
|
|
88
|
+
**Framework de execução padronizado**, garantindo que documentos de design sejam transformados com precisão em instruções de desenvolvimento executáveis:
|
|
89
|
+
- **Princípio do manual de operações**: Skill é SOP, etapas são claras, contínuas e autossuficientes
|
|
90
|
+
- **Contrato de entrada-saída**: Interfaces claramente definidas, executadas com o rigor de pseudocódigo
|
|
91
|
+
- **Arquitetura de revelação progressiva**: Informações carregadas em camadas, evitando sobrecarga de contexto única
|
|
92
|
+
- **Delegação de sub-Agent**: Tarefas complexas divididas automaticamente, execução paralela garante qualidade
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## 8 Problemas Principais Resolvidos
|
|
45
97
|
|
|
46
98
|
### 1. IA Ignora Documentação de Projeto Existente (Lacuna de Conhecimento)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
Após a inicialização, os seguintes itens serão gerados no projeto:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — 7 definições de papéis de Agent
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` —
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — 30+ fluxos de trabalho de Skill
|
|
193
245
|
- `speccrew-workspace/` — Espaço de trabalho (diretórios de iteração, base de conhecimento, templates de documentos)
|
|
194
246
|
- `.speccrewrc` — Arquivo de configuração do SpecCrew
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ Siga o fluxo de trabalho de engenharia padrão passo a passo:
|
|
|
213
265
|
|
|
214
266
|
> Os entregáveis de cada fase requerem confirmação humana antes de prosseguir para a próxima fase.
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. Atualizar SpecCrew
|
|
269
|
+
|
|
270
|
+
Quando uma nova versão do SpecCrew for lançada, complete a atualização em duas etapas:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **Nota**: `npm install -g speccrew@latest` atualiza a própria ferramenta CLI, enquanto `speccrew update` atualiza os arquivos de definição de Agent e Skill no seu projeto. Ambas as etapas são necessárias para uma atualização completa.
|
|
282
|
+
|
|
283
|
+
### 5. Outros Comandos CLI
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # Listar agents e skills instalados
|
|
@@ -239,7 +306,7 @@ your-project/
|
|
|
239
306
|
│ │ ├── speccrew-system-developer.md # System Developer: Desenvolvimento paralelo por plataforma
|
|
240
307
|
│ │ ├── speccrew-test-manager.md # Test Manager: Coordenação de testes em três fases
|
|
241
308
|
│ │ └── speccrew-task-worker.md # Task Worker: Execução paralela de subtarefas
|
|
242
|
-
│ └── skills/ #
|
|
309
|
+
│ └── skills/ # 30+ Skills (agrupadas por função)
|
|
243
310
|
│ ├── speccrew-pm-*/ # Gestão de Produto (análise de requisitos, avaliação)
|
|
244
311
|
│ ├── speccrew-fd-*/ # Feature Design (Feature Design, Contrato API)
|
|
245
312
|
│ ├── speccrew-sd-*/ # System Design (frontend/backend/mobile/desktop)
|
package/README.ru.md
CHANGED
|
@@ -41,6 +41,58 @@ SpecCrew — это встраиваемый фреймворк виртуаль
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ Ключевые особенности
|
|
45
|
+
|
|
46
|
+
### 🏭 Виртуальная команда разработки
|
|
47
|
+
Генерация в один клик **7 профессиональных ролей Агентов** + **30+ рабочих процессов Навыков**, создание полной виртуальной команды разработки:
|
|
48
|
+
- **Team Leader** - Глобальное планирование и управление итерациями
|
|
49
|
+
- **Product Manager** - Анализ требований и генерация PRD
|
|
50
|
+
- **Feature Designer** - Проектирование функций + API-контракты
|
|
51
|
+
- **System Designer** - Проектирование систем Frontend/Backend/Mobile/Desktop
|
|
52
|
+
- **System Developer** - Многоплатформенная параллельная разработка
|
|
53
|
+
- **Test Manager** - Координация тестирования в три этапа
|
|
54
|
+
- **Task Worker** - Параллельное выполнение подзадач
|
|
55
|
+
|
|
56
|
+
### 📐 Моделирование ISA-95 в шесть этапов
|
|
57
|
+
Основано на международной методологии моделирования **ISA-95**, стандартизация преобразования бизнес-требований в программные системы:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- Каждый этап соответствует определенным UML-диаграммам (use case, sequence, class diagrams)
|
|
64
|
+
- Бизнес-требования "уточняются поэтапно", без потери информации
|
|
65
|
+
- Результаты непосредственно пригодны для разработки
|
|
66
|
+
|
|
67
|
+
### 📚 Система базы знаний
|
|
68
|
+
Трехуровневая архитектура базы знаний, гарантирующая, что ИИ всегда работает на основе "единого источника истины":
|
|
69
|
+
|
|
70
|
+
| Уровень | Каталог | Содержимое | Назначение |
|
|
71
|
+
|---------|---------|-----------|------------|
|
|
72
|
+
| L1 Системные знания | `knowledge/techs/` | Технологический стек, архитектура, соглашения | ИИ понимает технические границы проекта |
|
|
73
|
+
| L2 Бизнес-знания | `knowledge/bizs/` | Функции модулей, бизнес-процессы, сущности | ИИ понимает бизнес-логику |
|
|
74
|
+
| L3 Артефакты итераций | `iterations/iXXX/` | PRD, проектные документы, отчеты о тестировании | Полная цепочка отслеживания для текущих требований |
|
|
75
|
+
|
|
76
|
+
### 🔄 Четырехэтапный конвейер знаний
|
|
77
|
+
**Автоматизированная архитектура генерации знаний**, автоматическая генерация бизнес/технической документации из исходного кода:
|
|
78
|
+
```
|
|
79
|
+
Этап 1: Сканирование исходного кода → Генерация списка модулей
|
|
80
|
+
Этап 2: Параллельный анализ → Извлечение функций (много Worker параллельно)
|
|
81
|
+
Этап 3: Параллельное обобщение → Завершение обзоров модулей (много Worker параллельно)
|
|
82
|
+
Этап 4: Системная агрегация → Генерация панорамы системы
|
|
83
|
+
```
|
|
84
|
+
- Поддерживает **полную синхронизацию** и **инкрементальную синхронизацию** (на основе Git diff)
|
|
85
|
+
- Один оптимизирует, команда использует
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness Практическая структура внедрения
|
|
88
|
+
**Стандартизированная структура исполнения**, обеспечивающая точное преобразование проектных документов в выполнимые инструкции по разработке:
|
|
89
|
+
- **Принцип операционного руководства**: Skill — это СОП, шаги чёткие, последовательные и самодостаточные
|
|
90
|
+
- **Контракт входа-выхода**: Чётко определённые интерфейсы, выполняемые так же строго, как псевдокод
|
|
91
|
+
- **Архитектура прогрессивного раскрытия**: Информация загружается по слоям, избегая разовой перегрузки контекста
|
|
92
|
+
- **Делегирование суб-Агентов**: Сложные задачи автоматически разделяются, параллельное выполнение обеспечивает качество
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## Решение 8 ключевых проблем
|
|
45
97
|
|
|
46
98
|
### 1. ИИ игнорирует существующую документацию проекта (разрыв знаний)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
После инициализации в проекте будут созданы:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — 7 определений ролей Агентов
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` —
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — 30+ рабочих процессов Навыков
|
|
193
245
|
- `speccrew-workspace/` — Рабочее пространство (каталоги итераций, база знаний, шаблоны документов)
|
|
194
246
|
- `.speccrewrc` — Файл конфигурации SpecCrew
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ speccrew update --ide claude
|
|
|
213
265
|
|
|
214
266
|
> Результаты каждой фазы требуют человеческого подтверждения перед переходом к следующей фазе.
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. Обновить SpecCrew
|
|
269
|
+
|
|
270
|
+
Когда выходит новая версия SpecCrew, выполните обновление в два шага:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **Примечание**: `npm install -g speccrew@latest` обновляет сам инструмент CLI, а `speccrew update` обновляет файлы определений Агентов и Навыков в вашем проекте. Для полного обновления необходимы оба шага.
|
|
282
|
+
|
|
283
|
+
### 5. Другие команды CLI
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # Список установленных агентов и навыков
|
|
@@ -239,7 +306,7 @@ your-project/
|
|
|
239
306
|
│ │ ├── speccrew-system-developer.md # System Developer: Параллельная разработка по платформам
|
|
240
307
|
│ │ ├── speccrew-test-manager.md # Test Manager: Координация трёхфазного тестирования
|
|
241
308
|
│ │ └── speccrew-task-worker.md # Task Worker: Параллельное выполнение подзадач
|
|
242
|
-
│ └── skills/ #
|
|
309
|
+
│ └── skills/ # 30+ Навыков (сгруппированных по функциям)
|
|
243
310
|
│ ├── speccrew-pm-*/ # Управление продуктом (анализ требований, оценка)
|
|
244
311
|
│ ├── speccrew-fd-*/ # Feature Design (Feature Design, API контракт)
|
|
245
312
|
│ ├── speccrew-sd-*/ # System Design (frontend/backend/mobile/desktop)
|
package/README.th.md
CHANGED
|
@@ -41,6 +41,58 @@ SpecCrew เป็นเฟรมเวิร์กทีมพัฒนา AI
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ จุดเด่นหลัก
|
|
45
|
+
|
|
46
|
+
### 🏭 ทีมซอฟต์แวร์เสมือน
|
|
47
|
+
การสร้างด้วยคลิกเดียว **7 บทบาท Agent มืออาชีพ** + **30+ เวิร์กโฟลว์ Skill** สร้างทีมซอฟต์แวร์เสมือนที่สมบูรณ์:
|
|
48
|
+
- **Team Leader** - การวางแผนระดับโลกและการจัดการการทำซ้ำ
|
|
49
|
+
- **Product Manager** - การวิเคราะห์ความต้องการและผลลัพธ์ PRD
|
|
50
|
+
- **Feature Designer** - การออกแบบฟีเจอร์ + สัญญา API
|
|
51
|
+
- **System Designer** - การออกแบบระบบ Frontend/Backend/Mobile/Desktop
|
|
52
|
+
- **System Developer** - การพัฒนาขนานข้ามแพลตฟอร์ม
|
|
53
|
+
- **Test Manager** - การประสานการทดสอบสามขั้นตอน
|
|
54
|
+
- **Task Worker** - การทำงานย่อยขนานกัน
|
|
55
|
+
|
|
56
|
+
### 📐 การสร้างแบบจำลอง ISA-95 หกขั้นตอน
|
|
57
|
+
อิงตามวิธีการสร้างแบบจำลองมาตรฐานสากล **ISA-95** การ стандарти化การแปลงความต้องการทางธุรกิจเป็นระบบซอฟต์แวร์:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- แต่ละขั้นตอนสอดคล้องกับแผนภาพ UML เฉพาะ (use case, sequence, class)
|
|
64
|
+
- ความต้องการทางธุรกิจ "ถูกกลั่นกรองทีละขั้นตอน" โดยไม่สูญเสียข้อมูล
|
|
65
|
+
- ผลลัพธ์สามารถนำไปใช้ในการพัฒนาได้โดยตรง
|
|
66
|
+
|
|
67
|
+
### 📚 ระบบฐานความรู้
|
|
68
|
+
สถาปัตยกรรมฐานความรู้สามชั้นที่รับรองว่า AI ทำงานอิงตาม "แหล่งความจริงเดียว" เสมอ:
|
|
69
|
+
|
|
70
|
+
| ชั้น | ไดเรกทอรี | เนื้อหา | วัตถุประสงค์ |
|
|
71
|
+
|------|-----------|---------|-------------|
|
|
72
|
+
| L1 ความรู้ระบบ | `knowledge/techs/` | Stack เทคโนโลยี, สถาปัตยกรรม, ข้อตกลง | AI เข้าใจขอบเขตทางเทคนิคของโปรเจกต์ |
|
|
73
|
+
| L2 ความรู้ธุรกิจ | `knowledge/bizs/` | ฟังก์ชันโมดูล, การไหลทางธุรกิจ, เอนทิตี | AI เข้าใจตรรกะทางธุรกิจ |
|
|
74
|
+
| L3 สิ่งซ้ำการทำซ้ำ | `iterations/iXXX/` | PRD, เอกสารการออกแบบ, รายงานการทดสอบ | โซ่การติดตามที่สมบูรณ์สำหรับความต้องการปัจจุบัน |
|
|
75
|
+
|
|
76
|
+
### 🔄 ไปป์ไลน์ความรู้สี่ขั้นตอน
|
|
77
|
+
**สถาปัตยกรรมการสร้างความรู้โดยอัตโนมัติ** การสร้างเอกสารธุรกิจ/เทคนิคโดยอัตโนมัติจากรหัสต้นฉบับ:
|
|
78
|
+
```
|
|
79
|
+
ขั้นตอนที่ 1: สแกนรหัสต้นฉบับ → สร้างรายการโมดูล
|
|
80
|
+
ขั้นตอนที่ 2: การวิเคราะห์ขนาน → สกัดฟีเจอร์ (multi-Worker ขนาน)
|
|
81
|
+
ขั้นตอนที่ 3: การสรุปขนาน → ทำให้ภาพรวมโมดูลสมบูรณ์ (multi-Worker ขนาน)
|
|
82
|
+
ขั้นตอนที่ 4: การรวมระบบ → สร้างภาพพาโนรามาของระบบ
|
|
83
|
+
```
|
|
84
|
+
- รองรับ **การซิงค์แบบเต็ม** และ **การซิงค์แบบเพิ่ม** (อิงตาม Git diff)
|
|
85
|
+
- คนเดียวปรับปรุง ทีมแชร์
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness กรอบการลงมือปฏิบัติจริง
|
|
88
|
+
**กรอบการดำเนินการมาตรฐาน** เพื่อให้แน่ใจว่าเอกสารการออกแบบถูกแปลงเป็นคำสั่งพัฒนาที่ปฏิบัติได้อย่างแม่นยำ:
|
|
89
|
+
- **หลักคู่มือการดำเนินการ**: Skill คือ SOP ขั้นตอนชัดเจน ต่อเนื่อง และครบถ้วนในตัวเอง
|
|
90
|
+
- **สัญญาอินพุต-เอาต์พุต**: กำหนดอินเทอร์เฟซชัดเจน ปฏิบัติอย่างเคร่งครัดเหมือน pseudocode
|
|
91
|
+
- **สถาปัตยกรรมการเปิดเผยแบบก้าวหน้า**: โหลดข้อมูลแบบเลเยอร์ หลีกเลี่ยงการโหลดบริบทมากเกินไปในครั้งเดียว
|
|
92
|
+
- **การมอบหมาย Sub-Agent**: แยกงานอัตโนมัติสำหรับงานที่ซับซ้อน ดำเนินการแบบขนานเพื่อรับประกันคุณภาพ
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## แก้ปัญหาหลัก 8 ประการ
|
|
45
97
|
|
|
46
98
|
### 1. AI เพิกเฉยต่อเอกสารโปรเจกต์ที่มีอยู่ (ช่องว่างความรู้)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
หลังจากการเริ่มต้น สิ่งต่อไปนี้จะถูกสร้างในโปรเจกต์ของคุณ:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — นิยามบทบาท Agent 7 ตัว
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — เวิร์กโฟลว์ Skill
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — เวิร์กโฟลว์ Skill 30+ ตัว
|
|
193
245
|
- `speccrew-workspace/` — พื้นที่ทำงาน (ไดเรกทอรีวนซ้ำ, ฐานความรู้, เทมเพลตเอกสาร)
|
|
194
246
|
- `.speccrewrc` — ไฟล์การกำหนดค่า SpecCrew
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ speccrew update --ide claude
|
|
|
213
265
|
|
|
214
266
|
> ผลลัพธ์ของแต่ละเฟสต้องการการยืนยันจากมนุษย์ก่อนดำเนินการต่อไปยังเฟสถัดไป
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. อัปเดต SpecCrew
|
|
269
|
+
|
|
270
|
+
เมื่อมีการเปิดตัว SpecCrew เวอร์ชันใหม่ ให้ทำการอัปเดตให้เสร็จสิ้นใน 2 ขั้นตอน:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **หมายเหตุ**: `npm install -g speccrew@latest` อัปเดตเครื่องมือ CLI เอง ในขณะที่ `speccrew update` อัปเดตไฟล์กำหนด Agent และ Skill ในโปรเจกต์ของคุณ ต้องใช้ทั้งสองขั้นตอนสำหรับการอัปเดตที่สมบูรณ์
|
|
282
|
+
|
|
283
|
+
### 5. คำสั่ง CLI อื่นๆ
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # แสดงรายการ agent และ skill ที่ติดตั้ง
|
package/README.tr.md
CHANGED
|
@@ -41,6 +41,58 @@ Mevcut projelere Agent'ları ve Skill'leri entegre ederek, ekipler proje doküma
|
|
|
41
41
|
|
|
42
42
|
---
|
|
43
43
|
|
|
44
|
+
## ✨ Ana Özellikler
|
|
45
|
+
|
|
46
|
+
### 🏭 Sanal Yazılım Ekibi
|
|
47
|
+
Tek tıkla **7 profesyonel Agent rolü** + **30+ Skill iş akışı** oluşturma, eksiksiz bir sanal yazılım ekibi oluşturma:
|
|
48
|
+
- **Team Leader** - Global planlama ve iterasyon yönetimi
|
|
49
|
+
- **Product Manager** - Gereksinim analizi ve PRD çıktısı
|
|
50
|
+
- **Feature Designer** - Özellik tasarımı + API sözleşmeleri
|
|
51
|
+
- **System Designer** - Frontend/Backend/Mobil/Desktop sistem tasarımı
|
|
52
|
+
- **System Developer** - Çoklu platform paralel geliştirme
|
|
53
|
+
- **Test Manager** - Üç aşamalı test koordinasyonu
|
|
54
|
+
- **Task Worker** - Alt görev paralel yürütme
|
|
55
|
+
|
|
56
|
+
### 📐 ISA-95 Altı Aşamalı Modelleme
|
|
57
|
+
Uluslararası **ISA-95** modelleme metodolojisine dayalı, iş gereksinimlerinden yazılım sistemlerine dönüşümün standartlaştırılması:
|
|
58
|
+
```
|
|
59
|
+
Domain Descriptions → Functions in Domains → Functions of Interest
|
|
60
|
+
↓ ↓ ↓
|
|
61
|
+
Information Flows → Categories of Information → Information Descriptions
|
|
62
|
+
```
|
|
63
|
+
- Her aşama belirli UML diyagramlarına karşılık gelir (use case, sequence, class)
|
|
64
|
+
- İş gereksinimleri "adım adım rafine edilir", bilgi kaybı olmadan
|
|
65
|
+
- Çıktılar geliştirme için doğrudan kullanılabilir
|
|
66
|
+
|
|
67
|
+
### 📚 Bilgi Tabanı Sistemi
|
|
68
|
+
AI'nın her zaman "tek gerçek kaynağına" dayanarak çalışmasını sağlayan üç katmanlı bilgi tabanı mimarisi:
|
|
69
|
+
|
|
70
|
+
| Katman | Dizin | İçerik | Amaç |
|
|
71
|
+
|--------|-------|--------|------|
|
|
72
|
+
| L1 Sistem Bilgisi | `knowledge/techs/` | Tech stack, mimari, sözleşmeler | AI projenin teknik sınırlarını anlar |
|
|
73
|
+
| L2 İş Bilgisi | `knowledge/bizs/` | Modül işlevleri, iş akışları, varlıklar | AI iş mantığını anlar |
|
|
74
|
+
| L3 İterasyon Eserleri | `iterations/iXXX/` | PRD, tasarım belgeleri, test raporları | Mevcut gereksinimler için eksiksiz izlenebilirlik zinciri |
|
|
75
|
+
|
|
76
|
+
### 🔄 Dört Aşamalı Bilgi Hattı
|
|
77
|
+
**Otomatik bilgi üretimi mimarisi**, kaynak koddan iş/teknik dokümantasyonun otomatik olarak oluşturulması:
|
|
78
|
+
```
|
|
79
|
+
Aşama 1: Kaynak kod tarama → Modül listesi oluşturma
|
|
80
|
+
Aşama 2: Paralel analiz → Özellik çıkarma (çoklu Worker paralel)
|
|
81
|
+
Aşama 3: Paralel özetleme → Modül görünümlerini tamamlama (çoklu Worker paralel)
|
|
82
|
+
Aşama 4: Sistem agregasyonu → Sistem panoraması oluşturma
|
|
83
|
+
```
|
|
84
|
+
- **Tam senkronizasyon** ve **artımlı senkronizasyon** destekler (Git diff tabanlı)
|
|
85
|
+
- Bir kişi optimize eder, ekip paylaşır
|
|
86
|
+
|
|
87
|
+
### 🔧 Harness Pratik Uygulama Çerçevesi
|
|
88
|
+
**Standartlaştırılmış yürütme çerçevesi**, tasarım belgelerinin yürütülebilir geliştirme talimatlarına hassas bir şekilde dönüştürülmesini sağlar:
|
|
89
|
+
- **Operasyonel kılavuz ilkesi**: Skill bir SOP'dur, adımlar net, ardışık ve kendi kendine yeten
|
|
90
|
+
- **Girdi-çıktı sözleşmesi**: Arayüzleri açıkça tanımlar, pseudocode gibi titizlikle yürütür
|
|
91
|
+
- **Aşamalı açıklama mimarisi**: Bilgileri katmanlı yükler, tek seferde bağlam aşırı yüklenmesini önler
|
|
92
|
+
- **Alt Agent delege etme**: Karmaşık görevleri otomatik böler, paralel yürütme kaliteyi güvence altına alır
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
44
96
|
## Çözülen 8 Temel Sorun
|
|
45
97
|
|
|
46
98
|
### 1. AI Mevcut Proje Dokümantasyonunu Görmezden Gelir (Bilgi Boşluğu)
|
|
@@ -189,7 +241,7 @@ speccrew init --ide claude
|
|
|
189
241
|
|
|
190
242
|
Başlatmadan sonra projenizde şu dosyalar oluşturulacaktır:
|
|
191
243
|
- `.qoder/agents/` / `.cursor/agents/` / `.claude/agents/` — 7 Agent rol tanımı
|
|
192
|
-
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` —
|
|
244
|
+
- `.qoder/skills/` / `.cursor/skills/` / `.claude/skills/` — 30+ Skill iş akışı
|
|
193
245
|
- `speccrew-workspace/` — Çalışma alanı (iterasyon dizinleri, bilgi tabanı, doküman şablonları)
|
|
194
246
|
- `.speccrewrc` — SpecCrew yapılandırma dosyası
|
|
195
247
|
|
|
@@ -213,7 +265,22 @@ Standart mühendislik iş akışını adım adım takip edin:
|
|
|
213
265
|
|
|
214
266
|
> Her aşamanın teslim edilebilirleri bir sonraki aşamaya geçmeden önce insan onayı gerektirir.
|
|
215
267
|
|
|
216
|
-
### 4.
|
|
268
|
+
### 4. SpecCrew'ü Güncelle
|
|
269
|
+
|
|
270
|
+
SpecCrew'un yeni bir sürümü yayınlandığında, güncellemeyi iki adımda tamamlayın:
|
|
271
|
+
|
|
272
|
+
```bash
|
|
273
|
+
# Step 1: Update the global CLI tool to the latest version
|
|
274
|
+
npm install -g speccrew@latest
|
|
275
|
+
|
|
276
|
+
# Step 2: Sync Agents and Skills in your project to the latest version
|
|
277
|
+
cd /path/to/your-project
|
|
278
|
+
speccrew update
|
|
279
|
+
```
|
|
280
|
+
|
|
281
|
+
> **Not**: `npm install -g speccrew@latest` CLI aracının kendisini güncellerken, `speccrew update` projenizdeki Agent ve Skill tanım dosyalarını günceller. Tam bir güncelleme için her iki adım da gereklidir.
|
|
282
|
+
|
|
283
|
+
### 5. Diğer CLI Komutları
|
|
217
284
|
|
|
218
285
|
```bash
|
|
219
286
|
speccrew list # Yüklü agent'ları ve skill'leri listele
|