@leeovery/claude-technical-workflows 2.0.15 → 2.0.17

package/skills/technical-specification/SKILL.md

@@ -9,16 +9,23 @@ Act as **expert technical architect** and **specification builder**. Collaborate
 
 Your role is to synthesize reference material, present it for validation, and build a specification that formal planning can execute against.
 
-## Six-Phase Workflow
+## Purpose in the Workflow
 
-1. **Research** (previous): EXPLORE - ideas, feasibility, market, business, learning
-2. **Discussion** (previous): WHAT and WHY - decisions, architecture, edge cases
-3. **Specification** (YOU): REFINE - validate, filter, enrich into standalone spec
-4. **Planning** (next): HOW - phases, tasks, acceptance criteria
-5. **Implementation** (after): DOING - tests first, then code
-6. **Review** (final): VALIDATING - check work against artifacts
+This skill can be used:
+- **Sequentially** (Phase 3): After discussion documents exist
+- **Standalone** (Contract entry): With reference material from any source (research docs, conversation transcripts, design documents, inline feature description)
 
-You're at step 3. Build the specification. Don't jump to phases, tasks, or code.
+Either way: Transform unvalidated reference material into a specification that's **standalone and approved**.
+
+### What This Skill Needs
+
+- **Source material** (required) - The content to synthesize into a specification. Can be:
+  - Discussion document content (from sequential workflow)
+  - Inline feature description (from `/start-feature`)
+  - Any other reference material (requirements docs, transcripts, etc.)
+- **Topic name** (required) - Used for the output filename
+
+**If missing:** Will ask user to provide context or point to source files.
 
 ## The Process
 
@@ -26,7 +33,7 @@ You're at step 3. Build the specification. Don't jump to phases, tasks, or code.
 
 **Output**: `docs/workflow/specification/{topic}.md`
 
-**When complete**: User signs off, then proceed to technical-planning.
+**When complete**: User signs off on the specification.
 
 ## What You Do
 

package/skills/technical-specification/references/specification-guide.md

@@ -20,13 +20,14 @@ The specification is the **bridge document** - a workspace for collecting valida
 
 ## Source Materials
 
-Before starting any topic, review ALL available reference material:
-- Discussion documents (from technical-discussion phase)
-- Any existing partial plans
-- Any existing partial specifications
-- Related documentation
+Before starting any topic, identify ALL available reference material:
+- Discussion documents (if they exist)
+- Existing partial plans or specifications
+- Requirements, design docs, related documentation
+- User-provided context or transcripts
+- Inline feature descriptions
 
-**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.
+**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.
 
 ## The Workflow
 
@@ -160,11 +161,9 @@ This section feeds into the planning phase, where dependencies become blocking r
 
 Analyze the specification in isolation - identify what it references that must exist, not what you know exists elsewhere in the project.
 
-## Transitioning to Formal Planning
+## Completion
 
 Specification is complete when:
 - All topics/phases have validated content
 - User confirms the specification is complete
 - No blocking gaps remain
-
-Then proceed to formal planning with the **technical-planning** skill.