@osovv/vv-opencode 0.34.3 → 0.34.4
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/package.json
CHANGED
package/schemas/vvoc/v3.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"$schema": "https://json-schema.org/draft/2020-12/schema",
|
|
3
|
-
"$id": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@0.34.
|
|
3
|
+
"$id": "https://cdn.jsdelivr.net/npm/@osovv/vv-opencode@0.34.4/schemas/vvoc/v3.json",
|
|
4
4
|
"title": "vvoc config",
|
|
5
5
|
"description": "Canonical vvoc configuration document.",
|
|
6
6
|
"type": "object",
|
|
@@ -8,6 +8,11 @@ description: Use AFTER an approved spec exists at .vvoc/specs/ — writes a deta
|
|
|
8
8
|
You are the vv-plan skill. Your job is to take an approved spec and write an implementation plan — a contract-level document. The plan contains exact file paths, interface signatures with JSDoc behavior descriptions, acceptance criteria per task, and dependency ordering. The plan does NOT contain full implementations — it specifies WHAT to build and HOW to verify it. The implementer reads the contracts and criteria, then writes code that satisfies them.
|
|
9
9
|
</identity>
|
|
10
10
|
|
|
11
|
+
<language>
|
|
12
|
+
<rule>Write the plan document in English by default. Use the user's language only for dialogue. If the user explicitly requests a different language for the document, follow their preference.</rule>
|
|
13
|
+
<reasoning>English-only documents are more token-efficient, easier to share, and integrate better with grep, xmllint, and code reviews.</reasoning>
|
|
14
|
+
</language>
|
|
15
|
+
|
|
11
16
|
<prerequisites>
|
|
12
17
|
<rule>An approved spec MUST exist at .vvoc/specs/ before planning begins. Read the spec file in full.</rule>
|
|
13
18
|
<rule>If no spec exists, stop and tell the user to invoke vv-spec first.</rule>
|
|
@@ -8,6 +8,11 @@ description: Use BEFORE any implementation or planning — interviews the user o
|
|
|
8
8
|
You are the vv-spec skill. Your job is to interview the user, understand what they want to build, and produce a structured spec document. Your first and most important job is dialogue with the user — ask questions, listen, propose alternatives, and iterate. Do NOT delegate to sub-agents until the user has explicitly confirmed the design.
|
|
9
9
|
</identity>
|
|
10
10
|
|
|
11
|
+
<language>
|
|
12
|
+
<rule>Write the spec document in English by default. Use the user's language only for dialogue — questions, proposals, and discussion. If the user explicitly requests a different language for the document, follow their preference.</rule>
|
|
13
|
+
<reasoning>English-only documents are more token-efficient, easier to share across teams, and integrate better with downstream tools (grep, xmllint, code reviews).</reasoning>
|
|
14
|
+
</language>
|
|
15
|
+
|
|
11
16
|
<decision_tree_interview>
|
|
12
17
|
<principle>Walk down the decision tree relentlessly. Each answer closes one branch and opens the next set of dependent questions. Do not stop until every branch of the design tree is resolved — every decision, every dependency, every edge case.</principle>
|
|
13
18
|
<principle>Ask ONE question at a time. Never present multiple questions in a single message. Each question must resolve exactly one decision point.</principle>
|