@soleri/forge 9.14.4 → 9.16.7
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/dist/agent-schema.d.ts +2 -2
- package/dist/compose-claude-md.js +5 -2
- package/dist/compose-claude-md.js.map +1 -1
- package/dist/index.js +0 -0
- package/dist/lib.d.ts +1 -0
- package/dist/lib.js +1 -0
- package/dist/lib.js.map +1 -1
- package/dist/scaffold-filetree.js +27 -0
- package/dist/scaffold-filetree.js.map +1 -1
- package/dist/scaffolder.js +10 -0
- package/dist/scaffolder.js.map +1 -1
- package/dist/skills/soleri-agent-dev/SKILL.md +1 -0
- package/dist/skills/soleri-agent-guide/SKILL.md +1 -0
- package/dist/skills/soleri-agent-issues/SKILL.md +1 -0
- package/dist/skills/soleri-agent-mode/SKILL.md +173 -0
- package/dist/skills/soleri-agent-persona/SKILL.md +1 -0
- package/dist/skills/soleri-brain-debrief/SKILL.md +1 -0
- package/dist/skills/soleri-brainstorming/SKILL.md +1 -0
- package/dist/skills/soleri-build-skill/SKILL.md +2 -0
- package/dist/skills/soleri-code-patrol/SKILL.md +1 -0
- package/dist/skills/soleri-context-resume/SKILL.md +1 -0
- package/dist/skills/soleri-curator/SKILL.md +66 -0
- package/dist/skills/soleri-deep-review/SKILL.md +1 -0
- package/dist/skills/soleri-deliver-and-ship/SKILL.md +1 -0
- package/dist/skills/soleri-discovery-phase/SKILL.md +1 -0
- package/dist/skills/soleri-dream/SKILL.md +31 -1
- package/dist/skills/soleri-env-setup/SKILL.md +1 -0
- package/dist/skills/soleri-executing-plans/SKILL.md +1 -0
- package/dist/skills/soleri-finishing-a-development-branch/SKILL.md +1 -0
- package/dist/skills/soleri-fix-and-learn/SKILL.md +1 -0
- package/dist/skills/soleri-health-check/SKILL.md +1 -0
- package/dist/skills/soleri-intake/SKILL.md +100 -0
- package/dist/skills/soleri-knowledge-harvest/SKILL.md +1 -0
- package/dist/skills/soleri-loop/SKILL.md +69 -0
- package/dist/skills/soleri-mcp-doctor/SKILL.md +1 -0
- package/dist/skills/soleri-onboard-me/SKILL.md +1 -0
- package/dist/skills/soleri-orchestrate/SKILL.md +70 -0
- package/dist/skills/soleri-parallel-execute/SKILL.md +1 -0
- package/dist/skills/soleri-research-scout/SKILL.md +1 -0
- package/dist/skills/soleri-retrospective/SKILL.md +1 -0
- package/dist/skills/soleri-second-opinion/SKILL.md +1 -0
- package/dist/skills/soleri-subagent-driven-development/SKILL.md +1 -0
- package/dist/skills/soleri-systematic-debugging/SKILL.md +1 -0
- package/dist/skills/soleri-test-driven-development/SKILL.md +1 -0
- package/dist/skills/soleri-using-git-worktrees/SKILL.md +1 -0
- package/dist/skills/soleri-vault-capture/SKILL.md +6 -5
- package/dist/skills/soleri-vault-curate/SKILL.md +1 -0
- package/dist/skills/soleri-vault-navigator/SKILL.md +1 -0
- package/dist/skills/soleri-vault-smells/SKILL.md +1 -0
- package/dist/skills/soleri-verification-before-completion/SKILL.md +1 -0
- package/dist/skills/soleri-writing-plans/SKILL.md +6 -3
- package/dist/skills/soleri-yolo-mode/SKILL.md +1 -0
- package/dist/templates/claude-md-template.js +2 -29
- package/dist/templates/claude-md-template.js.map +1 -1
- package/dist/templates/package-json.js +2 -0
- package/dist/templates/package-json.js.map +1 -1
- package/dist/templates/setup-script.js +6 -63
- package/dist/templates/setup-script.js.map +1 -1
- package/dist/templates/shared-rules.js +11 -4
- package/dist/templates/shared-rules.js.map +1 -1
- package/dist/templates/skills.d.ts +13 -0
- package/dist/templates/skills.js +55 -3
- package/dist/templates/skills.js.map +1 -1
- package/dist/types.d.ts +2 -2
- package/package.json +1 -1
- package/src/__tests__/knowledge-installer.test.ts +1 -1
- package/src/__tests__/scaffold-filetree.test.ts +1 -1
- package/src/__tests__/scaffolder.test.ts +143 -111
- package/src/compose-claude-md.ts +5 -1
- package/src/lib.ts +1 -0
- package/src/scaffold-filetree.ts +33 -0
- package/src/scaffolder.ts +10 -0
- package/src/skills/soleri-agent-dev/SKILL.md +1 -0
- package/src/skills/soleri-agent-guide/SKILL.md +1 -0
- package/src/skills/soleri-agent-issues/SKILL.md +1 -0
- package/src/skills/soleri-agent-mode/SKILL.md +173 -0
- package/src/skills/soleri-agent-persona/SKILL.md +1 -0
- package/src/skills/soleri-brain-debrief/SKILL.md +1 -0
- package/src/skills/soleri-brainstorming/SKILL.md +1 -0
- package/src/skills/soleri-build-skill/SKILL.md +2 -0
- package/src/skills/soleri-code-patrol/SKILL.md +1 -0
- package/src/skills/soleri-context-resume/SKILL.md +1 -0
- package/src/skills/soleri-curator/SKILL.md +66 -0
- package/src/skills/soleri-deep-review/SKILL.md +1 -0
- package/src/skills/soleri-deliver-and-ship/SKILL.md +1 -0
- package/src/skills/soleri-discovery-phase/SKILL.md +1 -0
- package/src/skills/soleri-dream/SKILL.md +31 -1
- package/src/skills/soleri-env-setup/SKILL.md +1 -0
- package/src/skills/soleri-executing-plans/SKILL.md +1 -0
- package/src/skills/soleri-finishing-a-development-branch/SKILL.md +1 -0
- package/src/skills/soleri-fix-and-learn/SKILL.md +1 -0
- package/src/skills/soleri-health-check/SKILL.md +1 -0
- package/src/skills/soleri-intake/SKILL.md +100 -0
- package/src/skills/soleri-knowledge-harvest/SKILL.md +1 -0
- package/src/skills/soleri-loop/SKILL.md +69 -0
- package/src/skills/soleri-mcp-doctor/SKILL.md +1 -0
- package/src/skills/soleri-onboard-me/SKILL.md +1 -0
- package/src/skills/soleri-orchestrate/SKILL.md +70 -0
- package/src/skills/soleri-parallel-execute/SKILL.md +1 -0
- package/src/skills/soleri-research-scout/SKILL.md +1 -0
- package/src/skills/soleri-retrospective/SKILL.md +1 -0
- package/src/skills/soleri-second-opinion/SKILL.md +1 -0
- package/src/skills/soleri-subagent-driven-development/SKILL.md +1 -0
- package/src/skills/soleri-systematic-debugging/SKILL.md +1 -0
- package/src/skills/soleri-test-driven-development/SKILL.md +1 -0
- package/src/skills/soleri-using-git-worktrees/SKILL.md +1 -0
- package/src/skills/soleri-vault-capture/SKILL.md +6 -5
- package/src/skills/soleri-vault-curate/SKILL.md +1 -0
- package/src/skills/soleri-vault-navigator/SKILL.md +1 -0
- package/src/skills/soleri-vault-smells/SKILL.md +1 -0
- package/src/skills/soleri-verification-before-completion/SKILL.md +1 -0
- package/src/skills/soleri-writing-plans/SKILL.md +6 -3
- package/src/skills/soleri-yolo-mode/SKILL.md +1 -0
- package/src/templates/claude-md-template.ts +2 -50
- package/src/templates/package-json.ts +2 -0
- package/src/templates/setup-script.ts +6 -63
- package/src/templates/shared-rules.ts +11 -4
- package/src/templates/skills.ts +63 -3
- package/vitest.config.ts +2 -1
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: soleri-build-skill
|
|
3
|
+
tier: default
|
|
3
4
|
description: >
|
|
4
5
|
Use when creating a new skill, updating an existing skill, or scaffolding a skill
|
|
5
6
|
template for a Soleri agent. Triggers on "create a skill", "new skill", "build skill",
|
|
@@ -24,6 +25,7 @@ Skills live in two places:
|
|
|
24
25
|
```yaml
|
|
25
26
|
---
|
|
26
27
|
name: soleri-{skill-name}
|
|
28
|
+
tier: default
|
|
27
29
|
description: >
|
|
28
30
|
Use when the user says "trigger1", "trigger2", "trigger3",
|
|
29
31
|
or wants to [brief purpose]. [One sentence about what the skill does].
|
|
@@ -0,0 +1,66 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: soleri-curator
|
|
3
|
+
tier: default
|
|
4
|
+
description: >
|
|
5
|
+
Use when the user says "curator status", "vault health", "how is the vault",
|
|
6
|
+
"curator health", "check vault quality", or "what needs grooming".
|
|
7
|
+
Quick vault health check with targeted grooming recommendations.
|
|
8
|
+
For full maintenance (dedup, archive, consolidate), use vault-curate.
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Curator — Vault Health and Quick Grooming
|
|
12
|
+
|
|
13
|
+
Get a rapid health snapshot of the vault and run targeted grooming on specific entries. Use this for regular check-ins and spot fixes. For deep maintenance (dedup, archive stale, full consolidation) use the `vault-curate` skill.
|
|
14
|
+
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- Quick "how is the vault doing?" check
|
|
18
|
+
- After a few capture sessions to verify entry quality
|
|
19
|
+
- Spot-grooming specific entries or domains
|
|
20
|
+
- Before starting a big research session
|
|
21
|
+
|
|
22
|
+
## Orchestration
|
|
23
|
+
|
|
24
|
+
### Step 1: Health Snapshot
|
|
25
|
+
|
|
26
|
+
```
|
|
27
|
+
YOUR_AGENT_curator op:curator_health
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
Present results as a status table:
|
|
31
|
+
|
|
32
|
+
| Metric | Value | Status |
|
|
33
|
+
| ----------------------- | ------------------ | ------------- |
|
|
34
|
+
| **Total entries** | {totalEntries} | — |
|
|
35
|
+
| **Quality score** | {qualityScore}/100 | {ok/warn/bad} |
|
|
36
|
+
| **Stale entries** | {staleCount} | — |
|
|
37
|
+
| **Duplicates detected** | {duplicateCount} | — |
|
|
38
|
+
| **Grooming needed** | {needsGrooming} | — |
|
|
39
|
+
|
|
40
|
+
If health score < 70 or duplicates > 10, recommend running `vault-curate`.
|
|
41
|
+
|
|
42
|
+
### Step 2: Curator Status
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
YOUR_AGENT_curator op:curator_status
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Show last grooming date, entries processed, and any pending actions.
|
|
49
|
+
|
|
50
|
+
### Step 3: Targeted Grooming (optional)
|
|
51
|
+
|
|
52
|
+
If specific entries need attention:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
YOUR_AGENT_curator op:curator_groom
|
|
56
|
+
params: {
|
|
57
|
+
entryIds: ["<id1>", "<id2>"],
|
|
58
|
+
tags: ["<suggested-tag>"]
|
|
59
|
+
}
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
Report how many entries were updated.
|
|
63
|
+
|
|
64
|
+
## Exit Criteria
|
|
65
|
+
|
|
66
|
+
Health snapshot presented. If issues found, user is informed with a clear recommendation to run `vault-curate` for full maintenance or `curator_groom` for spot fixes.
|
|
@@ -1,5 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: soleri-dream
|
|
3
|
+
tier: default
|
|
3
4
|
description: >
|
|
4
5
|
Use when the user says "dream", "consolidate memory", "clean up memory",
|
|
5
6
|
"memory cleanup", or "dream status". Runs automatic memory consolidation
|
|
@@ -78,7 +79,18 @@ YOUR_AGENT_core op:brain_build_intelligence
|
|
|
78
79
|
|
|
79
80
|
Rebuild brain intelligence with the freshly consolidated vault data.
|
|
80
81
|
|
|
81
|
-
### Step 5:
|
|
82
|
+
### Step 5: Normalize Relative Dates
|
|
83
|
+
|
|
84
|
+
If the dream report includes entries with relative date references ("today", "yesterday", "last week"), normalize them. Search for entries containing relative dates and update to absolute ISO dates:
|
|
85
|
+
|
|
86
|
+
```
|
|
87
|
+
YOUR_AGENT_vault op:search_intelligent
|
|
88
|
+
params: { query: "today OR yesterday OR last week OR last month", limit: 20 }
|
|
89
|
+
```
|
|
90
|
+
|
|
91
|
+
For each entry with relative dates, update `content` to replace relative references with absolute dates based on the entry's `capturedAt` timestamp.
|
|
92
|
+
|
|
93
|
+
### Step 6: Capture to Memory
|
|
82
94
|
|
|
83
95
|
```
|
|
84
96
|
YOUR_AGENT_memory op:session_capture
|
|
@@ -96,6 +108,24 @@ Auto-dream triggers automatically on session start when BOTH conditions are met:
|
|
|
96
108
|
|
|
97
109
|
Manual `/dream` always runs immediately (force=true).
|
|
98
110
|
|
|
111
|
+
## Auto-Dream Scheduling
|
|
112
|
+
|
|
113
|
+
To enable periodic auto-dream (runs every 24h after 5+ sessions):
|
|
114
|
+
|
|
115
|
+
```
|
|
116
|
+
YOUR_AGENT_core op:curator_schedule_start
|
|
117
|
+
params: {
|
|
118
|
+
intervalHours: 24,
|
|
119
|
+
minSessions: 5
|
|
120
|
+
}
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
To disable:
|
|
124
|
+
|
|
125
|
+
```
|
|
126
|
+
YOUR_AGENT_core op:curator_schedule_stop
|
|
127
|
+
```
|
|
128
|
+
|
|
99
129
|
## Background
|
|
100
130
|
|
|
101
131
|
Inspired by Claude Code's AutoDream feature and the neuroscience of REM sleep.
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: soleri-intake
|
|
3
|
+
tier: default
|
|
4
|
+
description: >
|
|
5
|
+
Use when the user says "ingest this", "add this URL", "import this book",
|
|
6
|
+
"read and capture", "ingest batch", or when processing external content
|
|
7
|
+
into the vault. Handles URLs, text, books, and batch imports with
|
|
8
|
+
automatic knowledge extraction.
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Intake — Ingest External Content
|
|
12
|
+
|
|
13
|
+
Import external content (URLs, books, text, batch files) into the vault with automatic knowledge extraction. The intake skill handles chunking, entity extraction, and vault persistence so you don't have to do it manually.
|
|
14
|
+
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- User pastes a URL ("save this article to vault")
|
|
18
|
+
- User shares a book or long document ("ingest this book into your knowledge base")
|
|
19
|
+
- User wants to capture raw text from an external source
|
|
20
|
+
- Batch importing multiple sources at once
|
|
21
|
+
|
|
22
|
+
## Orchestration
|
|
23
|
+
|
|
24
|
+
### Step 1: Identify Content Type
|
|
25
|
+
|
|
26
|
+
Determine what the user is providing:
|
|
27
|
+
|
|
28
|
+
| Type | Use Op | When |
|
|
29
|
+
| ---------------- | -------------- | -------------------------------- |
|
|
30
|
+
| URL | `ingest_url` | User pastes a web link |
|
|
31
|
+
| Book / long doc | `ingest_book` | PDF, long markdown, or file path |
|
|
32
|
+
| Raw text | `ingest_text` | User pastes text directly |
|
|
33
|
+
| Multiple sources | `ingest_batch` | List of URLs or file paths |
|
|
34
|
+
|
|
35
|
+
### Step 2: Ingest
|
|
36
|
+
|
|
37
|
+
**URL:**
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
YOUR_AGENT_intake op:ingest_url
|
|
41
|
+
params: {
|
|
42
|
+
url: "<url>",
|
|
43
|
+
domain: "<inferred domain>",
|
|
44
|
+
tags: ["<tag1>", "<tag2>"]
|
|
45
|
+
}
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
**Book / Long Document:**
|
|
49
|
+
|
|
50
|
+
```
|
|
51
|
+
YOUR_AGENT_intake op:ingest_book
|
|
52
|
+
params: {
|
|
53
|
+
path: "<file path or url>",
|
|
54
|
+
title: "<document title>",
|
|
55
|
+
domain: "<domain>",
|
|
56
|
+
chunkStrategy: "chapter"
|
|
57
|
+
}
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
**Raw Text:**
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
YOUR_AGENT_intake op:ingest_text
|
|
64
|
+
params: {
|
|
65
|
+
text: "<content>",
|
|
66
|
+
title: "<descriptive title>",
|
|
67
|
+
domain: "<domain>",
|
|
68
|
+
tags: ["<tag>"]
|
|
69
|
+
}
|
|
70
|
+
```
|
|
71
|
+
|
|
72
|
+
**Batch:**
|
|
73
|
+
|
|
74
|
+
```
|
|
75
|
+
YOUR_AGENT_intake op:ingest_batch
|
|
76
|
+
params: {
|
|
77
|
+
sources: [
|
|
78
|
+
{ type: "url", value: "<url1>" },
|
|
79
|
+
{ type: "url", value: "<url2>" }
|
|
80
|
+
],
|
|
81
|
+
domain: "<domain>"
|
|
82
|
+
}
|
|
83
|
+
```
|
|
84
|
+
|
|
85
|
+
### Step 3: Report Results
|
|
86
|
+
|
|
87
|
+
Present a summary table:
|
|
88
|
+
|
|
89
|
+
| Field | Value |
|
|
90
|
+
| ------------------- | ----------------- |
|
|
91
|
+
| **Entries created** | {count} |
|
|
92
|
+
| **Domain** | {domain} |
|
|
93
|
+
| **Tags** | {tags.join(', ')} |
|
|
94
|
+
| **Status** | {status} |
|
|
95
|
+
|
|
96
|
+
If any sources failed, list them with reasons so the user can retry.
|
|
97
|
+
|
|
98
|
+
## Exit Criteria
|
|
99
|
+
|
|
100
|
+
All content ingested, entry IDs confirmed, results reported to user.
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: soleri-loop
|
|
3
|
+
tier: default
|
|
4
|
+
description: >
|
|
5
|
+
Use when the user says "start a loop", "run until done", "iterate until X",
|
|
6
|
+
"loop status", or "cancel loop". Manages iterative execution loops that
|
|
7
|
+
repeat a task until a condition is met or a grade threshold is reached.
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
# Loop — Iterative Execution
|
|
11
|
+
|
|
12
|
+
Run a task in a loop until a condition is met — grade threshold, promise fulfilled, or explicit cancellation. Useful for plan refinement, quality iteration, and autonomous improvement cycles.
|
|
13
|
+
|
|
14
|
+
## When to Use
|
|
15
|
+
|
|
16
|
+
- Improving a plan until it reaches grade A
|
|
17
|
+
- Running validation until all tests pass
|
|
18
|
+
- Any task that needs to repeat with self-correction until done
|
|
19
|
+
|
|
20
|
+
## Orchestration
|
|
21
|
+
|
|
22
|
+
### Step 1: Start Loop
|
|
23
|
+
|
|
24
|
+
```
|
|
25
|
+
YOUR_AGENT_loop op:loop_start
|
|
26
|
+
params: {
|
|
27
|
+
prompt: "<task description>",
|
|
28
|
+
mode: "<plan-iteration | custom>",
|
|
29
|
+
maxIterations: <number, default 10>
|
|
30
|
+
}
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
**Modes:**
|
|
34
|
+
|
|
35
|
+
- `plan-iteration` — repeats `create_plan` until grade >= A (target-based)
|
|
36
|
+
- `custom` — user-defined stop condition; loop continues until promise satisfied
|
|
37
|
+
|
|
38
|
+
Note the `loopId` from the response — needed for status and cancel.
|
|
39
|
+
|
|
40
|
+
### Step 2: Monitor
|
|
41
|
+
|
|
42
|
+
At each iteration, check status:
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
YOUR_AGENT_loop op:loop_status
|
|
46
|
+
params: { loopId: "<loopId>" }
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Report progress to user:
|
|
50
|
+
|
|
51
|
+
| Field | Value |
|
|
52
|
+
| ------------------ | ------------------------------------ |
|
|
53
|
+
| **Iteration** | {currentIteration} / {maxIterations} |
|
|
54
|
+
| **Status** | {status} |
|
|
55
|
+
| **Last result** | {lastResult} |
|
|
56
|
+
| **Stop condition** | {stopCondition} |
|
|
57
|
+
|
|
58
|
+
### Step 3: Cancel (if needed)
|
|
59
|
+
|
|
60
|
+
If the user wants to stop early:
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
YOUR_AGENT_loop op:loop_cancel
|
|
64
|
+
params: { loopId: "<loopId>", reason: "<why stopping>" }
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
## Exit Criteria
|
|
68
|
+
|
|
69
|
+
Loop completes when: stop condition is met, max iterations reached, or user explicitly cancels. Report final outcome and iteration count.
|
|
@@ -0,0 +1,70 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: soleri-orchestrate
|
|
3
|
+
tier: default
|
|
4
|
+
description: >
|
|
5
|
+
Use when the user gives a work task: "implement X", "build Y", "fix Z",
|
|
6
|
+
"add feature", or any request that requires planning and execution.
|
|
7
|
+
Runs the full orchestration loop: plan → execute → complete with vault
|
|
8
|
+
context and brain recommendations built in.
|
|
9
|
+
---
|
|
10
|
+
|
|
11
|
+
# Orchestrate — Full Work Loop
|
|
12
|
+
|
|
13
|
+
Run the full work loop with vault intelligence: plan the task, execute it step by step, and close with knowledge capture. Use this for any non-trivial task where missing context or skipping steps would cost time.
|
|
14
|
+
|
|
15
|
+
## When to Use
|
|
16
|
+
|
|
17
|
+
- User gives a concrete work task ("implement auth", "refactor the parser", "fix the flaky test")
|
|
18
|
+
- Task spans multiple files or has cross-cutting concerns
|
|
19
|
+
- You want vault patterns and brain recommendations surfaced automatically
|
|
20
|
+
|
|
21
|
+
## Orchestration
|
|
22
|
+
|
|
23
|
+
### Step 1: Plan
|
|
24
|
+
|
|
25
|
+
```
|
|
26
|
+
YOUR_AGENT_orchestrate op:orchestrate_plan
|
|
27
|
+
params: {
|
|
28
|
+
prompt: "<user task description>",
|
|
29
|
+
context: { domain: "<inferred domain>" }
|
|
30
|
+
}
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
Present the plan to the user. If grade < A-, ask for approval before proceeding.
|
|
34
|
+
|
|
35
|
+
### Step 2: Execute
|
|
36
|
+
|
|
37
|
+
Once approved, begin execution. For each task in the plan:
|
|
38
|
+
|
|
39
|
+
```
|
|
40
|
+
YOUR_AGENT_orchestrate op:orchestrate_execute
|
|
41
|
+
params: {
|
|
42
|
+
planId: "<planId from step 1>",
|
|
43
|
+
taskId: "<current task id>",
|
|
44
|
+
output: "<what you did>"
|
|
45
|
+
}
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
Log progress after each task: show completed count / total and current task title.
|
|
49
|
+
|
|
50
|
+
### Step 3: Complete
|
|
51
|
+
|
|
52
|
+
After all tasks are done:
|
|
53
|
+
|
|
54
|
+
```
|
|
55
|
+
YOUR_AGENT_orchestrate op:orchestrate_complete
|
|
56
|
+
params: {
|
|
57
|
+
planId: "<planId>",
|
|
58
|
+
summary: "<one-line outcome>",
|
|
59
|
+
operatorSignals: {
|
|
60
|
+
qualityNotes: "<any quality observations>",
|
|
61
|
+
unexpectedComplexity: <true|false>
|
|
62
|
+
}
|
|
63
|
+
}
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
Report the completion summary and any knowledge captured.
|
|
67
|
+
|
|
68
|
+
## Exit Criteria
|
|
69
|
+
|
|
70
|
+
All plan tasks executed, `orchestrate_complete` called with outcome, knowledge persisted to vault.
|
|
@@ -1,11 +1,12 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: soleri-vault-capture
|
|
3
|
+
tier: default
|
|
3
4
|
description: >
|
|
4
|
-
Use when the user says "save this", "capture this", "remember this pattern",
|
|
5
|
-
"add to vault", "vault capture", or when persisting learnings from a work
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
knowledge-harvest
|
|
5
|
+
Use when the user says "save this to vault", "capture this", "remember this pattern",
|
|
6
|
+
"add to vault", "vault capture", or when persisting learnings from a work session.
|
|
7
|
+
Priority over memory_capture for durable knowledge (patterns, decisions, anti-patterns).
|
|
8
|
+
For quick session notes say "save this as a memory" to use memory_capture instead.
|
|
9
|
+
For bulk extraction from documents, code, or PRs, use knowledge-harvest.
|
|
9
10
|
---
|
|
10
11
|
|
|
11
12
|
# Vault Capture — Validated Knowledge Persistence
|
|
@@ -1,9 +1,12 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: soleri-writing-plans
|
|
3
|
+
tier: default
|
|
3
4
|
description: >
|
|
4
|
-
Use when the user says "create a plan", "break this down",
|
|
5
|
-
"plan the implementation".
|
|
6
|
-
|
|
5
|
+
Use when the user says "create a plan", "write up a plan", "break this down",
|
|
6
|
+
or "plan the implementation". Produces a human-readable markdown plan file.
|
|
7
|
+
Takes priority over orchestrate_plan MCP op for explicit plan-writing requests.
|
|
8
|
+
For exploration or ideation, use brainstorming. For automated task orchestration,
|
|
9
|
+
the engine uses orchestrate_plan directly without this skill.
|
|
7
10
|
---
|
|
8
11
|
|
|
9
12
|
# Writing Plans
|