sherpa-skill 2.0.4 → 2.0.5
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/README.md +146 -146
- package/distribution/cli/sherpa +1 -1
- package/distribution/uninstall.ps1 +3 -2
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,146 +1,146 @@
|
|
|
1
|
-
# Sherpa
|
|
2
|
-
|
|
3
|
-
**Build the right thing. Prove it works. Show why it matters.**
|
|
4
|
-
|
|
5
|
-
In 30 seconds you get an AI hackathon mentor installed in Claude Code or OpenCode that takes your team from a vague idea to a scoped, evidence-backed plan — and a demo you can defend to judges.
|
|
6
|
-
|
|
7
|
-
```bash
|
|
8
|
-
npm install -g sherpa-skill
|
|
9
|
-
sherpa install
|
|
10
|
-
```
|
|
11
|
-
|
|
12
|
-
Then in your agent:
|
|
13
|
-
```text
|
|
14
|
-
/sherpa suggest
|
|
15
|
-
/sherpa plan
|
|
16
|
-
/sherpa demo
|
|
17
|
-
/sherpa submission
|
|
18
|
-
```
|
|
19
|
-
|
|
20
|
-
**What you get right away:**
|
|
21
|
-
- **One install:** works in Claude Code and OpenCode; project state lives in `.sherpa/` and survives restarts and context switches.
|
|
22
|
-
- **Evidence-led:** facts vs assumptions, with `UNKNOWN` when information is missing — no invented details.
|
|
23
|
-
- **Human approval gates:** Sherpa recommends, never silently picks an idea or writes code without you confirming.
|
|
24
|
-
- **Full lifecycle:** idea → plan → build → verify → demo → submission → postmortem.
|
|
25
|
-
|
|
26
|
-
[](https://www.npmjs.com/package/sherpa-skill)
|
|
27
|
-
[](LICENSE)
|
|
28
|
-
[](https://github.com/Anshkaliya18/sherpa/stargazers)
|
|
29
|
-
[](AGENT-COMPATIBILITY.md)
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
## Install
|
|
34
|
-
|
|
35
|
-
The npm package is published as `sherpa-skill` (the name `sherpa` is already taken on npm).
|
|
36
|
-
|
|
37
|
-
### Option 1: npm (recommended)
|
|
38
|
-
|
|
39
|
-
```bash
|
|
40
|
-
npm install -g sherpa-skill
|
|
41
|
-
sherpa install
|
|
42
|
-
```
|
|
43
|
-
|
|
44
|
-
This installs the Sherpa skill for both Claude Code and OpenCode, plus the `sherpa` distribution CLI. To preview without writing files:
|
|
45
|
-
|
|
46
|
-
```bash
|
|
47
|
-
sherpa install --dry-run
|
|
48
|
-
```
|
|
49
|
-
|
|
50
|
-
To install only the skill (skip the CLI):
|
|
51
|
-
|
|
52
|
-
```bash
|
|
53
|
-
sherpa install --no-cli
|
|
54
|
-
```
|
|
55
|
-
|
|
56
|
-
To remove:
|
|
57
|
-
|
|
58
|
-
```bash
|
|
59
|
-
sherpa uninstall
|
|
60
|
-
```
|
|
61
|
-
|
|
62
|
-
The npm wrapper commands are `install`, `migrate`, and `uninstall`. (The separate `sherpa` CLI installed by the release script below supports `update`, `doctor`, `audit`, `clean`, and `help`.)
|
|
63
|
-
|
|
64
|
-
Node.js is required to run the npm package. `package.json` does not declare an `engines` field, so no specific Node version is pinned — use a current LTS release.
|
|
65
|
-
|
|
66
|
-
### Option 2: Other install methods (release installers)
|
|
67
|
-
|
|
68
|
-
The release installers download a versioned GitHub Releases archive, verify its SHA-256 checksum, and install the skill and CLI:
|
|
69
|
-
|
|
70
|
-
macOS / Linux:
|
|
71
|
-
```bash
|
|
72
|
-
curl -fsSL https://github.com/Anshkaliya18/sherpa/releases/latest/download/install.sh | bash
|
|
73
|
-
```
|
|
74
|
-
|
|
75
|
-
Windows PowerShell:
|
|
76
|
-
```powershell
|
|
77
|
-
irm https://github.com/Anshkaliya18/sherpa/releases/latest/download/install.ps1 | iex
|
|
78
|
-
```
|
|
79
|
-
|
|
80
|
-
Both installers target `~/.claude/skills/sherpa/` (Claude Code) and `~/.config/opencode/skills/sherpa/` (OpenCode) by default and never touch your project data or `.sherpa/` directories.
|
|
81
|
-
|
|
82
|
-
## See it in action
|
|
83
|
-
|
|
84
|
-
The following is an illustrative example, not a guaranteed transcript. It shows how a vague team idea becomes a scoped plan using real `/sherpa` operations.
|
|
85
|
-
|
|
86
|
-
**Before** — a vague team idea:
|
|
87
|
-
> "We should build something for campus accessibility. Maybe an app?"
|
|
88
|
-
|
|
89
|
-
**After** — walking the idea through Sherpa operations:
|
|
90
|
-
|
|
91
|
-
```text
|
|
92
|
-
/sherpa suggest ideas for campus accessibility
|
|
93
|
-
# -> Surfaces candidate ideas with pros/cons, risks, and judging-impact notes.
|
|
94
|
-
# Human picks one; Sherpa never auto-selects.
|
|
95
|
-
|
|
96
|
-
/sherpa evaluate the chosen idea
|
|
97
|
-
# -> Compares candidates against evidence and criteria, then recommends.
|
|
98
|
-
|
|
99
|
-
/sherpa plan
|
|
100
|
-
# -> Writes an implementation-ready engineering plan to .sherpa/.
|
|
101
|
-
# Architecture is not auto-approved and no code is written yet.
|
|
102
|
-
|
|
103
|
-
/sherpa demo
|
|
104
|
-
# -> Produces a judge-oriented demo preparation plan from validated evidence.
|
|
105
|
-
|
|
106
|
-
/sherpa submission
|
|
107
|
-
# -> Verifies and freezes submission materials without submitting.
|
|
108
|
-
|
|
109
|
-
/sherpa status
|
|
110
|
-
# -> Shows where you are, what's complete, what's broken, and the risks.
|
|
111
|
-
```
|
|
112
|
-
|
|
113
|
-
Each operation maps to a real workflow in `workflows/` (e.g. `idea-intelligence.md`, `project-planning.md`, `demo-preparation.md`, `submission.md`) and is registered in `commands/manifest.json`. Invoke as `/sherpa <operation> [focus]`.
|
|
114
|
-
|
|
115
|
-
## Supported agents
|
|
116
|
-
|
|
117
|
-
| Agent | Integration files | Global installer | Runtime status |
|
|
118
|
-
|---|---|---:|---|
|
|
119
|
-
| Claude Code | `.claude/skills/` skill and command files | Yes | VERIFIED |
|
|
120
|
-
| OpenCode | `.opencode/commands/` and package metadata | Yes | VERIFIED |
|
|
121
|
-
| Kilo Code | `.kilo/commands/` | No | NOT VERIFIED |
|
|
122
|
-
| Codex CLI, Qwen Code, Gemini CLI | No verified native adapter | No | Not supported |
|
|
123
|
-
|
|
124
|
-
Details and evidence: [agent compatibility](AGENT-COMPATIBILITY.md).
|
|
125
|
-
|
|
126
|
-
Verified status is updated only after runtime testing. The table above reflects integration-file coverage, not confirmed runtime loading.
|
|
127
|
-
|
|
128
|
-
Help us verify: install Sherpa on your agent, run `/sherpa status` and `/sherpa next`, and open an issue with your results.
|
|
129
|
-
|
|
130
|
-
## Why Sherpa
|
|
131
|
-
|
|
132
|
-
- **Evidence-led:** facts, assumptions, and unknowns are kept distinct; `UNKNOWN` is used when information is unavailable.
|
|
133
|
-
- **Human approval gates:** recommendations never silently choose ideas or approve consequential work — you confirm each step.
|
|
134
|
-
- **Project-local notes:** project context and generated records live in `.sherpa/` inside your repo, not in the skill directory.
|
|
135
|
-
- **Full lifecycle coverage:** idea selection → planning → implementation → testing/security → demo prep → submission → postmortem.
|
|
136
|
-
|
|
137
|
-
## Contributing / Community
|
|
138
|
-
|
|
139
|
-
- [Contributing guide](CONTRIBUTING.md) — pull requests welcome.
|
|
140
|
-
- Look for issues labeled **good first issue**.
|
|
141
|
-
- [Open an issue](https://github.com/Anshkaliya18/sherpa/issues) for bugs or verification reports.
|
|
142
|
-
- [GitHub Discussions](https://github.com/Anshkaliya18/sherpa/discussions) for questions and ideas.
|
|
143
|
-
|
|
144
|
-
## Documentation
|
|
145
|
-
|
|
146
|
-
Field guide: https://anshkaliya18.github.io/Sherpa/ · Project references: [installation](INSTALLATION.md) · [commands](COMMANDS.md) · [workflows](WORKFLOWS.md) · [configuration](CONFIGURATION.md) · [architecture](ARCHITECTURE.md) · [security](SECURITY.md) · [migration](MIGRATION.md) · [contributing](CONTRIBUTING.md) · [changelog](CHANGELOG.md).
|
|
1
|
+
# Sherpa
|
|
2
|
+
|
|
3
|
+
**Build the right thing. Prove it works. Show why it matters.**
|
|
4
|
+
|
|
5
|
+
In 30 seconds you get an AI hackathon mentor installed in Claude Code or OpenCode that takes your team from a vague idea to a scoped, evidence-backed plan — and a demo you can defend to judges.
|
|
6
|
+
|
|
7
|
+
```bash
|
|
8
|
+
npm install -g sherpa-skill
|
|
9
|
+
sherpa install
|
|
10
|
+
```
|
|
11
|
+
|
|
12
|
+
Then in your agent:
|
|
13
|
+
```text
|
|
14
|
+
/sherpa suggest
|
|
15
|
+
/sherpa plan
|
|
16
|
+
/sherpa demo
|
|
17
|
+
/sherpa submission
|
|
18
|
+
```
|
|
19
|
+
|
|
20
|
+
**What you get right away:**
|
|
21
|
+
- **One install:** works in Claude Code and OpenCode; project state lives in `.sherpa/` and survives restarts and context switches.
|
|
22
|
+
- **Evidence-led:** facts vs assumptions, with `UNKNOWN` when information is missing — no invented details.
|
|
23
|
+
- **Human approval gates:** Sherpa recommends, never silently picks an idea or writes code without you confirming.
|
|
24
|
+
- **Full lifecycle:** idea → plan → build → verify → demo → submission → postmortem.
|
|
25
|
+
|
|
26
|
+
[](https://www.npmjs.com/package/sherpa-skill)
|
|
27
|
+
[](LICENSE)
|
|
28
|
+
[](https://github.com/Anshkaliya18/sherpa/stargazers)
|
|
29
|
+
[](AGENT-COMPATIBILITY.md)
|
|
30
|
+
|
|
31
|
+
|
|
32
|
+
|
|
33
|
+
## Install
|
|
34
|
+
|
|
35
|
+
The npm package is published as `sherpa-skill` (the name `sherpa` is already taken on npm).
|
|
36
|
+
|
|
37
|
+
### Option 1: npm (recommended)
|
|
38
|
+
|
|
39
|
+
```bash
|
|
40
|
+
npm install -g sherpa-skill
|
|
41
|
+
sherpa install
|
|
42
|
+
```
|
|
43
|
+
|
|
44
|
+
This installs the Sherpa skill for both Claude Code and OpenCode, plus the `sherpa` distribution CLI. To preview without writing files:
|
|
45
|
+
|
|
46
|
+
```bash
|
|
47
|
+
sherpa install --dry-run
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
To install only the skill (skip the CLI):
|
|
51
|
+
|
|
52
|
+
```bash
|
|
53
|
+
sherpa install --no-cli
|
|
54
|
+
```
|
|
55
|
+
|
|
56
|
+
To remove:
|
|
57
|
+
|
|
58
|
+
```bash
|
|
59
|
+
sherpa uninstall
|
|
60
|
+
```
|
|
61
|
+
|
|
62
|
+
The npm wrapper commands are `install`, `migrate`, and `uninstall`. (The separate `sherpa` CLI installed by the release script below supports `update`, `doctor`, `audit`, `clean`, and `help`.)
|
|
63
|
+
|
|
64
|
+
Node.js is required to run the npm package. `package.json` does not declare an `engines` field, so no specific Node version is pinned — use a current LTS release.
|
|
65
|
+
|
|
66
|
+
### Option 2: Other install methods (release installers)
|
|
67
|
+
|
|
68
|
+
The release installers download a versioned GitHub Releases archive, verify its SHA-256 checksum, and install the skill and CLI:
|
|
69
|
+
|
|
70
|
+
macOS / Linux:
|
|
71
|
+
```bash
|
|
72
|
+
curl -fsSL https://github.com/Anshkaliya18/sherpa/releases/latest/download/install.sh | bash
|
|
73
|
+
```
|
|
74
|
+
|
|
75
|
+
Windows PowerShell:
|
|
76
|
+
```powershell
|
|
77
|
+
irm https://github.com/Anshkaliya18/sherpa/releases/latest/download/install.ps1 | iex
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
Both installers target `~/.claude/skills/sherpa/` (Claude Code) and `~/.config/opencode/skills/sherpa/` (OpenCode) by default and never touch your project data or `.sherpa/` directories.
|
|
81
|
+
|
|
82
|
+
## See it in action
|
|
83
|
+
|
|
84
|
+
The following is an illustrative example, not a guaranteed transcript. It shows how a vague team idea becomes a scoped plan using real `/sherpa` operations.
|
|
85
|
+
|
|
86
|
+
**Before** — a vague team idea:
|
|
87
|
+
> "We should build something for campus accessibility. Maybe an app?"
|
|
88
|
+
|
|
89
|
+
**After** — walking the idea through Sherpa operations:
|
|
90
|
+
|
|
91
|
+
```text
|
|
92
|
+
/sherpa suggest ideas for campus accessibility
|
|
93
|
+
# -> Surfaces candidate ideas with pros/cons, risks, and judging-impact notes.
|
|
94
|
+
# Human picks one; Sherpa never auto-selects.
|
|
95
|
+
|
|
96
|
+
/sherpa evaluate the chosen idea
|
|
97
|
+
# -> Compares candidates against evidence and criteria, then recommends.
|
|
98
|
+
|
|
99
|
+
/sherpa plan
|
|
100
|
+
# -> Writes an implementation-ready engineering plan to .sherpa/.
|
|
101
|
+
# Architecture is not auto-approved and no code is written yet.
|
|
102
|
+
|
|
103
|
+
/sherpa demo
|
|
104
|
+
# -> Produces a judge-oriented demo preparation plan from validated evidence.
|
|
105
|
+
|
|
106
|
+
/sherpa submission
|
|
107
|
+
# -> Verifies and freezes submission materials without submitting.
|
|
108
|
+
|
|
109
|
+
/sherpa status
|
|
110
|
+
# -> Shows where you are, what's complete, what's broken, and the risks.
|
|
111
|
+
```
|
|
112
|
+
|
|
113
|
+
Each operation maps to a real workflow in `workflows/` (e.g. `idea-intelligence.md`, `project-planning.md`, `demo-preparation.md`, `submission.md`) and is registered in `commands/manifest.json`. Invoke as `/sherpa <operation> [focus]`.
|
|
114
|
+
|
|
115
|
+
## Supported agents
|
|
116
|
+
|
|
117
|
+
| Agent | Integration files | Global installer | Runtime status |
|
|
118
|
+
|---|---|---:|---|
|
|
119
|
+
| Claude Code | `.claude/skills/` skill and command files | Yes | VERIFIED |
|
|
120
|
+
| OpenCode | `.opencode/commands/` and package metadata | Yes | VERIFIED |
|
|
121
|
+
| Kilo Code | `.kilo/commands/` | No | NOT VERIFIED |
|
|
122
|
+
| Codex CLI, Qwen Code, Gemini CLI | No verified native adapter | No | Not supported |
|
|
123
|
+
|
|
124
|
+
Details and evidence: [agent compatibility](AGENT-COMPATIBILITY.md).
|
|
125
|
+
|
|
126
|
+
Verified status is updated only after runtime testing. The table above reflects integration-file coverage, not confirmed runtime loading.
|
|
127
|
+
|
|
128
|
+
Help us verify: install Sherpa on your agent, run `/sherpa status` and `/sherpa next`, and open an issue with your results.
|
|
129
|
+
|
|
130
|
+
## Why Sherpa
|
|
131
|
+
|
|
132
|
+
- **Evidence-led:** facts, assumptions, and unknowns are kept distinct; `UNKNOWN` is used when information is unavailable.
|
|
133
|
+
- **Human approval gates:** recommendations never silently choose ideas or approve consequential work — you confirm each step.
|
|
134
|
+
- **Project-local notes:** project context and generated records live in `.sherpa/` inside your repo, not in the skill directory.
|
|
135
|
+
- **Full lifecycle coverage:** idea selection → planning → implementation → testing/security → demo prep → submission → postmortem.
|
|
136
|
+
|
|
137
|
+
## Contributing / Community
|
|
138
|
+
|
|
139
|
+
- [Contributing guide](CONTRIBUTING.md) — pull requests welcome.
|
|
140
|
+
- Look for issues labeled **good first issue**.
|
|
141
|
+
- [Open an issue](https://github.com/Anshkaliya18/sherpa/issues) for bugs or verification reports.
|
|
142
|
+
- [GitHub Discussions](https://github.com/Anshkaliya18/sherpa/discussions) for questions and ideas.
|
|
143
|
+
|
|
144
|
+
## Documentation
|
|
145
|
+
|
|
146
|
+
Field guide: https://anshkaliya18.github.io/Sherpa/ · Project references: [installation](INSTALLATION.md) · [commands](COMMANDS.md) · [workflows](WORKFLOWS.md) · [configuration](CONFIGURATION.md) · [architecture](ARCHITECTURE.md) · [security](SECURITY.md) · [migration](MIGRATION.md) · [contributing](CONTRIBUTING.md) · [changelog](CHANGELOG.md).
|
package/distribution/cli/sherpa
CHANGED
|
@@ -48,7 +48,7 @@ CLI_NAME = "sherpa"
|
|
|
48
48
|
|
|
49
49
|
# Embedded fallback version. Overridden by a VERSION file next to this script
|
|
50
50
|
# when one is shipped by the installer/release.
|
|
51
|
-
DEFAULT_CLI_VERSION = "2.0.
|
|
51
|
+
DEFAULT_CLI_VERSION = "2.0.5"
|
|
52
52
|
|
|
53
53
|
# Default release manifest URL. Users publishing their own releases override
|
|
54
54
|
# this with SHERPA_RELEASE_MANIFEST_URL.
|
|
@@ -37,7 +37,8 @@ if (Test-Path (Join-Path $OPENCODE_SKILL_DIR "SKILL.md")) {
|
|
|
37
37
|
}
|
|
38
38
|
$cliExe = Join-Path $CLI_BIN_DIR $CLI_NAME
|
|
39
39
|
$cliBat = Join-Path $CLI_BIN_DIR "${CLI_NAME}.bat"
|
|
40
|
-
|
|
40
|
+
$cliExists = (Test-Path $cliExe) -or (Test-Path $cliBat)
|
|
41
|
+
if ($cliExists) {
|
|
41
42
|
Write-Host (" * CLI: {0}" -f $CLI_BIN_DIR) -ForegroundColor Green
|
|
42
43
|
$removed++
|
|
43
44
|
}
|
|
@@ -64,7 +65,7 @@ if (Test-Path (Join-Path $OPENCODE_SKILL_DIR "SKILL.md")) {
|
|
|
64
65
|
}
|
|
65
66
|
if (Test-Path $cliExe) { Remove-Item -Path $cliExe -Force }
|
|
66
67
|
if (Test-Path $cliBat) { Remove-Item -Path $cliBat -Force }
|
|
67
|
-
if ($
|
|
68
|
+
if ($cliExists) { Write-Ok "Removed CLI" }
|
|
68
69
|
|
|
69
70
|
if ($removed -eq 0) {
|
|
70
71
|
Write-Host "No sherpa installation found."
|