@leeovery/claude-technical-workflows 2.0.7 → 2.0.8
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
CHANGED
|
@@ -45,6 +45,8 @@ Review → Validate against spec
|
|
|
45
45
|
|
|
46
46
|
**This is a work in progress.** The workflow is being refined through real-world usage. Expect updates as patterns evolve.
|
|
47
47
|
|
|
48
|
+
**Model compatibility:** These skills have been developed and refined for Claude Code running on **Opus 4.5**. Different models may exhibit different edge cases, and future model releases may require adjustments to the prompts and workflows.
|
|
49
|
+
|
|
48
50
|
## How do I use this?
|
|
49
51
|
|
|
50
52
|
You have two entry points:
|
|
@@ -70,12 +72,12 @@ Each phase builds on the previous. Specification validates your discussions into
|
|
|
70
72
|
|
|
71
73
|
Each phase has a command designed as its entry point:
|
|
72
74
|
|
|
73
|
-
| Phase
|
|
74
|
-
|
|
75
|
-
| Research
|
|
76
|
-
| Discussion
|
|
77
|
-
| Specification
|
|
78
|
-
| Planning
|
|
75
|
+
| Phase | Command |
|
|
76
|
+
|----------------|-------------------------|
|
|
77
|
+
| Research | `/start-research` |
|
|
78
|
+
| Discussion | `/start-discussion` |
|
|
79
|
+
| Specification | `/start-specification` |
|
|
80
|
+
| Planning | `/start-planning` |
|
|
79
81
|
| Implementation | `/start-implementation` |
|
|
80
82
|
|
|
81
83
|
Run the command directly or ask Claude to run it. Each command gathers the context it needs, asking what you're researching, discussing, or planning. Where relevant, it looks at outputs from the previous phase and offers you a choice from the list.
|
|
@@ -199,14 +201,14 @@ agents/
|
|
|
199
201
|
|
|
200
202
|
## Skills
|
|
201
203
|
|
|
202
|
-
| Skill
|
|
203
|
-
|
|
204
|
-
| [**technical-research**](skills/technical-research/)
|
|
205
|
-
| [**technical-discussion**](skills/technical-discussion/)
|
|
206
|
-
| [**technical-specification**](skills/technical-specification/)
|
|
207
|
-
| [**technical-planning**](skills/technical-planning/)
|
|
208
|
-
| [**technical-implementation**](skills/technical-implementation/) | 5
|
|
209
|
-
| [**technical-review**](skills/technical-review/)
|
|
204
|
+
| Skill | Phase | Description |
|
|
205
|
+
|------------------------------------------------------------------|-------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
206
|
+
| [**technical-research**](skills/technical-research/) | 1 | Explore ideas from their earliest seed. Investigate market fit, technical feasibility, business viability. Free-flowing exploration across technical, business, and market domains. |
|
|
207
|
+
| [**technical-discussion**](skills/technical-discussion/) | 2 | Document technical discussions as expert architect and meeting assistant. Captures context, decisions, edge cases, competing solutions, debates, and rationale. |
|
|
208
|
+
| [**technical-specification**](skills/technical-specification/) | 3 | Build validated specifications from discussion documents through collaborative refinement. Filters hallucinations, enriches gaps, produces standalone spec. |
|
|
209
|
+
| [**technical-planning**](skills/technical-planning/) | 4 | Transform specifications into actionable implementation plans with phases, tasks, and acceptance criteria. Supports multiple output formats. |
|
|
210
|
+
| [**technical-implementation**](skills/technical-implementation/) | 5 | Execute implementation plans using strict TDD workflow. Writes tests first, implements to pass, commits frequently, and gates phases on user approval. |
|
|
211
|
+
| [**technical-review**](skills/technical-review/) | 6 | Review completed implementation against specification requirements and plan acceptance criteria. Uses parallel subagents for efficient chain verification. Produces structured feedback without fixing code. |
|
|
210
212
|
|
|
211
213
|
### technical-research
|
|
212
214
|
|
|
@@ -305,21 +307,21 @@ Reviews completed work with fresh perspective. Validates implementation against
|
|
|
305
307
|
|
|
306
308
|
Slash commands to quickly invoke the workflow.
|
|
307
309
|
|
|
308
|
-
| Command
|
|
309
|
-
|
|
310
|
-
| [**/start-research**](commands/start-research.md)
|
|
311
|
-
| [**/start-discussion**](commands/start-discussion.md)
|
|
312
|
-
| [**/start-specification**](commands/start-specification.md)
|
|
313
|
-
| [**/start-planning**](commands/start-planning.md)
|
|
314
|
-
| [**/start-implementation**](commands/start-implementation.md) | Start implementing a plan. Executes tasks via strict TDD, committing after each passing test.
|
|
315
|
-
| [**/interview**](commands/interview.md)
|
|
310
|
+
| Command | Description |
|
|
311
|
+
|---------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
312
|
+
| [**/start-research**](commands/start-research.md) | Begin research exploration. For early-stage ideas, feasibility checks, and broad exploration before formal discussion. |
|
|
313
|
+
| [**/start-discussion**](commands/start-discussion.md) | Begin a new technical discussion. Gathers topic, context, background information, and relevant codebase areas before starting documentation. |
|
|
314
|
+
| [**/start-specification**](commands/start-specification.md) | Start a specification session from an existing discussion. Validates and refines discussion content into a standalone specification. |
|
|
315
|
+
| [**/start-planning**](commands/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). |
|
|
316
|
+
| [**/start-implementation**](commands/start-implementation.md) | Start implementing a plan. Executes tasks via strict TDD, committing after each passing test. |
|
|
317
|
+
| [**/interview**](commands/interview.md) | Shift into focused questioning mode during research or discussion. Probes ideas with non-obvious questions, challenges assumptions, and surfaces concerns. |
|
|
316
318
|
|
|
317
319
|
## Agents
|
|
318
320
|
|
|
319
321
|
Subagents that skills can spawn for parallel task execution.
|
|
320
322
|
|
|
321
|
-
| Agent
|
|
322
|
-
|
|
323
|
+
| Agent | Used By | Description |
|
|
324
|
+
|------------------------------------------------|------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
323
325
|
| [**chain-verifier**](agents/chain-verifier.md) | technical-review | Verifies a single plan task was implemented correctly. Checks implementation, tests (not under/over-tested), and code quality. Multiple chain-verifiers run in parallel to verify ALL tasks efficiently. |
|
|
324
326
|
|
|
325
327
|
## Requirements
|
|
@@ -62,7 +62,7 @@ Ask: **Which specification would you like to plan?**
|
|
|
62
62
|
|
|
63
63
|
Ask: **Where should this plan live?**
|
|
64
64
|
|
|
65
|
-
Load **[output-formats.md](skills/technical-planning/references/output-formats.md)** and present the available formats to help the user choose. Then load the corresponding output adapter for that format's setup requirements.
|
|
65
|
+
Load **[output-formats.md](../skills/technical-planning/references/output-formats.md)** and present the available formats to help the user choose. Then load the corresponding output adapter for that format's setup requirements.
|
|
66
66
|
|
|
67
67
|
## Step 5: Gather Additional Context
|
|
68
68
|
|
package/package.json
CHANGED
|
@@ -6,6 +6,8 @@
|
|
|
6
6
|
|
|
7
7
|
Plans can be stored in different formats. **Ask the user which format they prefer** - present the benefits from each adapter file and let them decide.
|
|
8
8
|
|
|
9
|
+
**IMPORTANT**: Only offer formats listed below. Do not invent or suggest formats that don't have corresponding `output-*.md` files in this directory.
|
|
10
|
+
|
|
9
11
|
## Available Formats
|
|
10
12
|
|
|
11
13
|
- **[Local Markdown](output-local-markdown.md)** - Single markdown file, no external tools
|