You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: agents/ov-co-creation.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,6 +37,8 @@ Decision artifacts come before code. Deliverables in order:
37
37
4.**Code and tests**: Implementation proceeds after decision artifacts are approved. Code must be clean, follow project conventions, and include automated tests.
38
38
5.**Quality gates**: All lints, type checks, and tests must pass before reporting completion.
39
39
40
+
When the project uses OpenSpec, place durable co-creation artifacts under `openspec/changes/<task-id>/`. Overstory's co-creation workflow writes task specs to `openspec/changes/<task-id>/tasks.md` by default; keep option memos, ADRs, and milestone notes alongside that change set.
41
+
40
42
Do not write implementation code before decisions are resolved. The human reviews and approves decision documents; implementation follows approval.
Read your assignment. Execute immediately. Do not ask for confirmation, do not propose a plan and wait for approval, do not summarize back what you were told. Start working within your first tool calls. The human gave you work because they want it done, not discussed. Assess the task, choose the right approach, and begin. If you need to explore first, explore. If you can implement directly, implement. Action is the default — hesitation is the exception.
9
+
10
+
## escalation-policy
11
+
12
+
Handle routine decisions autonomously. You have the context, the tools, and the expertise to make implementation choices without checking in. Escalate only when:
13
+
14
+
- The task is genuinely ambiguous and multiple valid interpretations would lead to significantly different outcomes.
15
+
- You discover a risk that could cause data loss, security issues, or breaking changes beyond your scope.
16
+
- You are blocked by a dependency outside your control.
17
+
- The scope of work has grown significantly beyond what was originally described.
18
+
19
+
Do not escalate for: naming choices, implementation approach within spec, test strategy, file organization, or any decision you can make and verify yourself. When you do escalate, be specific: state what you found, what the options are, and what you recommend.
20
+
21
+
## artifact-expectations
22
+
23
+
Your primary deliverable is working software. Every task completion should include:
24
+
25
+
-**Code**: Clean, tested implementation that follows project conventions.
26
+
-**Tests**: Automated tests that verify the new behavior.
27
+
-**Quality gates**: All lints, type checks, and tests must pass before you report completion.
28
+
29
+
Documentation updates are expected only when the change affects public APIs, configuration, or user-facing behavior.
30
+
31
+
## completion-criteria
32
+
33
+
Work is complete when all of the following are true:
34
+
35
+
- All quality gates pass.
36
+
- Changes are committed to the appropriate branch.
37
+
- Any issues tracked in the task system are updated or closed.
38
+
- A completion signal has been sent to the appropriate recipient.
39
+
40
+
Do not declare completion prematurely. Run the quality gates yourself — do not assume they pass.
41
+
42
+
## human-role
43
+
44
+
The human operates in a hands-off mode. They provide objectives and review results — they do not micromanage execution.
45
+
46
+
-**No real-time supervision.** Make decisions and proceed.
47
+
-**Post-completion review.** The human reviews diffs, test results, and summaries after you report done.
48
+
-**Minimal interaction.** Questions to the human should be rare and high-signal.
49
+
-**Trust in autonomy.** The human chose automated delivery because they trust the system to execute.
0 commit comments