rrce-workflow 0.2.77 → 0.2.79
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/agent-core/prompts/doctor.md +20 -4
- package/agent-core/prompts/executor.md +224 -56
- package/agent-core/prompts/init.md +2 -1
- package/agent-core/prompts/planning_discussion.md +292 -0
- package/agent-core/prompts/research_discussion.md +167 -65
- package/agent-core/templates/planning_output.md +154 -29
- package/agent-core/templates/research_output.md +134 -32
- package/dist/index.js +347 -56
- package/docs/architecture.md +14 -0
- package/package.json +1 -1
- package/agent-core/prompts/planning_orchestrator.md +0 -85
|
@@ -18,48 +18,150 @@
|
|
|
18
18
|
- {{date}}: ISO date (YYYY-MM-DD)
|
|
19
19
|
- {{source}}: URL or reference to original request
|
|
20
20
|
- {{workspace_name}}: Project name
|
|
21
|
+
|
|
22
|
+
NOTE: This document is the output of an interactive research session.
|
|
23
|
+
The Research agent engaged in constructive dialogue with the user to
|
|
24
|
+
achieve 100% understanding before this brief was generated.
|
|
21
25
|
-->
|
|
22
26
|
# Research Brief – {{task_title}}
|
|
23
27
|
|
|
24
|
-
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
28
|
+
| Field | Value |
|
|
29
|
+
|-------|-------|
|
|
30
|
+
| Task ID | `{{task_id}}` |
|
|
31
|
+
| Task Slug | `{{task_slug}}` |
|
|
32
|
+
| Author | `{{author}}` |
|
|
33
|
+
| Date | `{{date}}` |
|
|
34
|
+
| Source Request | `{{source}}` |
|
|
35
|
+
| Workspace | `{{workspace_name}}` |
|
|
36
|
+
|
|
37
|
+
---
|
|
30
38
|
|
|
31
39
|
## 1. Request Summary
|
|
32
|
-
- Concise restatement of the user's ask.
|
|
33
|
-
- Highlight explicit goals, constraints, and success metrics.
|
|
34
40
|
|
|
35
|
-
|
|
36
|
-
|
|
37
|
-
|
|
41
|
+
> **Original Request**: [Quote the user's initial request]
|
|
42
|
+
|
|
43
|
+
**Refined Understanding** (after clarification):
|
|
44
|
+
- [Clear, specific statement of what needs to be built]
|
|
45
|
+
- [Why it needs to be built - problem/opportunity]
|
|
46
|
+
|
|
47
|
+
---
|
|
48
|
+
|
|
49
|
+
## 2. Clarification Summary
|
|
50
|
+
|
|
51
|
+
The following was clarified through interactive dialogue:
|
|
52
|
+
|
|
53
|
+
| Topic | Question Asked | User Response | Impact on Scope |
|
|
54
|
+
|-------|----------------|---------------|-----------------|
|
|
55
|
+
| Intent | | | |
|
|
56
|
+
| Constraints | | | |
|
|
57
|
+
| Success Criteria | | | |
|
|
58
|
+
| Edge Cases | | | |
|
|
59
|
+
|
|
60
|
+
**Key Decisions Made**:
|
|
61
|
+
- [Decision 1 and rationale]
|
|
62
|
+
- [Decision 2 and rationale]
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## 3. Current Knowledge Snapshot
|
|
67
|
+
|
|
68
|
+
Relevant prior work and context from project knowledge:
|
|
69
|
+
|
|
70
|
+
| Source | Relevance |
|
|
71
|
+
|--------|-----------|
|
|
72
|
+
| `{{RRCE_DATA}}/knowledge/...` | [How it applies] |
|
|
73
|
+
| [Search result] | [How it applies] |
|
|
74
|
+
|
|
75
|
+
**Patterns to Follow**:
|
|
76
|
+
- [Existing pattern 1 from codebase]
|
|
77
|
+
- [Existing pattern 2 from codebase]
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## 4. Requirements
|
|
82
|
+
|
|
83
|
+
### Functional Requirements
|
|
84
|
+
- [ ] [FR-1]: [Requirement description]
|
|
85
|
+
- [ ] [FR-2]: [Requirement description]
|
|
86
|
+
- [ ] [FR-3]: [Requirement description]
|
|
87
|
+
|
|
88
|
+
### Non-Functional Requirements
|
|
89
|
+
- [ ] [NFR-1]: [Performance/Security/etc. requirement]
|
|
90
|
+
- [ ] [NFR-2]: [Requirement description]
|
|
91
|
+
|
|
92
|
+
### Success Criteria
|
|
93
|
+
How we'll know this is done:
|
|
94
|
+
1. [Measurable outcome 1]
|
|
95
|
+
2. [Measurable outcome 2]
|
|
96
|
+
3. [Measurable outcome 3]
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## 5. Scope Boundaries
|
|
101
|
+
|
|
102
|
+
### In Scope
|
|
103
|
+
- [Explicit inclusion 1]
|
|
104
|
+
- [Explicit inclusion 2]
|
|
105
|
+
|
|
106
|
+
### Out of Scope
|
|
107
|
+
- [Explicit exclusion 1]
|
|
108
|
+
- [Explicit exclusion 2]
|
|
109
|
+
|
|
110
|
+
### Constraints
|
|
111
|
+
- [Hard constraint 1 - e.g., timeline, tech, resources]
|
|
112
|
+
- [Hard constraint 2]
|
|
113
|
+
|
|
114
|
+
---
|
|
115
|
+
|
|
116
|
+
## 6. Assumptions & Risks
|
|
117
|
+
|
|
118
|
+
### Assumptions
|
|
119
|
+
| ID | Assumption | Confidence | Validation Needed |
|
|
120
|
+
|----|------------|------------|-------------------|
|
|
121
|
+
| A1 | [Assumption] | High/Medium/Low | [How to validate] |
|
|
122
|
+
| A2 | [Assumption] | High/Medium/Low | [How to validate] |
|
|
123
|
+
|
|
124
|
+
### Risks
|
|
125
|
+
| ID | Risk | Impact | Likelihood | Mitigation |
|
|
126
|
+
|----|------|--------|------------|------------|
|
|
127
|
+
| R1 | [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation] |
|
|
128
|
+
| R2 | [Risk description] | High/Medium/Low | High/Medium/Low | [Mitigation] |
|
|
129
|
+
|
|
130
|
+
---
|
|
131
|
+
|
|
132
|
+
## 7. Opportunity & Alternative Approaches
|
|
133
|
+
|
|
134
|
+
Approaches considered during research:
|
|
135
|
+
|
|
136
|
+
| Approach | Pros | Cons | Recommendation |
|
|
137
|
+
|----------|------|------|----------------|
|
|
138
|
+
| [Approach A] | | | Chosen / Rejected |
|
|
139
|
+
| [Approach B] | | | Chosen / Rejected |
|
|
140
|
+
|
|
141
|
+
**Rationale for chosen approach**: [Explanation]
|
|
142
|
+
|
|
143
|
+
---
|
|
38
144
|
|
|
39
|
-
##
|
|
40
|
-
- Relevant prior work or documents from `{{RRCE_DATA}}/knowledge` or workspace.
|
|
41
|
-
- Key facts that shape feasibility or scope.
|
|
145
|
+
## 8. Hand-off Notes for Planning
|
|
42
146
|
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
147
|
+
### Ready for Planning
|
|
148
|
+
- [ ] Core requirements are clear and specific
|
|
149
|
+
- [ ] Success criteria are measurable
|
|
150
|
+
- [ ] Scope boundaries are explicit
|
|
151
|
+
- [ ] No blocking open questions remain
|
|
47
152
|
|
|
48
|
-
|
|
49
|
-
-
|
|
50
|
-
-
|
|
153
|
+
### Context for Planning Agent
|
|
154
|
+
- [Important context the planner needs to know]
|
|
155
|
+
- [Technical considerations for task breakdown]
|
|
51
156
|
|
|
52
|
-
|
|
53
|
-
-
|
|
54
|
-
- Trade-offs or spikes recommended before execution.
|
|
157
|
+
### Open Questions (Non-Blocking)
|
|
158
|
+
- [Question that can be resolved during planning or execution]
|
|
55
159
|
|
|
56
|
-
|
|
57
|
-
-
|
|
58
|
-
- Note acceptance signals or metrics where available.
|
|
160
|
+
### References Added to meta.json
|
|
161
|
+
- [List of knowledge files referenced]
|
|
59
162
|
|
|
60
|
-
|
|
61
|
-
- Immediate next steps for Planning.
|
|
62
|
-
- Pending clarifications or decisions to resolve.
|
|
63
|
-
- References added to `meta.json`.
|
|
163
|
+
---
|
|
64
164
|
|
|
65
|
-
>
|
|
165
|
+
> **Next Step**: `/plan TASK_SLUG={{task_slug}}`
|
|
166
|
+
>
|
|
167
|
+
> Keep this document under 500 lines. Replace placeholders with concise entries and trim empty sections.
|