@devshop/crew 0.13.0 → 0.14.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.
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
{
|
|
2
|
-
"name": "
|
|
2
|
+
"name": "devshop",
|
|
3
3
|
"owner": {
|
|
4
4
|
"name": "devshop-software"
|
|
5
5
|
},
|
|
6
6
|
"description": "Project-agnostic Claude Code skills for spec → implement → qa → review → ship.",
|
|
7
7
|
"plugins": [
|
|
8
8
|
{
|
|
9
|
-
"name": "
|
|
10
|
-
"source": "./skills/
|
|
11
|
-
"description": "Turn rough intent into agent-ready, testable GitHub Issues (
|
|
9
|
+
"name": "crew",
|
|
10
|
+
"source": "./skills/crew",
|
|
11
|
+
"description": "Turn rough intent into agent-ready, testable GitHub Issues (crew:ticket)."
|
|
12
12
|
}
|
|
13
13
|
]
|
|
14
14
|
}
|
package/CHANGELOG.md
CHANGED
|
@@ -1,3 +1,10 @@
|
|
|
1
|
+
# [0.14.0](https://github.com/devshop-software/crew/compare/v0.13.0...v0.14.0) (2026-06-11)
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
### Features
|
|
5
|
+
|
|
6
|
+
* **plugin:** rename plan plugin to crew (crew:ticket), marketplace to devshop ([da4d93a](https://github.com/devshop-software/crew/commit/da4d93aad3ac43c518099f813b392bb355eb98e3))
|
|
7
|
+
|
|
1
8
|
# [0.13.0](https://github.com/devshop-software/crew/compare/v0.12.0...v0.13.0) (2026-06-11)
|
|
2
9
|
|
|
3
10
|
|
package/README.md
CHANGED
|
@@ -32,14 +32,14 @@ This copies the skills into `./.claude/skills/`, writes a manifest, and appends
|
|
|
32
32
|
|
|
33
33
|
### Namespaced skills (plugins)
|
|
34
34
|
|
|
35
|
-
Some skills ship as Claude Code **plugins** so they're invoked under a namespace — e.g. the
|
|
35
|
+
Some skills ship as Claude Code **plugins** so they're invoked under a namespace — e.g. the ticket-writer is **`/crew:ticket`**. No extra step is needed: `crew init` copies the plugin to `.claude/skills/crew/` (it carries a `.claude-plugin/plugin.json`), and Claude Code auto-loads any such folder as `crew@skills-dir`, exposing `/crew:ticket` on the next session.
|
|
36
36
|
|
|
37
37
|
Prefer Claude Code's own plugin system over the CLI? Install straight from the marketplace instead:
|
|
38
38
|
|
|
39
39
|
```sh
|
|
40
40
|
# run inside Claude Code
|
|
41
41
|
/plugin marketplace add devshop-software/crew
|
|
42
|
-
/plugin install
|
|
42
|
+
/plugin install crew@devshop
|
|
43
43
|
```
|
|
44
44
|
|
|
45
45
|
## Commands
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: ticket
|
|
3
|
-
description: "Interactive ticket-writer. Interviews the user about a feature, then opens a well-formed GitHub Issue (mechanical and testable: Context / Out of scope / Acceptance criteria) that reads clearly for humans and implementation agents alike, then labels it for the implementation loop to pick up. Project conventions are read from CLAUDE.md at runtime — the skill contains no project-specific knowledge. Use when the user invokes /
|
|
3
|
+
description: "Interactive ticket-writer. Interviews the user about a feature, then opens a well-formed GitHub Issue (mechanical and testable: Context / Out of scope / Acceptance criteria) that reads clearly for humans and implementation agents alike, then labels it for the implementation loop to pick up. Project conventions are read from CLAUDE.md at runtime — the skill contains no project-specific knowledge. Use when the user invokes /crew:ticket."
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Ticket
|
|
@@ -17,7 +17,7 @@ The output is a GitHub Issue — it lands in a reviewable queue that humans tria
|
|
|
17
17
|
|
|
18
18
|
## When to Apply
|
|
19
19
|
|
|
20
|
-
Activate when called from the `/
|
|
20
|
+
Activate when called from the `/crew:ticket` command. Otherwise ignore.
|
|
21
21
|
|
|
22
22
|
---
|
|
23
23
|
|
|
@@ -134,7 +134,7 @@ Then ask: _"Want to tweak anything before the loop picks this up?"_ If the user
|
|
|
134
134
|
|
|
135
135
|
- Embed project-specific tool, framework, or package-manager names into this skill file. It must work in any repo that has a `CLAUDE.md`.
|
|
136
136
|
- Prescribe mechanisms (hooks, CSS utilities, component layout, which file to edit) unless the user explicitly committed to one in the interview. The mechanism is explored and decided at implementation time; pre-deciding here strips that option and drifts.
|
|
137
|
-
- Skip the interview. The point of `/
|
|
137
|
+
- Skip the interview. The point of `/crew:ticket` is to extract what only the user knows.
|
|
138
138
|
- Explore the codebase to implementation depth. Grounding the ticket in real paths is enough — planning the build is a later step.
|
|
139
139
|
- Open a second issue when refining — edit the existing one.
|
|
140
140
|
|