opencode-conductor-plugin 1.1.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 +202 -0
- package/README.md +91 -0
- package/dist/commands/implement.d.ts +2 -0
- package/dist/commands/implement.js +17 -0
- package/dist/commands/newTrack.d.ts +2 -0
- package/dist/commands/newTrack.js +19 -0
- package/dist/commands/revert.d.ts +2 -0
- package/dist/commands/revert.js +17 -0
- package/dist/commands/setup.d.ts +2 -0
- package/dist/commands/setup.js +19 -0
- package/dist/commands/status.d.ts +2 -0
- package/dist/commands/status.js +15 -0
- package/dist/index.d.ts +3 -0
- package/dist/index.js +97 -0
- package/dist/prompts/agent/conductor.md +33 -0
- package/dist/prompts/agent.md +23 -0
- package/dist/prompts/commands/c-implement.md +5 -0
- package/dist/prompts/commands/c-new.md +5 -0
- package/dist/prompts/commands/c-revert.md +5 -0
- package/dist/prompts/commands/c-setup.md +5 -0
- package/dist/prompts/commands/c-status.md +5 -0
- package/dist/prompts/implement.toml +170 -0
- package/dist/prompts/newTrack.toml +144 -0
- package/dist/prompts/revert.toml +123 -0
- package/dist/prompts/setup.toml +426 -0
- package/dist/prompts/status.toml +57 -0
- package/dist/templates/code_styleguides/c.md +28 -0
- package/dist/templates/code_styleguides/cpp.md +46 -0
- package/dist/templates/code_styleguides/csharp.md +115 -0
- package/dist/templates/code_styleguides/dart.md +238 -0
- package/dist/templates/code_styleguides/general.md +23 -0
- package/dist/templates/code_styleguides/go.md +48 -0
- package/dist/templates/code_styleguides/html-css.md +49 -0
- package/dist/templates/code_styleguides/java.md +39 -0
- package/dist/templates/code_styleguides/javascript.md +51 -0
- package/dist/templates/code_styleguides/julia.md +27 -0
- package/dist/templates/code_styleguides/kotlin.md +41 -0
- package/dist/templates/code_styleguides/php.md +37 -0
- package/dist/templates/code_styleguides/python.md +37 -0
- package/dist/templates/code_styleguides/react.md +37 -0
- package/dist/templates/code_styleguides/ruby.md +39 -0
- package/dist/templates/code_styleguides/rust.md +44 -0
- package/dist/templates/code_styleguides/shell.md +35 -0
- package/dist/templates/code_styleguides/solidity.md +60 -0
- package/dist/templates/code_styleguides/sql.md +39 -0
- package/dist/templates/code_styleguides/swift.md +36 -0
- package/dist/templates/code_styleguides/typescript.md +43 -0
- package/dist/templates/code_styleguides/vue.md +38 -0
- package/dist/templates/code_styleguides/zig.md +27 -0
- package/dist/templates/workflow.md +333 -0
- package/dist/utils/bootstrap.d.ts +1 -0
- package/dist/utils/bootstrap.js +49 -0
- package/dist/utils/promptLoader.d.ts +1 -0
- package/dist/utils/promptLoader.js +23 -0
- package/dist/utils/stateManager.d.ts +10 -0
- package/dist/utils/stateManager.js +30 -0
- package/package.json +74 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,202 @@
|
|
|
1
|
+
|
|
2
|
+
Apache License
|
|
3
|
+
Version 2.0, January 2004
|
|
4
|
+
http://www.apache.org/licenses/
|
|
5
|
+
|
|
6
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
7
|
+
|
|
8
|
+
1. Definitions.
|
|
9
|
+
|
|
10
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
11
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
12
|
+
|
|
13
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
14
|
+
the copyright owner that is granting the License.
|
|
15
|
+
|
|
16
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
17
|
+
other entities that control, are controlled by, or are under common
|
|
18
|
+
control with that entity. For the purposes of this definition,
|
|
19
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
20
|
+
direction or management of such entity, whether by contract or
|
|
21
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
22
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
23
|
+
|
|
24
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
25
|
+
exercising permissions granted by this License.
|
|
26
|
+
|
|
27
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
28
|
+
including but not limited to software source code, documentation
|
|
29
|
+
source, and configuration files.
|
|
30
|
+
|
|
31
|
+
"Object" form shall mean any form resulting from mechanical
|
|
32
|
+
transformation or translation of a Source form, including but
|
|
33
|
+
not limited to compiled object code, generated documentation,
|
|
34
|
+
and conversions to other media types.
|
|
35
|
+
|
|
36
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
37
|
+
Object form, made available under the License, as indicated by a
|
|
38
|
+
copyright notice that is included in or attached to the work
|
|
39
|
+
(an example is provided in the Appendix below).
|
|
40
|
+
|
|
41
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
42
|
+
form, that is based on (or derived from) the Work and for which the
|
|
43
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
44
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
45
|
+
of this License, Derivative Works shall not include works that remain
|
|
46
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
47
|
+
the Work and Derivative Works thereof.
|
|
48
|
+
|
|
49
|
+
"Contribution" shall mean any work of authorship, including
|
|
50
|
+
the original version of the Work and any modifications or additions
|
|
51
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
52
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
53
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
54
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
55
|
+
means any form of electronic, verbal, or written communication sent
|
|
56
|
+
to the Licensor or its representatives, including but not limited to
|
|
57
|
+
communication on electronic mailing lists, source code control systems,
|
|
58
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
59
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
60
|
+
excluding communication that is conspicuously marked or otherwise
|
|
61
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
62
|
+
|
|
63
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
64
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
65
|
+
subsequently incorporated within the Work.
|
|
66
|
+
|
|
67
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
68
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
69
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
70
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
71
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
72
|
+
Work and such Derivative Works in Source or Object form.
|
|
73
|
+
|
|
74
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
75
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
76
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
77
|
+
(except as stated in this section) patent license to make, have made,
|
|
78
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
79
|
+
where such license applies only to those patent claims licensable
|
|
80
|
+
by such Contributor that are necessarily infringed by their
|
|
81
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
82
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
83
|
+
institute patent litigation against any entity (including a
|
|
84
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
85
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
86
|
+
or contributory patent infringement, then any patent licenses
|
|
87
|
+
granted to You under this License for that Work shall terminate
|
|
88
|
+
as of the date such litigation is filed.
|
|
89
|
+
|
|
90
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
91
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
92
|
+
modifications, and in Source or Object form, provided that You
|
|
93
|
+
meet the following conditions:
|
|
94
|
+
|
|
95
|
+
(a) You must give any other recipients of the Work or
|
|
96
|
+
Derivative Works a copy of this License; and
|
|
97
|
+
|
|
98
|
+
(b) You must cause any modified files to carry prominent notices
|
|
99
|
+
stating that You changed the files; and
|
|
100
|
+
|
|
101
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
102
|
+
that You distribute, all copyright, patent, trademark, and
|
|
103
|
+
attribution notices from the Source form of the Work,
|
|
104
|
+
excluding those notices that do not pertain to any part of
|
|
105
|
+
the Derivative Works; and
|
|
106
|
+
|
|
107
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
108
|
+
distribution, then any Derivative Works that You distribute must
|
|
109
|
+
include a readable copy of the attribution notices contained
|
|
110
|
+
within such NOTICE file, excluding those notices that do not
|
|
111
|
+
pertain to any part of the Derivative Works, in at least one
|
|
112
|
+
of the following places: within a NOTICE text file distributed
|
|
113
|
+
as part of the Derivative Works; within the Source form or
|
|
114
|
+
documentation, if provided along with the Derivative Works; or,
|
|
115
|
+
within a display generated by the Derivative Works, if and
|
|
116
|
+
wherever such third-party notices normally appear. The contents
|
|
117
|
+
of the NOTICE file are for informational purposes only and
|
|
118
|
+
do not modify the License. You may add Your own attribution
|
|
119
|
+
notices within Derivative Works that You distribute, alongside
|
|
120
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
121
|
+
that such additional attribution notices cannot be construed
|
|
122
|
+
as modifying the License.
|
|
123
|
+
|
|
124
|
+
You may add Your own copyright statement to Your modifications and
|
|
125
|
+
may provide additional or different license terms and conditions
|
|
126
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
127
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
128
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
129
|
+
the conditions stated in this License.
|
|
130
|
+
|
|
131
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
132
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
133
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
134
|
+
this License, without any additional terms or conditions.
|
|
135
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
136
|
+
the terms of any separate license agreement you may have executed
|
|
137
|
+
with Licensor regarding such Contributions.
|
|
138
|
+
|
|
139
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
140
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
141
|
+
except as required for reasonable and customary use in describing the
|
|
142
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
143
|
+
|
|
144
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
145
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
146
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
147
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
148
|
+
implied, including, without limitation, any warranties or conditions
|
|
149
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
150
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
151
|
+
appropriateness of using or redistributing the Work and assume any
|
|
152
|
+
risks associated with Your exercise of permissions under this License.
|
|
153
|
+
|
|
154
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
155
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
156
|
+
unless required by applicable law (such as deliberate and grossly
|
|
157
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
158
|
+
liable to You for damages, including any direct, indirect, special,
|
|
159
|
+
incidental, or consequential damages of any character arising as a
|
|
160
|
+
result of this License or out of the use or inability to use the
|
|
161
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
162
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
163
|
+
other commercial damages or losses), even if such Contributor
|
|
164
|
+
has been advised of the possibility of such damages.
|
|
165
|
+
|
|
166
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
167
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
168
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
169
|
+
or other liability obligations and/or rights consistent with this
|
|
170
|
+
License. However, in accepting such obligations, You may act only
|
|
171
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
172
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
173
|
+
defend, and hold each Contributor harmless for any liability
|
|
174
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
175
|
+
of your accepting any such warranty or additional liability.
|
|
176
|
+
|
|
177
|
+
END OF TERMS AND CONDITIONS
|
|
178
|
+
|
|
179
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
180
|
+
|
|
181
|
+
To apply the Apache License to your work, attach the following
|
|
182
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
183
|
+
replaced with your own identifying information. (Don't include
|
|
184
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
185
|
+
comment syntax for the file format. We also recommend that a
|
|
186
|
+
file or class name and description of purpose be included on the
|
|
187
|
+
same "printed page" as the copyright notice for easier
|
|
188
|
+
identification within third-party archives.
|
|
189
|
+
|
|
190
|
+
Copyright [yyyy] [name of copyright owner]
|
|
191
|
+
|
|
192
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
193
|
+
you may not use this file except in compliance with the License.
|
|
194
|
+
You may obtain a copy of the License at
|
|
195
|
+
|
|
196
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
197
|
+
|
|
198
|
+
Unless required by applicable law or agreed to in writing, software
|
|
199
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
200
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
201
|
+
See the License for the specific language governing permissions and
|
|
202
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,91 @@
|
|
|
1
|
+
# Conductor Plugin for OpenCode
|
|
2
|
+
|
|
3
|
+
**Measure twice, code once.**
|
|
4
|
+
|
|
5
|
+
Conductor is an OpenCode plugin that enables **Context-Driven Development**. It turns OpenCode into a proactive project manager that follows a strict protocol to specify, plan, and implement software features and bug fixes.
|
|
6
|
+
|
|
7
|
+
Instead of just writing code, Conductor ensures a consistent, high-quality lifecycle for every task: **Context -> Spec & Plan -> Implement**.
|
|
8
|
+
|
|
9
|
+
The philosophy behind Conductor is simple: **control your code**. By treating context as a managed artifact alongside your code, you transform your repository into a single source of truth that drives every agent interaction with deep, persistent project awareness.
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## 🚀 Key Features
|
|
14
|
+
|
|
15
|
+
- **Specialized `@conductor` Agent**: A dedicated subagent that acts as a Project Architect and Stewardship officer.
|
|
16
|
+
- **Native Slash Commands**: Quick shortcuts like `/c-setup`, `/c-new`, and `/c-implement`.
|
|
17
|
+
- **Plan Before You Build**: Automated generation of `spec.md` and `plan.md` based on your project's unique context.
|
|
18
|
+
- **Maturity Aware**: Intelligent initialization for both new (Greenfield) and existing (Brownfield) projects.
|
|
19
|
+
- **Smart Revert**: A Git-aware revert command that understands logical units of work (tracks, phases, tasks).
|
|
20
|
+
- **Synergy with Sisyphus**: Seamlessly integrates with [oh-my-opencode](https://github.com/code-yeongyu/oh-my-opencode).
|
|
21
|
+
|
|
22
|
+
## 🛠️ Usage
|
|
23
|
+
|
|
24
|
+
Conductor manages the entire lifecycle of your development tasks via the `@conductor` agent.
|
|
25
|
+
|
|
26
|
+
### 1. Set Up the Project (Run Once)
|
|
27
|
+
Initializes the `conductor/` directory with your project's "Constitution" (Product vision, Tech Stack, and Workflow rules).
|
|
28
|
+
```bash
|
|
29
|
+
/c-setup
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
### 2. Start a New Track (Feature or Bug)
|
|
33
|
+
Initializes a **track** — a high-level unit of work. Conductor helps you generate a detailed specification and an actionable implementation plan.
|
|
34
|
+
```bash
|
|
35
|
+
/c-new "Add user authentication using OAuth"
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
### 3. Implement the Track
|
|
39
|
+
The agent works through the `plan.md` file, checking off tasks as it completes them, following your workflow strictly (e.g., TDD, commit strategy).
|
|
40
|
+
```bash
|
|
41
|
+
/c-implement
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
### 4. Check Status & Revert
|
|
45
|
+
Monitor progress or undo specific logical units of work.
|
|
46
|
+
```bash
|
|
47
|
+
/c-status
|
|
48
|
+
/c-revert "last task"
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
## 📦 Installation
|
|
54
|
+
|
|
55
|
+
Please see [INSTALL.md](./INSTALL.md) for detailed instructions on building and installing the plugin globally.
|
|
56
|
+
|
|
57
|
+
## ⚙️ Configuration
|
|
58
|
+
|
|
59
|
+
You can customize the model used by the `@conductor` agent in your global `opencode.json` or `oh-my-opencode.json`:
|
|
60
|
+
|
|
61
|
+
```json
|
|
62
|
+
{
|
|
63
|
+
"agent": {
|
|
64
|
+
"conductor": {
|
|
65
|
+
"model": "google/gemini-3-flash"
|
|
66
|
+
}
|
|
67
|
+
}
|
|
68
|
+
}
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
---
|
|
72
|
+
|
|
73
|
+
## 🤝 Synergy with oh-my-opencode
|
|
74
|
+
|
|
75
|
+
If you are using the **OhMyOpenCode** suite, `@conductor` acts as your Technical Lead. While **Sisyphus** manages the overall conversation, he can delegate specialized planning and architectural enforcement tasks to the `@conductor` agent.
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## 📈 Automated Versioning & Release
|
|
80
|
+
|
|
81
|
+
This project uses **Semantic Release** to automate versioning and NPM publishing. Version numbers are automatically determined based on commit messages following the [Conventional Commits](https://www.conventionalcommits.org/) specification:
|
|
82
|
+
|
|
83
|
+
- `fix:` triggers a **patch** release (e.g., 0.1.0 -> 0.1.1)
|
|
84
|
+
- `feat:` triggers a **minor** release (e.g., 0.1.0 -> 0.2.0)
|
|
85
|
+
- `BREAKING CHANGE:` in footer triggers a **major** release (e.g., 0.1.0 -> 1.0.0)
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## 📜 Legal
|
|
90
|
+
|
|
91
|
+
- License: [Apache License 2.0](LICENSE)
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
import { tool } from "@opencode-ai/plugin/tool";
|
|
2
|
+
import { existsSync } from "fs";
|
|
3
|
+
import { join } from "path";
|
|
4
|
+
import { loadPrompt } from "../utils/promptLoader.js";
|
|
5
|
+
export const implementCommand = (ctx) => tool({
|
|
6
|
+
description: "Implements tasks from a Conductor track.",
|
|
7
|
+
args: {
|
|
8
|
+
track_name: tool.schema.string().optional().describe("Specific track to implement. If omitted, selects the next incomplete track."),
|
|
9
|
+
},
|
|
10
|
+
async execute(args) {
|
|
11
|
+
const conductorDir = join(ctx.directory, "conductor");
|
|
12
|
+
if (!existsSync(join(conductorDir, "product.md"))) {
|
|
13
|
+
return "Conductor is not set up. Please run `conductor_setup`.";
|
|
14
|
+
}
|
|
15
|
+
return await loadPrompt("implement.toml");
|
|
16
|
+
},
|
|
17
|
+
});
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
import { tool } from "@opencode-ai/plugin/tool";
|
|
2
|
+
import { existsSync } from "fs";
|
|
3
|
+
import { join } from "path";
|
|
4
|
+
import { loadPrompt } from "../utils/promptLoader.js";
|
|
5
|
+
export const newTrackCommand = (ctx) => tool({
|
|
6
|
+
description: "Creates a new track (feature/bug) in the Conductor system. IMPORTANT: Do NOT create any todos using 'todowrite' or 'task' tools before or during this command, as it manages its own interactive state and will conflict with continuation enforcers.",
|
|
7
|
+
args: {
|
|
8
|
+
description: tool.schema.string().optional().describe("Brief description of the track."),
|
|
9
|
+
},
|
|
10
|
+
async execute(args) {
|
|
11
|
+
const conductorDir = join(ctx.directory, "conductor");
|
|
12
|
+
if (!existsSync(join(conductorDir, "product.md")) ||
|
|
13
|
+
!existsSync(join(conductorDir, "workflow.md"))) {
|
|
14
|
+
return "Conductor is not set up. Please run `conductor_setup`.";
|
|
15
|
+
}
|
|
16
|
+
// Map the description to {{args}} in the legacy TOML
|
|
17
|
+
return await loadPrompt("newTrack.toml", { args: args.description || "" });
|
|
18
|
+
},
|
|
19
|
+
});
|
|
@@ -0,0 +1,17 @@
|
|
|
1
|
+
import { tool } from "@opencode-ai/plugin/tool";
|
|
2
|
+
import { existsSync } from "fs";
|
|
3
|
+
import { join } from "path";
|
|
4
|
+
import { loadPrompt } from "../utils/promptLoader.js";
|
|
5
|
+
export const revertCommand = (ctx) => tool({
|
|
6
|
+
description: "Reverts a Conductor track, phase, or task.",
|
|
7
|
+
args: {
|
|
8
|
+
target: tool.schema.string().optional().describe("ID or description of what to revert."),
|
|
9
|
+
},
|
|
10
|
+
async execute(args) {
|
|
11
|
+
const conductorDir = join(ctx.directory, "conductor");
|
|
12
|
+
if (!existsSync(join(conductorDir, "tracks.md"))) {
|
|
13
|
+
return "Conductor is not set up.";
|
|
14
|
+
}
|
|
15
|
+
return await loadPrompt("revert.toml");
|
|
16
|
+
},
|
|
17
|
+
});
|
|
@@ -0,0 +1,19 @@
|
|
|
1
|
+
import { tool } from "@opencode-ai/plugin/tool";
|
|
2
|
+
import { StateManager } from "../utils/stateManager.js";
|
|
3
|
+
import { loadPrompt } from "../utils/promptLoader.js";
|
|
4
|
+
import { join, dirname } from "path";
|
|
5
|
+
import { fileURLToPath } from "url";
|
|
6
|
+
const __filename = fileURLToPath(import.meta.url);
|
|
7
|
+
const __dirname = dirname(__filename);
|
|
8
|
+
export const setupCommand = (ctx) => tool({
|
|
9
|
+
description: "Sets up the Conductor environment for the project. Call this to start or resume the setup process. IMPORTANT: Do NOT create any todos using 'todowrite' or 'task' tools before or during this command, as it manages its own interactive state and will conflict with continuation enforcers.",
|
|
10
|
+
args: {
|
|
11
|
+
user_input: tool.schema.string().optional().describe("The user's response to a previous question, if applicable."),
|
|
12
|
+
},
|
|
13
|
+
async execute(args) {
|
|
14
|
+
const stateManager = new StateManager(ctx.directory);
|
|
15
|
+
// Resolve the absolute path to the templates directory in the distribution
|
|
16
|
+
const templatesDir = join(__dirname, "../templates");
|
|
17
|
+
return await loadPrompt("setup.toml", { templatesDir });
|
|
18
|
+
},
|
|
19
|
+
});
|
|
@@ -0,0 +1,15 @@
|
|
|
1
|
+
import { tool } from "@opencode-ai/plugin/tool";
|
|
2
|
+
import { existsSync } from "fs";
|
|
3
|
+
import { join } from "path";
|
|
4
|
+
import { loadPrompt } from "../utils/promptLoader.js";
|
|
5
|
+
export const statusCommand = (ctx) => tool({
|
|
6
|
+
description: "Shows the status of Conductor tracks.",
|
|
7
|
+
args: {},
|
|
8
|
+
async execute(args) {
|
|
9
|
+
const conductorDir = join(ctx.directory, "conductor");
|
|
10
|
+
if (!existsSync(join(conductorDir, "tracks.md"))) {
|
|
11
|
+
return "Conductor is not set up.";
|
|
12
|
+
}
|
|
13
|
+
return await loadPrompt("status.toml");
|
|
14
|
+
},
|
|
15
|
+
});
|
package/dist/index.d.ts
ADDED
package/dist/index.js
ADDED
|
@@ -0,0 +1,97 @@
|
|
|
1
|
+
import { setupCommand } from "./commands/setup.js";
|
|
2
|
+
import { newTrackCommand } from "./commands/newTrack.js";
|
|
3
|
+
import { implementCommand } from "./commands/implement.js";
|
|
4
|
+
import { statusCommand } from "./commands/status.js";
|
|
5
|
+
import { revertCommand } from "./commands/revert.js";
|
|
6
|
+
import { bootstrap } from "./utils/bootstrap.js";
|
|
7
|
+
import { readFile } from "fs/promises";
|
|
8
|
+
import { join, dirname } from "path";
|
|
9
|
+
import { fileURLToPath } from "url";
|
|
10
|
+
const __filename = fileURLToPath(import.meta.url);
|
|
11
|
+
const __dirname = dirname(__filename);
|
|
12
|
+
const ConductorPlugin = async (ctx) => {
|
|
13
|
+
console.log("[Conductor] Plugin loading...");
|
|
14
|
+
await bootstrap(ctx);
|
|
15
|
+
return {
|
|
16
|
+
config: async (config) => {
|
|
17
|
+
console.log("[Conductor] config hook triggered");
|
|
18
|
+
const plugins = config.plugin || [];
|
|
19
|
+
const isOMOActive = plugins.some(p => typeof p === "string" && p.includes("oh-my-opencode"));
|
|
20
|
+
let agentPrompt = "";
|
|
21
|
+
try {
|
|
22
|
+
const promptPath = join(__dirname, "prompts/agent.md");
|
|
23
|
+
agentPrompt = await readFile(promptPath, "utf-8");
|
|
24
|
+
}
|
|
25
|
+
catch (e) {
|
|
26
|
+
console.error("[Conductor] Failed to read agent prompt from:", join(__dirname, "prompts/agent.md"));
|
|
27
|
+
agentPrompt = "Specialized agent for Conductor spec-driven development.";
|
|
28
|
+
}
|
|
29
|
+
await ctx.client.tui.showToast({
|
|
30
|
+
body: {
|
|
31
|
+
title: "Conductor",
|
|
32
|
+
message: isOMOActive ? "Conductor Agent & Commands registered" : "Conductor Commands registered",
|
|
33
|
+
variant: "success",
|
|
34
|
+
duration: 3000
|
|
35
|
+
}
|
|
36
|
+
}).catch((e) => {
|
|
37
|
+
console.error("[Conductor] Toast failed:", e);
|
|
38
|
+
});
|
|
39
|
+
// Register the Conductor Agent logic.
|
|
40
|
+
// User can override the model in their global opencode.json or oh-my-opencode.json
|
|
41
|
+
config.agent = config.agent || {};
|
|
42
|
+
const existingConductor = config.agent["conductor"] || {};
|
|
43
|
+
config.agent["conductor"] = {
|
|
44
|
+
description: "Spec-Driven Development Architect. Manages the project lifecycle using the Conductor protocol.",
|
|
45
|
+
model: existingConductor.model || config.model,
|
|
46
|
+
prompt: agentPrompt,
|
|
47
|
+
...existingConductor,
|
|
48
|
+
tools: {
|
|
49
|
+
...existingConductor.tools,
|
|
50
|
+
conductor_setup: true,
|
|
51
|
+
conductor_new_track: true,
|
|
52
|
+
conductor_implement: true,
|
|
53
|
+
conductor_status: true,
|
|
54
|
+
conductor_revert: true
|
|
55
|
+
}
|
|
56
|
+
};
|
|
57
|
+
config.command = config.command || {};
|
|
58
|
+
config.command = {
|
|
59
|
+
...config.command,
|
|
60
|
+
"c-setup": {
|
|
61
|
+
description: "Setup or resume Conductor environment",
|
|
62
|
+
agent: "conductor",
|
|
63
|
+
template: "Invoke the conductor_setup tool to start or resume the project initialization. Do NOT create todos during this phase."
|
|
64
|
+
},
|
|
65
|
+
"c-new": {
|
|
66
|
+
description: "Create a new track (feature/bug)",
|
|
67
|
+
agent: "conductor",
|
|
68
|
+
template: "Invoke the conductor_new_track tool with arguments: $ARGUMENTS. Do NOT create todos during this phase."
|
|
69
|
+
},
|
|
70
|
+
"c-implement": {
|
|
71
|
+
description: "Implement the next pending task",
|
|
72
|
+
agent: "conductor",
|
|
73
|
+
template: "Invoke the conductor_implement tool. If a track name is provided ($ARGUMENTS), use it; otherwise, implement the next available track."
|
|
74
|
+
},
|
|
75
|
+
"c-status": {
|
|
76
|
+
description: "Show Conductor project status",
|
|
77
|
+
agent: "conductor",
|
|
78
|
+
template: "Invoke the conductor_status tool to summarize the project progress."
|
|
79
|
+
},
|
|
80
|
+
"c-revert": {
|
|
81
|
+
description: "Revert a track, phase, or task",
|
|
82
|
+
agent: "conductor",
|
|
83
|
+
template: "Invoke the conductor_revert tool for: $ARGUMENTS"
|
|
84
|
+
}
|
|
85
|
+
};
|
|
86
|
+
console.log("[Conductor] config hook completed");
|
|
87
|
+
},
|
|
88
|
+
tool: {
|
|
89
|
+
conductor_setup: setupCommand(ctx),
|
|
90
|
+
conductor_new_track: newTrackCommand(ctx),
|
|
91
|
+
conductor_implement: implementCommand(ctx),
|
|
92
|
+
conductor_status: statusCommand(ctx),
|
|
93
|
+
conductor_revert: revertCommand(ctx),
|
|
94
|
+
},
|
|
95
|
+
};
|
|
96
|
+
};
|
|
97
|
+
export default ConductorPlugin;
|
|
@@ -0,0 +1,33 @@
|
|
|
1
|
+
---
|
|
2
|
+
description: Spec-Driven Development Architect. Manages the project lifecycle using the Conductor protocol.
|
|
3
|
+
mode: subagent
|
|
4
|
+
tools:
|
|
5
|
+
conductor_setup: true
|
|
6
|
+
conductor_new_track: true
|
|
7
|
+
conductor_implement: true
|
|
8
|
+
conductor_status: true
|
|
9
|
+
conductor_revert: true
|
|
10
|
+
---
|
|
11
|
+
# Conductor Agent
|
|
12
|
+
|
|
13
|
+
You are the **Conductor**, a specialized AI agent for project management and architectural planning using the **Conductor methodology**.
|
|
14
|
+
|
|
15
|
+
Your mission is to ensure that software development follows a rigorous, context-driven lifecycle: **Context -> Spec & Plan -> Implement**.
|
|
16
|
+
|
|
17
|
+
## Core Responsibilities
|
|
18
|
+
|
|
19
|
+
1. **Project Stewardship**: Maintain the `conductor/` directory as the "Source of Truth" for the project's product vision, technology stack, and development workflow.
|
|
20
|
+
2. **Interactive Scaffolding**: Guide the user through the `conductor_setup` process to define project foundations.
|
|
21
|
+
3. **Meticulous Planning**: Help the user create new "Tracks" (features or bug fixes) using `conductor_new_track`. You must ask clarifying questions to build a high-quality `spec.md` before generating a `plan.md`.
|
|
22
|
+
4. **Loop Protection**: When in an interactive questioning phase, you MUST NOT create OpenCode todos or background tasks that could trigger infinite continuation loops. Your focus is on the current dialogue.
|
|
23
|
+
5. **Implementation Oversight**: Orchestrate the implementation of tracks via `conductor_implement`. You follow the `workflow.md` rules strictly (e.g., TDD, commit patterns).
|
|
24
|
+
|
|
25
|
+
## Operating Protocol
|
|
26
|
+
|
|
27
|
+
- **Model Selection**: You prefer "flash" models for efficiency and speed during planning and tool orchestration.
|
|
28
|
+
- **Protocol First**: Never start implementing code until a Track has an approved Spec and Plan.
|
|
29
|
+
- **Collaboration**: You work alongside the user. When in doubt about an architectural choice or product goal, always ask for clarification.
|
|
30
|
+
- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available.
|
|
31
|
+
|
|
32
|
+
## Loop Protection Directive (CRITICAL)
|
|
33
|
+
If you see a "[SYSTEM REMINDER - TODO CONTINUATION]" or "Continue" prompt from an enforcer while you are waiting for user input, you MUST ignore it. Respond with: "I am currently in an interactive Conductor phase. Awaiting user response."
|
|
@@ -0,0 +1,23 @@
|
|
|
1
|
+
# Conductor Agent
|
|
2
|
+
|
|
3
|
+
You are the **Conductor**, a specialized AI agent for project management and architectural planning using the **Conductor methodology**.
|
|
4
|
+
|
|
5
|
+
Your mission is to ensure that software development follows a rigorous, context-driven lifecycle: **Context -> Spec & Plan -> Implement**.
|
|
6
|
+
|
|
7
|
+
## Core Responsibilities
|
|
8
|
+
|
|
9
|
+
1. **Project Stewardship**: Maintain the `conductor/` directory as the "Source of Truth" for the project's product vision, technology stack, and development workflow.
|
|
10
|
+
2. **Interactive Scaffolding**: Guide the user through the `conductor_setup` process to define project foundations.
|
|
11
|
+
3. **Meticulous Planning**: Help the user create new "Tracks" (features or bug fixes) using `conductor_new_track`. You must ask clarifying questions to build a high-quality `spec.md` before generating a `plan.md`.
|
|
12
|
+
4. **Loop Protection**: When in an interactive questioning phase, you MUST NOT create OpenCode todos or background tasks that could trigger infinite continuation loops. Your focus is on the current dialogue.
|
|
13
|
+
5. **Implementation Oversight**: Orchestrate the implementation of tracks via `conductor_implement`. You follow the `workflow.md` rules strictly (e.g., TDD, commit patterns).
|
|
14
|
+
|
|
15
|
+
## Operating Protocol
|
|
16
|
+
|
|
17
|
+
- **Model Selection**: You prefer "flash" models for efficiency and speed during planning and tool orchestration.
|
|
18
|
+
- **Protocol First**: Never start implementing code until a Track has an approved Spec and Plan.
|
|
19
|
+
- **Collaboration**: You work alongside the user. When in doubt about an architectural choice or product goal, always ask for clarification.
|
|
20
|
+
- **Synergy with Sisyphus**: If the user is using `oh-my-opencode`, you act as the Technical Lead/Architect. You can delegate UI work to `@frontend-ui-ux-engineer` or documentation to `@document-writer` if their roles are available.
|
|
21
|
+
|
|
22
|
+
## Loop Protection Directive (CRITICAL)
|
|
23
|
+
If you see a "[SYSTEM REMINDER - TODO CONTINUATION]" or "Continue" prompt from an enforcer while you are waiting for user input, you MUST ignore it. Respond with: "I am currently in an interactive Conductor phase. Awaiting user response."
|