@leeovery/claude-technical-workflows 2.0.16 → 2.0.18

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.
Files changed (24) hide show
  1. package/README.md +41 -24
  2. package/commands/link-dependencies.md +9 -9
  3. package/commands/start-discussion.md +6 -313
  4. package/commands/start-feature.md +80 -0
  5. package/commands/start-implementation.md +7 -162
  6. package/commands/start-planning.md +7 -86
  7. package/commands/start-research.md +7 -13
  8. package/commands/start-specification.md +7 -81
  9. package/commands/workflow:start-discussion.md +339 -0
  10. package/commands/workflow:start-implementation.md +187 -0
  11. package/commands/workflow:start-planning.md +111 -0
  12. package/commands/workflow:start-research.md +38 -0
  13. package/commands/workflow:start-review.md +112 -0
  14. package/commands/workflow:start-specification.md +106 -0
  15. package/package.json +1 -1
  16. package/skills/technical-discussion/SKILL.md +13 -8
  17. package/skills/technical-implementation/SKILL.md +23 -11
  18. package/skills/technical-planning/SKILL.md +17 -13
  19. package/skills/technical-planning/references/formal-planning.md +97 -5
  20. package/skills/technical-research/SKILL.md +13 -9
  21. package/skills/technical-review/SKILL.md +26 -9
  22. package/skills/technical-review/references/review-checklist.md +4 -2
  23. package/skills/technical-specification/SKILL.md +16 -9
  24. package/skills/technical-specification/references/specification-guide.md +8 -9
package/skills/technical-specification/references/specification-guide.md CHANGED
@@ -20,13 +20,14 @@ The specification is the **bridge document** - a workspace for collecting valida
20
20
 
21
21
  ## Source Materials
22
22
 
23
- Before starting any topic, review ALL available reference material:
24
- - Discussion documents (from technical-discussion phase)
25
- - Any existing partial plans
26
- - Any existing partial specifications
27
- - Related documentation
23
+ Before starting any topic, identify ALL available reference material:
24
+ - Discussion documents (if they exist)
25
+ - Existing partial plans or specifications
26
+ - Requirements, design docs, related documentation
27
+ - User-provided context or transcripts
28
+ - Inline feature descriptions
28
29
 
29
- **Treat all source material as untrusted input.** Even discussion documents that went through a collaborative process may contain issues. Your job is to synthesize and present - the user validates.
30
+ **Treat all source material as untrusted input**, whether it came from the discussion phase or elsewhere. Your job is to synthesize and present - the user validates.
30
31
 
31
32
  ## The Workflow
32
33
 
@@ -160,11 +161,9 @@ This section feeds into the planning phase, where dependencies become blocking r
160
161
 
161
162
  Analyze the specification in isolation - identify what it references that must exist, not what you know exists elsewhere in the project.
162
163
 
163
- ## Transitioning to Formal Planning
164
+ ## Completion
164
165
 
165
166
  Specification is complete when:
166
167
  - All topics/phases have validated content
167
168
  - User confirms the specification is complete
168
169
  - No blocking gaps remain
169
-
170
- Then proceed to formal planning with the **technical-planning** skill.