start-specification

Consolidate concluded discussions into a standalone specification session.

27|1|Updated Nov 23, 2025
One-click install
npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-specification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-specification
Source: https://github.com/leeovery/claude-technical-workflows/tree/main/skills/start-specification
Command: npx skills add https://github.com/leeovery/claude-technical-workflows --skill start-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams transition from scattered, incomplete discussions to a cohesive specification session by analyzing conclusions, consolidating related topics, and preparing a formal spec draft.

Core Features & Use Cases

  • Discovery & consolidation: identifies available discussions, evaluates whether multiple topics should be grouped into a single specification, and flags naming conflicts with anchored specs.
  • Decision routing: presents options to continue an in-progress spec, create a new grouped spec, or proceed with individual specs, based on cache state.
  • Skill orchestration: invokes the technical-specification skill to transform discussions into a finalized specification, with provenance and traceability.
  • Cache & provenance: persists grouping analyses to docs/workflow/.cache and preserves anchored names for continuity across runs.

Quick Start

Start a specification session from the current discussions by kicking off the start-specification flow. It will discover discussions, analyze groupings, and prepare the path to the technical-specification skill.

Frequently Asked Questions about start-specification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn scattered discussions into a single actionable specification?

You can turn scattered discussions into an actionable specification by analyzing concluded conversations, consolidating related topics, and preparing a formal draft while preserving anchored names for continuity.

What is the best way to consolidate multiple discussions into one specification session?

Consolidating multiple discussions involves evaluating grouping opportunities for related topics, caching the grouping analysis, and routing decisions to either create a grouped spec or proceed with individual specs.

How does grouping analysis work when starting a specification from discussions?

Grouping analysis works by assessing concluded discussions to identify consolidation opportunities, persisting the analysis to a cache directory, and presenting guided options to group, reanalyze, or proceed with the specification.

Can I continue an in-progress specification if I already have cached grouping analyses?

Yes, you can continue an in-progress specification because the workflow evaluates the cache state and presents routing options to either resume the existing spec or start a new grouped specification.

How are finalized specifications generated after discussions are consolidated?

Finalized specifications are generated through skill orchestration that invokes a technical-specification process to transform the consolidated discussions, ensuring provenance and traceability throughout the workflow.

Why does my specification workflow preserve anchored names and cache grouping analyses?

Your specification workflow preserves anchored names and caches grouping analyses to maintain provenance, ensure continuity across multiple runs, and flag naming conflicts with existing anchored specifications.