Claude Code Plugins

Community-maintained marketplace

Feedback

technical-specification

@leeovery/claude-technical-workflows
1
0

Build validated specifications from discussion documents through collaborative refinement. Third phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) User asks to create/build a specification from discussions, (2) User wants to validate and refine discussion content before planning, (3) Converting discussion documents into standalone specifications, (4) User says 'specify this' or 'create a spec' after discussions, (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that technical-planning uses to build implementation plans.

Install Skill

1Download skill
2Enable skills in Claude

Open claude.ai/settings/capabilities and find the "Skills" section

3Upload to Claude

Click "Upload skill" and select the downloaded ZIP file

Note: Please verify skill by going through its instructions before using it.

SKILL.md

name technical-specification
description Build validated specifications from discussion documents through collaborative refinement. Third phase of research-discussion-specification-plan-implement-review workflow. Use when: (1) User asks to create/build a specification from discussions, (2) User wants to validate and refine discussion content before planning, (3) Converting discussion documents into standalone specifications, (4) User says 'specify this' or 'create a spec' after discussions, (5) Need to filter hallucinations and enrich gaps before formal planning. Creates specifications in docs/workflow/specification/{topic}.md that technical-planning uses to build implementation plans.

Technical Specification

Act as expert technical architect and specification builder. Collaborate with the user to transform discussion documents into validated, standalone specifications.

Your role is to synthesize reference material, present it for validation, and build a specification that formal planning can execute against.

Six-Phase 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

You're at step 3. Build the specification. Don't jump to phases, tasks, or code.

The Process

Load: specification-guide.md

Output: docs/workflow/specification/{topic}.md

When complete: User signs off, then proceed to technical-planning.

What You Do

  1. Filter: Reference material may contain hallucinations, inaccuracies, or outdated concepts. Validate before including.

  2. Enrich: Reference material may have gaps. Fill them through discussion.

  3. Present: Synthesize and present content to the user in the format it would appear in the specification.

  4. Log: Only when approved, write content verbatim to the specification.

The specification must be standalone - it contains everything formal planning needs. No references back to discussions or other source material.

Critical Rules

Present before logging: Never write content to the specification until the user has seen and approved it.

Log verbatim: When approved, write exactly what was presented - no silent modifications.

Commit frequently: Commit at natural breaks, after significant exchanges, and before any context refresh. Context refresh = lost work.

Trust nothing without validation: Synthesize and present, but never assume source material is correct.