-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathmanifest.yml
More file actions
225 lines (196 loc) · 5.59 KB
/
manifest.yml
File metadata and controls
225 lines (196 loc) · 5.59 KB
1
2
3
4
5
6
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
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
# Engineering Team Manifest
#
# Single source of truth for:
# - Role roster (who's on the team, which agent type, review order)
# - Pipeline stages (workflow, commands, labels)
# - Controlled vocabularies (severity levels, test layers, etc.)
#
# All process docs and templates derive from this file.
# When this file changes, cascade updates to downstream consumers.
team: engineering
version: 1
# --- Roles ---
# Persona files are relative to this manifest's directory.
# Agent type IDs reference agents.yml.
# Optional `stages` map overrides the default `agent` for specific pipeline stages.
roles:
- id: ux-designer
name: UX Designer
agent: builder
stages: { review-merge: validator }
persona: personas/ux-designer.md
reviews_code: true
review_order: 1
- id: software-engineer
name: Software Engineer
agent: builder
stages: { review-merge: validator }
persona: personas/software-engineer.md
reviews_code: true
review_order: 2
- id: system-architect
name: System Architect
agent: builder
stages: { review-merge: validator }
persona: personas/system-architect.md
reviews_code: true
review_order: 3
- id: data-engineer
name: Data Engineer
agent: builder
stages: { review-merge: validator }
persona: personas/data-engineer.md
reviews_code: true
review_order: 4
- id: ai-ml-engineer
name: AI/ML Engineer
agent: builder
stages: { review-merge: validator }
persona: personas/ai-ml-engineer.md
reviews_code: true
review_order: 5
- id: security-engineer
name: Security Engineer
agent: validator
persona: personas/security-engineer.md
reviews_code: true
review_order: 6
- id: qa-engineer
name: QA Engineer
agent: validator
persona: personas/qa-engineer.md
reviews_code: true
review_order: 7
- id: sre
name: SRE
agent: builder
stages: { review-merge: validator }
persona: personas/sre.md
reviews_code: true
review_order: 8
- id: writer
name: Writer
agent: validator
persona: personas/writer.md
reviews_code: true
review_order: 9
- id: engineering-manager
name: Engineering Manager
agent: builder
persona: personas/engineering-manager.md
reviews_code: false
synthesizes: true
review_order: last
- id: pm
name: PM
agent: validator
persona: personas/pm.md
reviews_code: false
pipeline_only: true
shared_traits: personas/cross-cutting-traits.md
# --- Pipeline ---
# Each stage defines what happens, who does it, and which label marks completion.
# Command names map to per-project slash commands (e.g., .claude/commands/define.md).
pipeline:
- stage: pm-review
name: Define
command: /define
agent: validator
label:
name: pm-reviewed
color: "6f42c1"
produces: "PRD comment on the GitHub issue"
- stage: design-review
name: Design
command: /design
agent: [builder, validator]
label:
name: design-complete
color: "0e8a16"
produces: "Design decision + test specification comments"
- stage: implement
name: Implement
command: /implement
agent: builder
label:
name: implementing
color: "fbca04"
produces: "Code in a feature branch, all tests passing"
- stage: review-merge
name: Review
command: /review
agent: [builder, validator]
label:
name: merged
color: "6e5494"
produces: "Merged PR"
- stage: deploy
name: Deploy & Verify
agent: builder
produces: "Running deployment"
- stage: summarize
name: Summarize
command: /summarize
agent: validator
label:
name: summarized
optional: true
produces: "Summary comment"
# --- Controlled Vocabularies ---
# Canonical definitions. Process docs and project configs reference these.
vocabularies:
severity_levels:
- id: must-fix
name: MUST-FIX
blocks: merge
description: "Correctness bug, security vulnerability, data loss risk, or broken contract"
- id: should-fix
name: SHOULD-FIX
blocks: current_round
description: "Code quality issue, missing edge case, poor naming, or maintainability concern"
- id: nit
name: NIT
blocks: nothing
description: "Style preference, minor suggestion, optional improvement"
test_layers:
- id: service
name: Service / Unit
speed: fastest
when: "Pure logic, models, services — no HTTP, no UI"
- id: api
name: API / Endpoint
speed: fast
when: "HTTP status, response shapes, auth checks"
- id: component
name: Component
speed: medium
when: "UI component rendering, user interaction"
- id: e2e
name: E2E / Browser
speed: slowest
when: "Cross-page workflows, JS interaction, auth boundary testing"
commit_prefixes:
- feat
- fix
- test
- docs
- refactor
pipeline_modes:
- id: autonomous
description: "No human review gates. Pipeline runs end-to-end."
- id: gated
description: "Agents notify and wait for human authorization before publishing and integrating."
task_modes:
- id: build
description: "Design API first. Write tests before implementation."
- id: debug
description: "Reproduce → Hypothesis → Evidence → Fix → Verify"
- id: refactor
description: "Tests first. One change at a time. Preserve behavior."
- id: review
description: "Correctness > style. Flag what matters, ignore what doesn't."
# --- Settings ---
# Numeric constants referenced across process docs.
settings:
max_review_rounds: 3
ci_time_limit_minutes: 10