@leeovery/claude-technical-workflows 2.0.8 → 2.0.9
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 +25 -5
- package/commands/start-planning.md +2 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -84,13 +84,32 @@ Run the command directly or ask Claude to run it. Each command gathers the conte
|
|
|
84
84
|
|
|
85
85
|
## Installation
|
|
86
86
|
|
|
87
|
-
|
|
87
|
+
Two installation methods are available:
|
|
88
|
+
|
|
89
|
+
| Method | Best for | Trade-off |
|
|
90
|
+
|--------|----------|-----------|
|
|
91
|
+
| **Marketplace** | Local Claude Code | Simple install, skills cached globally |
|
|
92
|
+
| **npm** | Claude Code for Web | Skills copied to repo, requires npm |
|
|
93
|
+
|
|
94
|
+
### Option 1: Claude Marketplace
|
|
95
|
+
|
|
96
|
+
```
|
|
97
|
+
/plugin marketplace add leeovery/claude-plugins-marketplace
|
|
98
|
+
/plugin install claude-technical-workflows@claude-plugins-marketplace
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
> **Note:** Marketplace plugins are cached globally (`~/.claude/plugins/`) and won't be available in Claude Code for Web since files aren't in your repository.
|
|
102
|
+
|
|
103
|
+
### Option 2: npm (Recommended for Web)
|
|
88
104
|
|
|
89
105
|
```bash
|
|
90
106
|
npm install -D @leeovery/claude-technical-workflows
|
|
91
107
|
```
|
|
92
108
|
|
|
93
|
-
|
|
109
|
+
Skills are copied to `.claude/` in your project and can be committed to your repository—making them available in Claude Code for Web.
|
|
110
|
+
|
|
111
|
+
<details>
|
|
112
|
+
<summary>pnpm users</summary>
|
|
94
113
|
|
|
95
114
|
pnpm doesn't expose binaries from transitive dependencies, so install the manager directly:
|
|
96
115
|
|
|
@@ -99,16 +118,17 @@ pnpm add -D @leeovery/claude-manager @leeovery/claude-technical-workflows
|
|
|
99
118
|
pnpm approve-builds # approve when prompted
|
|
100
119
|
pnpm install # triggers postinstall
|
|
101
120
|
```
|
|
121
|
+
</details>
|
|
102
122
|
|
|
103
|
-
|
|
123
|
+
<details>
|
|
124
|
+
<summary>Removal (npm/pnpm)</summary>
|
|
104
125
|
|
|
105
126
|
Due to bugs in npm 7+ ([issue #3042](https://github.com/npm/cli/issues/3042)) and pnpm ([issue #3276](https://github.com/pnpm/pnpm/issues/3276)), preuninstall hooks don't run reliably. Remove files manually first:
|
|
106
127
|
|
|
107
128
|
```bash
|
|
108
129
|
npx claude-manager remove @leeovery/claude-technical-workflows && npm rm @leeovery/claude-technical-workflows
|
|
109
130
|
```
|
|
110
|
-
|
|
111
|
-
The [Claude Manager](https://github.com/leeovery/claude-manager) copies skills, commands, and agents to `.claude/` automatically.
|
|
131
|
+
</details>
|
|
112
132
|
|
|
113
133
|
## The Six-Phase Workflow
|
|
114
134
|
|
|
@@ -56,6 +56,8 @@ Which specification would you like to create a plan for?
|
|
|
56
56
|
|
|
57
57
|
**Important:** Only completed specifications should proceed to planning. If a specification is still being built, advise the user to complete the specification phase first.
|
|
58
58
|
|
|
59
|
+
**Auto-select:** If exactly one specification exists, automatically select it and proceed to Step 4. Inform the user which specification was selected. Do not ask for confirmation.
|
|
60
|
+
|
|
59
61
|
Ask: **Which specification would you like to plan?**
|
|
60
62
|
|
|
61
63
|
## Step 4: Choose Output Destination
|