@leeovery/claude-technical-workflows 2.0.30 → 2.0.31
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 +47 -37
- package/commands/start-feature.md +1 -1
- package/commands/workflow/start-implementation.md +2 -2
- package/commands/workflow/start-planning.md +1 -1
- package/commands/workflow/start-review.md +1 -1
- package/commands/workflow/start-specification.md +2 -2
- package/commands/workflow/status.md +2 -2
- package/package.json +1 -1
- package/scripts/specification-discovery.sh +1 -1
package/README.md
CHANGED
|
@@ -59,7 +59,7 @@ See [Installation](#installation) for details and trade-offs.
|
|
|
59
59
|
Research → Discussion → Specification → Planning → Implementation → Review
|
|
60
60
|
```
|
|
61
61
|
|
|
62
|
-
Start with `/
|
|
62
|
+
Start with `/start-research` or `/start-discussion` and follow the flow. Each phase outputs files that the next phase consumes.
|
|
63
63
|
|
|
64
64
|
**2. Standalone Commands** - Jump directly to a skill with flexible inputs:
|
|
65
65
|
|
|
@@ -84,7 +84,7 @@ Start with `/workflow:start-research` or `/workflow:start-discussion` and follow
|
|
|
84
84
|
│ COMMANDS │
|
|
85
85
|
│ (gather inputs from files, prompts, inline context) │
|
|
86
86
|
├─────────────────────────────────────────────────────────────┤
|
|
87
|
-
│ /
|
|
87
|
+
│ /start-specification /start-feature (your custom) │
|
|
88
88
|
│ │ │ │ │
|
|
89
89
|
│ └───────────┬───────────┘ │ │
|
|
90
90
|
│ ▼ ▼ │
|
|
@@ -101,23 +101,23 @@ Start with `/workflow:start-research` or `/workflow:start-discussion` and follow
|
|
|
101
101
|
|
|
102
102
|
### Workflow Commands
|
|
103
103
|
|
|
104
|
-
| Phase | Command
|
|
105
|
-
|
|
106
|
-
| Research | `/
|
|
107
|
-
| Discussion | `/
|
|
108
|
-
| Specification | `/
|
|
109
|
-
| Planning | `/
|
|
110
|
-
| Implementation | `/
|
|
111
|
-
| Review | `/
|
|
104
|
+
| Phase | Command |
|
|
105
|
+
|----------------|-------------------------|
|
|
106
|
+
| Research | `/start-research` |
|
|
107
|
+
| Discussion | `/start-discussion` |
|
|
108
|
+
| Specification | `/start-specification` |
|
|
109
|
+
| Planning | `/start-planning` |
|
|
110
|
+
| Implementation | `/start-implementation` |
|
|
111
|
+
| Review | `/start-review` |
|
|
112
112
|
|
|
113
113
|
Run the command directly or ask Claude to run it. Each gathers context from previous phase outputs and passes it to the skill.
|
|
114
114
|
|
|
115
115
|
## Installation
|
|
116
116
|
|
|
117
|
-
| Method
|
|
118
|
-
|
|
119
|
-
| **Marketplace** | `~/.claude/plugins/` (global cache) | Quick setup, don't need files in repo
|
|
120
|
-
| **npm**
|
|
117
|
+
| Method | Where files live | Best for |
|
|
118
|
+
|-----------------|-------------------------------------|-------------------------------------------------|
|
|
119
|
+
| **Marketplace** | `~/.claude/plugins/` (global cache) | Quick setup, don't need files in repo |
|
|
120
|
+
| **npm** | `.claude/` in your project | Ownership, version control, Claude Code for Web |
|
|
121
121
|
|
|
122
122
|
### Option 1: Claude Marketplace
|
|
123
123
|
|
|
@@ -163,20 +163,30 @@ npx claude-manager remove @leeovery/claude-technical-workflows && npm rm @leeove
|
|
|
163
163
|
When using the full workflow, it progresses through six distinct phases:
|
|
164
164
|
|
|
165
165
|
```
|
|
166
|
-
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
|
|
167
|
-
│ Research │──▶│ Discussion │──▶│ Specification
|
|
168
|
-
│ (Phase 1) │ │ (Phase 2) │ │ (Phase 3) │
|
|
169
|
-
├───────────────┤ ├───────────────┤ ├───────────────┤
|
|
170
|
-
│ EXPLORING │ │ WHAT & WHY │ │ REFINING │
|
|
171
|
-
│ │ │ │ │ │
|
|
172
|
-
│ • Ideas │ │ • Architecture│ │ • Validate │
|
|
173
|
-
│ • Market │ │ • Decisions │ │ • Filter │
|
|
174
|
-
│ • Viability │ │ • Edge cases │ │ • Enrich │
|
|
175
|
-
│ │ │ • Rationale │ │ • Standalone │
|
|
176
|
-
└───────────────┘ └───────────────┘ └───────────────┘
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
166
|
+
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
|
|
167
|
+
│ Research │──▶│ Discussion │──▶│ Specification │
|
|
168
|
+
│ (Phase 1) │ │ (Phase 2) │ │ (Phase 3) │
|
|
169
|
+
├───────────────┤ ├───────────────┤ ├───────────────┤
|
|
170
|
+
│ EXPLORING │ │ WHAT & WHY │ │ REFINING │
|
|
171
|
+
│ │ │ │ │ │
|
|
172
|
+
│ • Ideas │ │ • Architecture│ │ • Validate │
|
|
173
|
+
│ • Market │ │ • Decisions │ │ • Filter │
|
|
174
|
+
│ • Viability │ │ • Edge cases │ │ • Enrich │
|
|
175
|
+
│ │ │ • Rationale │ │ • Standalone │
|
|
176
|
+
└───────────────┘ └───────────────┘ └───────────────┘
|
|
177
|
+
│
|
|
178
|
+
▼
|
|
179
|
+
┌───────────────┐ ┌───────────────┐ ┌───────────────┐
|
|
180
|
+
│ Review │◀──│Implementation │◀──│ Planning │
|
|
181
|
+
│ (Phase 6) │ │ (Phase 5) │ │ (Phase 4) │
|
|
182
|
+
├───────────────┤ ├───────────────┤ ├───────────────┤
|
|
183
|
+
│ VALIDATING │ │ DOING │ │ HOW │
|
|
184
|
+
│ │ │ │ │ │
|
|
185
|
+
│ • Plan check │ │ • Tests first │ │ • Phases │
|
|
186
|
+
│ • Specs check │ │ • Then code │ │ • Tasks │
|
|
187
|
+
│ • Test quality│ │ • Commit often│ │ • Criteria │
|
|
188
|
+
│ • Code quality│ │ • Phase gates │ │ • Outputs │
|
|
189
|
+
└───────────────┘ └───────────────┘ └───────────────┘
|
|
180
190
|
```
|
|
181
191
|
|
|
182
192
|
**Phase 1 - Research:** Explore ideas from their earliest seed. Investigate market fit, technical feasibility, business viability. Free-flowing exploration that may or may not lead to building something.
|
|
@@ -263,16 +273,16 @@ Commands are the input layer: they gather context and pass it to skills. Two typ
|
|
|
263
273
|
|
|
264
274
|
### Workflow Commands
|
|
265
275
|
|
|
266
|
-
Sequential commands
|
|
276
|
+
Sequential commands in `commands/workflow/`. They expect files from previous phases and pass content to skills.
|
|
267
277
|
|
|
268
278
|
| Command | Description |
|
|
269
279
|
|--------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
270
|
-
| [**/
|
|
271
|
-
| [**/
|
|
272
|
-
| [**/
|
|
273
|
-
| [**/
|
|
274
|
-
| [**/
|
|
275
|
-
| [**/
|
|
280
|
+
| [**/start-research**](commands/workflow/start-research.md) | Begin research exploration. For early-stage ideas, feasibility checks, and broad exploration before formal discussion. |
|
|
281
|
+
| [**/start-discussion**](commands/workflow/start-discussion.md) | Begin a new technical discussion. Gathers topic, context, background information, and relevant codebase areas before starting documentation. |
|
|
282
|
+
| [**/start-specification**](commands/workflow/start-specification.md) | Start a specification session from existing discussion(s). Automatically analyses multiple discussions for natural groupings and consolidates them into unified specifications. |
|
|
283
|
+
| [**/start-planning**](commands/workflow/start-planning.md) | Start a planning session from an existing specification. Creates implementation plans with phases, tasks, and acceptance criteria. Supports multiple output formats (markdown, Linear, Backlog.md, Beads). |
|
|
284
|
+
| [**/start-implementation**](commands/workflow/start-implementation.md) | Start implementing a plan. Executes tasks via strict TDD, committing after each passing test. |
|
|
285
|
+
| [**/start-review**](commands/workflow/start-review.md) | Start reviewing completed work. Validates implementation against plan tasks and acceptance criteria. |
|
|
276
286
|
|
|
277
287
|
### Utility Commands
|
|
278
288
|
|
|
@@ -280,8 +290,8 @@ Helpers for navigating and understanding the workflow.
|
|
|
280
290
|
|
|
281
291
|
| Command | Description |
|
|
282
292
|
|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|
|
|
283
|
-
| [**/
|
|
284
|
-
| [**/
|
|
293
|
+
| [**/status**](commands/workflow/status.md) | Show workflow status - what topics exist at each phase, and suggested next steps. |
|
|
294
|
+
| [**/view-plan**](commands/workflow/view-plan.md) | View a plan's tasks and progress, regardless of output format. |
|
|
285
295
|
|
|
286
296
|
### Standalone Commands
|
|
287
297
|
|
|
@@ -76,5 +76,5 @@ Work from the inline context provided above.
|
|
|
76
76
|
|
|
77
77
|
- The specification skill contains instructions for synthesizing the inline context, presenting it for validation, and building the specification
|
|
78
78
|
- Output is a standard specification file at `docs/workflow/specification/{topic}.md`
|
|
79
|
-
- From there, the user can proceed to `/
|
|
79
|
+
- From there, the user can proceed to `/start-planning` as normal
|
|
80
80
|
- This path skips formal discussion documentation - use the full workflow for complex features that need debate captured
|
|
@@ -54,7 +54,7 @@ Scan the codebase for plans:
|
|
|
54
54
|
|
|
55
55
|
Show what you found.
|
|
56
56
|
|
|
57
|
-
> **Note:** If no plans exist, inform the user that this workflow is designed to be executed in sequence. They need to create plans from specifications prior to implementation using `/
|
|
57
|
+
> **Note:** If no plans exist, inform the user that this workflow is designed to be executed in sequence. They need to create plans from specifications prior to implementation using `/start-planning`.
|
|
58
58
|
|
|
59
59
|
> **Auto-select:** If exactly one plan exists, automatically select it and proceed to Step 3. Inform the user which plan was selected. Do not ask for confirmation.
|
|
60
60
|
|
|
@@ -89,7 +89,7 @@ If ANY dependency is unresolved or incomplete, **stop and present**:
|
|
|
89
89
|
|
|
90
90
|
UNRESOLVED (not yet planned):
|
|
91
91
|
- billing-system: Invoice generation for order completion
|
|
92
|
-
→ No plan exists for this topic. Create with /
|
|
92
|
+
→ No plan exists for this topic. Create with /start-planning or mark as satisfied externally.
|
|
93
93
|
|
|
94
94
|
INCOMPLETE (planned but not implemented):
|
|
95
95
|
- beads-7x2k (authentication): User context retrieval
|
|
@@ -59,7 +59,7 @@ Scan the codebase for specifications and plans:
|
|
|
59
59
|
```
|
|
60
60
|
⚠️ No specifications found in docs/workflow/specification/
|
|
61
61
|
|
|
62
|
-
The planning phase requires a completed specification. Please run /
|
|
62
|
+
The planning phase requires a completed specification. Please run /start-specification first to validate and refine the discussion content into a standalone specification before creating a plan.
|
|
63
63
|
```
|
|
64
64
|
|
|
65
65
|
Stop here and wait for the user to acknowledge.
|
|
@@ -51,7 +51,7 @@ Scan the codebase for plans:
|
|
|
51
51
|
```
|
|
52
52
|
No plans found in docs/workflow/planning/
|
|
53
53
|
|
|
54
|
-
The review phase requires a completed implementation based on a plan. Please run /
|
|
54
|
+
The review phase requires a completed implementation based on a plan. Please run /start-planning first to create a plan, then /start-implementation to build it.
|
|
55
55
|
```
|
|
56
56
|
|
|
57
57
|
Stop here and wait for the user to acknowledge.
|
|
@@ -68,7 +68,7 @@ This outputs structured YAML. Parse it to understand:
|
|
|
68
68
|
```
|
|
69
69
|
No discussions found in docs/workflow/discussion/
|
|
70
70
|
|
|
71
|
-
The specification phase requires a completed discussion. Please run /
|
|
71
|
+
The specification phase requires a completed discussion. Please run /start-discussion first to document the technical decisions, edge cases, and rationale before creating a specification.
|
|
72
72
|
```
|
|
73
73
|
|
|
74
74
|
**STOP.** Wait for user acknowledgment. Do not proceed.
|
|
@@ -82,7 +82,7 @@ The following discussions are still exploring:
|
|
|
82
82
|
- {topic-1} (exploring)
|
|
83
83
|
- {topic-2} (exploring)
|
|
84
84
|
|
|
85
|
-
Please complete the discussion phase before creating specifications. Run /
|
|
85
|
+
Please complete the discussion phase before creating specifications. Run /start-discussion to continue a discussion.
|
|
86
86
|
```
|
|
87
87
|
|
|
88
88
|
**STOP.** Wait for user acknowledgment. Do not proceed.
|
|
@@ -45,7 +45,7 @@ Adapt based on what exists:
|
|
|
45
45
|
Based on what exists, offer relevant options. Don't assume linear progression - topics may have dependencies on each other.
|
|
46
46
|
|
|
47
47
|
**If nothing exists:**
|
|
48
|
-
- "Start with `/
|
|
48
|
+
- "Start with `/start-research` to explore ideas, or `/start-discussion` if you already know what you're building."
|
|
49
49
|
|
|
50
50
|
**If topics exist at various stages**, summarise options without being prescriptive:
|
|
51
51
|
- Topics in discussion can move to specification
|
|
@@ -62,7 +62,7 @@ Keep suggestions brief - the user knows their project's dependencies better than
|
|
|
62
62
|
If planning files exist, let the user know they can view plan details:
|
|
63
63
|
|
|
64
64
|
```
|
|
65
|
-
To view a plan's tasks and progress, use /
|
|
65
|
+
To view a plan's tasks and progress, use /view-plan
|
|
66
66
|
```
|
|
67
67
|
|
|
68
68
|
## Notes
|
package/package.json
CHANGED
|
@@ -3,7 +3,7 @@
|
|
|
3
3
|
# discover-spec-state.sh
|
|
4
4
|
#
|
|
5
5
|
# Discovers the current state of discussions, specifications, and cache
|
|
6
|
-
# for the
|
|
6
|
+
# for the /start-specification command.
|
|
7
7
|
#
|
|
8
8
|
# Outputs structured YAML that the command can consume directly.
|
|
9
9
|
#
|