my-opencode 1.3.4 → 3.0.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/LICENSE +21 -21
- package/README.md +309 -271
- package/agents/architect.md +30 -30
- package/agents/backend-dev.md +29 -0
- package/agents/business-analyst.md +30 -0
- package/agents/code-reviewer.md +29 -29
- package/agents/design-evidence.md +29 -0
- package/agents/frontend-dev.md +29 -0
- package/agents/system-designer.md +30 -0
- package/agents/team-lead.md +65 -60
- package/agents/tech-writer.md +30 -30
- package/agents/test-engineer.md +30 -30
- package/agents/verifier.md +38 -33
- package/bin/cli.js +366 -364
- package/bin/moc +206 -198
- package/bin/moc.js +9 -3
- package/opencode.json +240 -170
- package/package.json +53 -51
- package/plugins/README.md +74 -67
- package/plugins/provider-profile.mjs +238 -194
- package/scripts/postinstall.js +202 -202
- package/scripts/validate-role-flow.mjs +90 -0
- package/skills/adr/SKILL.md +91 -91
- package/skills/adr/references/templates.md +100 -100
- package/skills/adr/scripts/README.md +5 -5
- package/skills/design-evidence/SKILL.md +56 -0
- package/skills/dev-flow/SKILL.md +126 -188
- package/skills/dev-flow/references/code-phase.md +35 -72
- package/skills/dev-flow/references/contract-phase.md +66 -81
- package/skills/dev-flow/references/verify-phase.md +70 -129
- package/skills/dev-flow/scripts/README.md +3 -3
- package/skills/docs-gen/SKILL.md +162 -162
- package/skills/docs-gen/references/doc-styles.md +216 -216
- package/skills/docs-gen/scripts/README.md +5 -5
- package/skills/orchestrate/SKILL.md +63 -112
- package/skills/orchestrate/references/orchestration-patterns.md +49 -56
- package/skills/pr-review/SKILL.md +110 -110
- package/skills/pr-review/references/review-dimensions.md +117 -117
- package/skills/pr-review/references/security-checklist.md +122 -122
- package/skills/pr-review/scripts/README.md +5 -5
- package/skills/test-gen/SKILL.md +143 -143
- package/skills/test-gen/references/framework-detection.md +105 -105
- package/skills/test-gen/references/test-patterns.md +260 -260
- package/skills/test-gen/scripts/README.md +5 -5
- package/agents/executor.md +0 -30
- package/agents/fullstack-dev.md +0 -57
- package/agents/spec-writer.md +0 -37
|
@@ -1,216 +1,216 @@
|
|
|
1
|
-
# Doc Style Reference — Language-Specific Conventions
|
|
2
|
-
|
|
3
|
-
## TypeScript / JavaScript — JSDoc
|
|
4
|
-
|
|
5
|
-
```typescript
|
|
6
|
-
/**
|
|
7
|
-
* Creates a new user in the system.
|
|
8
|
-
*
|
|
9
|
-
* @param name - The user's display name (2-50 chars)
|
|
10
|
-
* @param email - The user's email address (must be unique)
|
|
11
|
-
* @returns The created user object with generated ID
|
|
12
|
-
* @throws {ValidationError} If name or email are invalid
|
|
13
|
-
* @throws {ConflictError} If email already exists
|
|
14
|
-
*/
|
|
15
|
-
async function createUser(name: string, email: string): Promise<User> {
|
|
16
|
-
```
|
|
17
|
-
|
|
18
|
-
### JSDoc Tags
|
|
19
|
-
| Tag | When to Use |
|
|
20
|
-
|-----|-------------|
|
|
21
|
-
| `@param name - desc` | Every function parameter |
|
|
22
|
-
| `@returns` | Non-void functions |
|
|
23
|
-
| `@throws` | Documented exceptions |
|
|
24
|
-
| `@template T` | Generic type parameters |
|
|
25
|
-
| `@deprecated reason` | Deprecated APIs, with migration path |
|
|
26
|
-
| `@example` | Usage example (preferred over prose) |
|
|
27
|
-
| `@see` | Cross-reference to related code |
|
|
28
|
-
|
|
29
|
-
---
|
|
30
|
-
|
|
31
|
-
## TypeScript / JavaScript — TSDoc
|
|
32
|
-
|
|
33
|
-
```typescript
|
|
34
|
-
/**
|
|
35
|
-
* Creates a new user in the system.
|
|
36
|
-
*
|
|
37
|
-
* @param name - The user's display name (2-50 chars)
|
|
38
|
-
* @param email - The user's email address (must be unique)
|
|
39
|
-
* @returns The created user
|
|
40
|
-
*
|
|
41
|
-
* @example
|
|
42
|
-
* ```ts
|
|
43
|
-
* const user = await createUser('Alice', 'alice@test.com')
|
|
44
|
-
* ```
|
|
45
|
-
*/
|
|
46
|
-
```
|
|
47
|
-
|
|
48
|
-
TSDoc is a superset of JSDoc with better TypeScript integration. Prefer TSDoc in TypeScript projects.
|
|
49
|
-
|
|
50
|
-
---
|
|
51
|
-
|
|
52
|
-
## Python — Google Style Docstrings
|
|
53
|
-
|
|
54
|
-
```python
|
|
55
|
-
def create_user(name: str, email: str) -> User:
|
|
56
|
-
"""Create a new user in the system.
|
|
57
|
-
|
|
58
|
-
Args:
|
|
59
|
-
name: The user's display name (2-50 chars).
|
|
60
|
-
email: The user's email address (must be unique).
|
|
61
|
-
|
|
62
|
-
Returns:
|
|
63
|
-
The created user object with generated ID.
|
|
64
|
-
|
|
65
|
-
Raises:
|
|
66
|
-
ValidationError: If name or email are invalid.
|
|
67
|
-
ConflictError: If email already exists.
|
|
68
|
-
"""
|
|
69
|
-
```
|
|
70
|
-
|
|
71
|
-
---
|
|
72
|
-
|
|
73
|
-
## Python — NumPy Style Docstrings
|
|
74
|
-
|
|
75
|
-
```python
|
|
76
|
-
def create_user(name: str, email: str) -> User:
|
|
77
|
-
"""Create a new user in the system.
|
|
78
|
-
|
|
79
|
-
Parameters
|
|
80
|
-
----------
|
|
81
|
-
name : str
|
|
82
|
-
The user's display name (2-50 chars).
|
|
83
|
-
email : str
|
|
84
|
-
The user's email address (must be unique).
|
|
85
|
-
|
|
86
|
-
Returns
|
|
87
|
-
-------
|
|
88
|
-
User
|
|
89
|
-
The created user object with generated ID.
|
|
90
|
-
|
|
91
|
-
Raises
|
|
92
|
-
------
|
|
93
|
-
ValidationError
|
|
94
|
-
If name or email are invalid.
|
|
95
|
-
"""
|
|
96
|
-
```
|
|
97
|
-
|
|
98
|
-
---
|
|
99
|
-
|
|
100
|
-
## Python — reST Style (Sphinx)
|
|
101
|
-
|
|
102
|
-
```python
|
|
103
|
-
def create_user(name: str, email: str) -> User:
|
|
104
|
-
"""Create a new user in the system.
|
|
105
|
-
|
|
106
|
-
:param name: The user's display name (2-50 chars).
|
|
107
|
-
:param email: The user's email address (must be unique).
|
|
108
|
-
:returns: The created user object with generated ID.
|
|
109
|
-
:raises ValidationError: If name or email are invalid.
|
|
110
|
-
:raises ConflictError: If email already exists.
|
|
111
|
-
"""
|
|
112
|
-
```
|
|
113
|
-
|
|
114
|
-
---
|
|
115
|
-
|
|
116
|
-
## Rust — rustdoc
|
|
117
|
-
|
|
118
|
-
```rust
|
|
119
|
-
/// Creates a new user in the system.
|
|
120
|
-
///
|
|
121
|
-
/// # Arguments
|
|
122
|
-
/// * `name` - The user's display name (2-50 chars)
|
|
123
|
-
/// * `email` - The user's email address (must be unique)
|
|
124
|
-
///
|
|
125
|
-
/// # Returns
|
|
126
|
-
/// The created `User` object
|
|
127
|
-
///
|
|
128
|
-
/// # Errors
|
|
129
|
-
/// Returns `ValidationError` if name or email are invalid.
|
|
130
|
-
/// Returns `ConflictError` if email already exists.
|
|
131
|
-
///
|
|
132
|
-
/// # Example
|
|
133
|
-
/// ```rust
|
|
134
|
-
/// let user = create_user("Alice", "alice@test.com")?;
|
|
135
|
-
/// ```
|
|
136
|
-
```
|
|
137
|
-
|
|
138
|
-
---
|
|
139
|
-
|
|
140
|
-
## Go — Godoc
|
|
141
|
-
|
|
142
|
-
```go
|
|
143
|
-
// CreateUser creates a new user in the system.
|
|
144
|
-
// It validates the input and checks for duplicate emails.
|
|
145
|
-
//
|
|
146
|
-
// Parameters:
|
|
147
|
-
// - name: the user's display name (2-50 chars)
|
|
148
|
-
// - email: the user's email address (must be unique)
|
|
149
|
-
//
|
|
150
|
-
// Returns the created user, or an error if validation fails
|
|
151
|
-
// or the email already exists.
|
|
152
|
-
func CreateUser(name string, email string) (*User, error) {
|
|
153
|
-
```
|
|
154
|
-
|
|
155
|
-
### Godoc Conventions
|
|
156
|
-
- First sentence is the summary (used in `go doc` listing)
|
|
157
|
-
- Use full sentences with proper punctuation
|
|
158
|
-
- Document function behavior, not implementation
|
|
159
|
-
- `//` only, no `/* */`
|
|
160
|
-
|
|
161
|
-
---
|
|
162
|
-
|
|
163
|
-
## ADR Template
|
|
164
|
-
|
|
165
|
-
```markdown
|
|
166
|
-
# ADR-001: Use PostgreSQL for Primary Database
|
|
167
|
-
|
|
168
|
-
**Date:** 2026-05-25
|
|
169
|
-
**Status:** Accepted
|
|
170
|
-
|
|
171
|
-
## Context
|
|
172
|
-
We need a primary database for storing user data.
|
|
173
|
-
The system needs strong consistency and complex queries.
|
|
174
|
-
|
|
175
|
-
## Decision
|
|
176
|
-
Use PostgreSQL 16 as the primary database.
|
|
177
|
-
|
|
178
|
-
## Consequences
|
|
179
|
-
- ✅ Strong consistency with ACID transactions
|
|
180
|
-
- ✅ Rich query capabilities (JSON, full-text search)
|
|
181
|
-
- ⚠️ Requires managed database service (increased cost)
|
|
182
|
-
- ⚠️ Schema migrations need careful planning
|
|
183
|
-
|
|
184
|
-
## Alternatives Considered
|
|
185
|
-
- MySQL: Similar capabilities but weaker JSON support
|
|
186
|
-
- MongoDB: Better horizontal scaling but eventual consistency
|
|
187
|
-
```
|
|
188
|
-
|
|
189
|
-
ADR numbering: sequential (`ADR-001`, `ADR-002`). Location: `docs/adr/`.
|
|
190
|
-
|
|
191
|
-
---
|
|
192
|
-
|
|
193
|
-
## CHANGELOG Template
|
|
194
|
-
|
|
195
|
-
```markdown
|
|
196
|
-
# Changelog
|
|
197
|
-
|
|
198
|
-
## [1.2.0] - 2026-05-25
|
|
199
|
-
|
|
200
|
-
### Added
|
|
201
|
-
- User creation API endpoint (POST /api/users)
|
|
202
|
-
- Email validation utility
|
|
203
|
-
|
|
204
|
-
### Changed
|
|
205
|
-
- Upgraded Express from 4.18 to 4.21
|
|
206
|
-
- Rate limiting now applied to all endpoints
|
|
207
|
-
|
|
208
|
-
### Fixed
|
|
209
|
-
- Memory leak in WebSocket connections
|
|
210
|
-
- Edge case in date parsing for timezone offsets
|
|
211
|
-
|
|
212
|
-
### Security
|
|
213
|
-
- Updated bcrypt dependency to patch CVE-2026-XXXX
|
|
214
|
-
```
|
|
215
|
-
|
|
216
|
-
Follow [Keep a Changelog](https://keepachangelog.com) convention unless project uses custom format.
|
|
1
|
+
# Doc Style Reference — Language-Specific Conventions
|
|
2
|
+
|
|
3
|
+
## TypeScript / JavaScript — JSDoc
|
|
4
|
+
|
|
5
|
+
```typescript
|
|
6
|
+
/**
|
|
7
|
+
* Creates a new user in the system.
|
|
8
|
+
*
|
|
9
|
+
* @param name - The user's display name (2-50 chars)
|
|
10
|
+
* @param email - The user's email address (must be unique)
|
|
11
|
+
* @returns The created user object with generated ID
|
|
12
|
+
* @throws {ValidationError} If name or email are invalid
|
|
13
|
+
* @throws {ConflictError} If email already exists
|
|
14
|
+
*/
|
|
15
|
+
async function createUser(name: string, email: string): Promise<User> {
|
|
16
|
+
```
|
|
17
|
+
|
|
18
|
+
### JSDoc Tags
|
|
19
|
+
| Tag | When to Use |
|
|
20
|
+
|-----|-------------|
|
|
21
|
+
| `@param name - desc` | Every function parameter |
|
|
22
|
+
| `@returns` | Non-void functions |
|
|
23
|
+
| `@throws` | Documented exceptions |
|
|
24
|
+
| `@template T` | Generic type parameters |
|
|
25
|
+
| `@deprecated reason` | Deprecated APIs, with migration path |
|
|
26
|
+
| `@example` | Usage example (preferred over prose) |
|
|
27
|
+
| `@see` | Cross-reference to related code |
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## TypeScript / JavaScript — TSDoc
|
|
32
|
+
|
|
33
|
+
```typescript
|
|
34
|
+
/**
|
|
35
|
+
* Creates a new user in the system.
|
|
36
|
+
*
|
|
37
|
+
* @param name - The user's display name (2-50 chars)
|
|
38
|
+
* @param email - The user's email address (must be unique)
|
|
39
|
+
* @returns The created user
|
|
40
|
+
*
|
|
41
|
+
* @example
|
|
42
|
+
* ```ts
|
|
43
|
+
* const user = await createUser('Alice', 'alice@test.com')
|
|
44
|
+
* ```
|
|
45
|
+
*/
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
TSDoc is a superset of JSDoc with better TypeScript integration. Prefer TSDoc in TypeScript projects.
|
|
49
|
+
|
|
50
|
+
---
|
|
51
|
+
|
|
52
|
+
## Python — Google Style Docstrings
|
|
53
|
+
|
|
54
|
+
```python
|
|
55
|
+
def create_user(name: str, email: str) -> User:
|
|
56
|
+
"""Create a new user in the system.
|
|
57
|
+
|
|
58
|
+
Args:
|
|
59
|
+
name: The user's display name (2-50 chars).
|
|
60
|
+
email: The user's email address (must be unique).
|
|
61
|
+
|
|
62
|
+
Returns:
|
|
63
|
+
The created user object with generated ID.
|
|
64
|
+
|
|
65
|
+
Raises:
|
|
66
|
+
ValidationError: If name or email are invalid.
|
|
67
|
+
ConflictError: If email already exists.
|
|
68
|
+
"""
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
## Python — NumPy Style Docstrings
|
|
74
|
+
|
|
75
|
+
```python
|
|
76
|
+
def create_user(name: str, email: str) -> User:
|
|
77
|
+
"""Create a new user in the system.
|
|
78
|
+
|
|
79
|
+
Parameters
|
|
80
|
+
----------
|
|
81
|
+
name : str
|
|
82
|
+
The user's display name (2-50 chars).
|
|
83
|
+
email : str
|
|
84
|
+
The user's email address (must be unique).
|
|
85
|
+
|
|
86
|
+
Returns
|
|
87
|
+
-------
|
|
88
|
+
User
|
|
89
|
+
The created user object with generated ID.
|
|
90
|
+
|
|
91
|
+
Raises
|
|
92
|
+
------
|
|
93
|
+
ValidationError
|
|
94
|
+
If name or email are invalid.
|
|
95
|
+
"""
|
|
96
|
+
```
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## Python — reST Style (Sphinx)
|
|
101
|
+
|
|
102
|
+
```python
|
|
103
|
+
def create_user(name: str, email: str) -> User:
|
|
104
|
+
"""Create a new user in the system.
|
|
105
|
+
|
|
106
|
+
:param name: The user's display name (2-50 chars).
|
|
107
|
+
:param email: The user's email address (must be unique).
|
|
108
|
+
:returns: The created user object with generated ID.
|
|
109
|
+
:raises ValidationError: If name or email are invalid.
|
|
110
|
+
:raises ConflictError: If email already exists.
|
|
111
|
+
"""
|
|
112
|
+
```
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## Rust — rustdoc
|
|
117
|
+
|
|
118
|
+
```rust
|
|
119
|
+
/// Creates a new user in the system.
|
|
120
|
+
///
|
|
121
|
+
/// # Arguments
|
|
122
|
+
/// * `name` - The user's display name (2-50 chars)
|
|
123
|
+
/// * `email` - The user's email address (must be unique)
|
|
124
|
+
///
|
|
125
|
+
/// # Returns
|
|
126
|
+
/// The created `User` object
|
|
127
|
+
///
|
|
128
|
+
/// # Errors
|
|
129
|
+
/// Returns `ValidationError` if name or email are invalid.
|
|
130
|
+
/// Returns `ConflictError` if email already exists.
|
|
131
|
+
///
|
|
132
|
+
/// # Example
|
|
133
|
+
/// ```rust
|
|
134
|
+
/// let user = create_user("Alice", "alice@test.com")?;
|
|
135
|
+
/// ```
|
|
136
|
+
```
|
|
137
|
+
|
|
138
|
+
---
|
|
139
|
+
|
|
140
|
+
## Go — Godoc
|
|
141
|
+
|
|
142
|
+
```go
|
|
143
|
+
// CreateUser creates a new user in the system.
|
|
144
|
+
// It validates the input and checks for duplicate emails.
|
|
145
|
+
//
|
|
146
|
+
// Parameters:
|
|
147
|
+
// - name: the user's display name (2-50 chars)
|
|
148
|
+
// - email: the user's email address (must be unique)
|
|
149
|
+
//
|
|
150
|
+
// Returns the created user, or an error if validation fails
|
|
151
|
+
// or the email already exists.
|
|
152
|
+
func CreateUser(name string, email string) (*User, error) {
|
|
153
|
+
```
|
|
154
|
+
|
|
155
|
+
### Godoc Conventions
|
|
156
|
+
- First sentence is the summary (used in `go doc` listing)
|
|
157
|
+
- Use full sentences with proper punctuation
|
|
158
|
+
- Document function behavior, not implementation
|
|
159
|
+
- `//` only, no `/* */`
|
|
160
|
+
|
|
161
|
+
---
|
|
162
|
+
|
|
163
|
+
## ADR Template
|
|
164
|
+
|
|
165
|
+
```markdown
|
|
166
|
+
# ADR-001: Use PostgreSQL for Primary Database
|
|
167
|
+
|
|
168
|
+
**Date:** 2026-05-25
|
|
169
|
+
**Status:** Accepted
|
|
170
|
+
|
|
171
|
+
## Context
|
|
172
|
+
We need a primary database for storing user data.
|
|
173
|
+
The system needs strong consistency and complex queries.
|
|
174
|
+
|
|
175
|
+
## Decision
|
|
176
|
+
Use PostgreSQL 16 as the primary database.
|
|
177
|
+
|
|
178
|
+
## Consequences
|
|
179
|
+
- ✅ Strong consistency with ACID transactions
|
|
180
|
+
- ✅ Rich query capabilities (JSON, full-text search)
|
|
181
|
+
- ⚠️ Requires managed database service (increased cost)
|
|
182
|
+
- ⚠️ Schema migrations need careful planning
|
|
183
|
+
|
|
184
|
+
## Alternatives Considered
|
|
185
|
+
- MySQL: Similar capabilities but weaker JSON support
|
|
186
|
+
- MongoDB: Better horizontal scaling but eventual consistency
|
|
187
|
+
```
|
|
188
|
+
|
|
189
|
+
ADR numbering: sequential (`ADR-001`, `ADR-002`). Location: `docs/adr/`.
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
193
|
+
## CHANGELOG Template
|
|
194
|
+
|
|
195
|
+
```markdown
|
|
196
|
+
# Changelog
|
|
197
|
+
|
|
198
|
+
## [1.2.0] - 2026-05-25
|
|
199
|
+
|
|
200
|
+
### Added
|
|
201
|
+
- User creation API endpoint (POST /api/users)
|
|
202
|
+
- Email validation utility
|
|
203
|
+
|
|
204
|
+
### Changed
|
|
205
|
+
- Upgraded Express from 4.18 to 4.21
|
|
206
|
+
- Rate limiting now applied to all endpoints
|
|
207
|
+
|
|
208
|
+
### Fixed
|
|
209
|
+
- Memory leak in WebSocket connections
|
|
210
|
+
- Edge case in date parsing for timezone offsets
|
|
211
|
+
|
|
212
|
+
### Security
|
|
213
|
+
- Updated bcrypt dependency to patch CVE-2026-XXXX
|
|
214
|
+
```
|
|
215
|
+
|
|
216
|
+
Follow [Keep a Changelog](https://keepachangelog.com) convention unless project uses custom format.
|
|
@@ -1,5 +1,5 @@
|
|
|
1
|
-
# docs-gen Scripts
|
|
2
|
-
|
|
3
|
-
Placeholder for documentation utility scripts. Future candidates:
|
|
4
|
-
- `api-docs-from-routes.py` — Parse Express/FastAPI routes and generate API doc stubs
|
|
5
|
-
- `changelog-bump.py` — Generate changelog entry from conventional commits
|
|
1
|
+
# docs-gen Scripts
|
|
2
|
+
|
|
3
|
+
Placeholder for documentation utility scripts. Future candidates:
|
|
4
|
+
- `api-docs-from-routes.py` — Parse Express/FastAPI routes and generate API doc stubs
|
|
5
|
+
- `changelog-bump.py` — Generate changelog entry from conventional commits
|
|
@@ -1,112 +1,63 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: orchestrate
|
|
3
|
-
description: |
|
|
4
|
-
|
|
5
|
-
Use when tasks span multiple domains, require parallel execution, or need full lifecycle management.
|
|
6
|
-
Triggers on: "orchestrate", "coordinate", "manage", "run the full pipeline", "team", "complex task"
|
|
7
|
-
---
|
|
8
|
-
|
|
9
|
-
#
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
##
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
38
|
-
|
|
39
|
-
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
|
|
50
|
-
|
|
51
|
-
|
|
52
|
-
|
|
53
|
-
|
|
54
|
-
|
|
55
|
-
|
|
56
|
-
|
|
57
|
-
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
Task 1: architect (ADR) → Task 2: spec-writer (contract) → Task 3: executor (implement)
|
|
65
|
-
```
|
|
66
|
-
|
|
67
|
-
### Step 4: Collection
|
|
68
|
-
|
|
69
|
-
Read contract outputs from `docs/adr/` and `docs/specs/` for each subtask.
|
|
70
|
-
Resolve conflicts between parallel streams.
|
|
71
|
-
|
|
72
|
-
### Step 5: Synthesis
|
|
73
|
-
|
|
74
|
-
Combine parallel results into a coherent whole. Write `.handoffs/orchestrate/synthesis.md` with:
|
|
75
|
-
- What each subtask produced
|
|
76
|
-
- Integration notes
|
|
77
|
-
- Remaining work
|
|
78
|
-
- Risks discovered
|
|
79
|
-
|
|
80
|
-
### Step 6: Review
|
|
81
|
-
|
|
82
|
-
Run pr-review on the synthesized result:
|
|
83
|
-
- Delegate to code-reviewer agent
|
|
84
|
-
- Apply fixes if issues found
|
|
85
|
-
- Check that all architectural decisions have ADRs
|
|
86
|
-
|
|
87
|
-
### Step 7: Verification
|
|
88
|
-
|
|
89
|
-
Run tests:
|
|
90
|
-
- Delegate to test-engineer for new test generation
|
|
91
|
-
- Delegate to verifier for full test suite run
|
|
92
|
-
|
|
93
|
-
## Artifact Summary
|
|
94
|
-
|
|
95
|
-
| Artifact | Location | Persistent | Purpose |
|
|
96
|
-
|----------|----------|------------|---------|
|
|
97
|
-
| ADR | `docs/adr/NNNN-title.md` | ✅ Committed | Architecture decisions |
|
|
98
|
-
| Contract | `docs/specs/<feature>/` | ✅ Committed | Requirements, ACs, API |
|
|
99
|
-
| Synthesis | `.handoffs/orchestrate/synthesis.md` | ❌ Temporary | Merge notes |
|
|
100
|
-
|
|
101
|
-
## Handoff Directory
|
|
102
|
-
|
|
103
|
-
All orchestration state: `.handoffs/orchestrate/`
|
|
104
|
-
|
|
105
|
-
## Error Recovery
|
|
106
|
-
|
|
107
|
-
| Failure | Action |
|
|
108
|
-
|---------|--------|
|
|
109
|
-
| Subtask fails | Retry once, then report to user |
|
|
110
|
-
| Parallel conflicts | Reconcile in synthesis phase |
|
|
111
|
-
| Verification fails | Enter fix loop (max 3 retries) |
|
|
112
|
-
| User changes mind | Accept new direction, re-plan affected subtasks |
|
|
1
|
+
---
|
|
2
|
+
name: orchestrate
|
|
3
|
+
description: |
|
|
4
|
+
Orchestrate evidence-first delivery across Design Evidence, SA, SD, frontend, backend, review, tests, and verification.
|
|
5
|
+
Use when tasks span multiple domains, require parallel execution, or need full lifecycle management.
|
|
6
|
+
Triggers on: "orchestrate", "coordinate", "manage", "run the full pipeline", "team", "complex task"
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
# Evidence-First Orchestration
|
|
10
|
+
|
|
11
|
+
## Workflow
|
|
12
|
+
|
|
13
|
+
```text
|
|
14
|
+
Intake → Evidence → SA → SD → Slice Plan
|
|
15
|
+
├→ Frontend slice ─┐
|
|
16
|
+
└→ Backend slice ───┼→ Review → QA/Verify → Synthesis
|
|
17
|
+
```
|
|
18
|
+
|
|
19
|
+
## Dispatch Rules
|
|
20
|
+
|
|
21
|
+
1. `team-lead` records feature ID, source/version, owner, scope, status, and approval state.
|
|
22
|
+
2. `design-evidence` runs before business analysis whenever UI/UX input exists.
|
|
23
|
+
3. `business-analyst` runs after evidence and resolves business meaning only.
|
|
24
|
+
4. `system-designer` runs after business approval and produces the shared technical design plus role views.
|
|
25
|
+
5. `frontend-dev` and `backend-dev` run concurrently only after their contracts are ready.
|
|
26
|
+
6. `code-reviewer` reviews each bounded slice; `test-engineer` fills test gaps.
|
|
27
|
+
7. `verifier` independently checks business, visual/interaction, API/data, security/operations, and mechanical checks.
|
|
28
|
+
8. `team-lead` resolves conflicts, persists traceability and the final verification report, and starts the fix loop when needed.
|
|
29
|
+
|
|
30
|
+
## Slice Requirements
|
|
31
|
+
|
|
32
|
+
Each dispatched slice MUST include:
|
|
33
|
+
|
|
34
|
+
- Input artifact paths and source version
|
|
35
|
+
- Owner and reviewer
|
|
36
|
+
- File and behavior boundary
|
|
37
|
+
- `EVID-*`, `BR-*`, `BUS-*`, `API-*`, `DATA-*`, `AC-*`, and `VER-*` IDs in scope
|
|
38
|
+
- Expected output and verification command
|
|
39
|
+
|
|
40
|
+
Do not send a whole page or service to one worker when it can be split into independently reviewable slices.
|
|
41
|
+
|
|
42
|
+
## Parallelism
|
|
43
|
+
|
|
44
|
+
Parallelize independent evidence extraction, frontend/backend implementation, tests, and per-slice reviews. Keep dependencies sequential:
|
|
45
|
+
|
|
46
|
+
```text
|
|
47
|
+
Evidence → SA → SD → role contracts → implementation
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
Never run implementation before the contracts are approved. Never let parallel workers independently reinterpret the original design input.
|
|
51
|
+
|
|
52
|
+
## Synthesis
|
|
53
|
+
|
|
54
|
+
The synthesis must record:
|
|
55
|
+
|
|
56
|
+
- Artifact and code outputs by subtask
|
|
57
|
+
- Integrated slice list and owners
|
|
58
|
+
- Traceability coverage and unresolved unknowns
|
|
59
|
+
- Contract deviations and their owning layer
|
|
60
|
+
- Review findings and verification results
|
|
61
|
+
- Remaining work and release risks
|
|
62
|
+
|
|
63
|
+
Persist long-lived decisions and verification evidence under `docs/specs/<feature>/`; keep session-only coordination notes under `.handoffs/orchestrate/`.
|