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.
/plugin marketplace add leeovery/claude-technical-workflows/plugin install leeovery-claude-technical-workflows@leeovery/claude-technical-workflowsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
references/specification-guide.mdAct 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.
You're at step 3. Build the specification. Don't jump to phases, tasks, or code.
Load: specification-guide.md
Output: docs/workflow/specification/{topic}.md
When complete: User signs off, then proceed to technical-planning.
Filter: Reference material may contain hallucinations, inaccuracies, or outdated concepts. Validate before including.
Enrich: Reference material may have gaps. Fill them through discussion.
Present: Synthesize and present content to the user in the format it would appear in the specification.
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.
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.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.