| name | spec-gen |
| description | Specification generation pipeline for software projects.
Transforms discovery collateral (meeting transcripts, Linear issues, Slack threads,
deep research documents, user conversations) into implementation-ready specifications.
Uses Agent Teams for parallel codebase research and a composable phase pipeline
with validation gates between phases.
Keywords: spec, specification, requirements, design, tasks, discovery,
research, pipeline, transcript, planning, EARS, technical design.
|
Spec Generator
A composable specification generation pipeline. All commands use the spec: namespace.
Available Commands
| Command | Description |
|---|
/spec:init <name> | Initialize a new spec project with configured input sources |
/spec:discover | Ingest sources and produce discovery + research briefs |
/spec:research | Run Agent Teams parallel research on the codebase |
/spec:requirements | Generate EARS-format requirements from discovery & research |
/spec:design | Generate technical design from requirements |
/spec:tasks | Generate task breakdown and progress tracker |
/spec:pipeline <name> | Run full pipeline with validation gates between phases |
/spec:epic <name> | Initialize an epic with spec breakdown and ticket manifest |
/spec:epic-status [name] | Show aggregate epic progress and ticket status |
/spec:epic-pipeline <name> | Run pipeline for specs within an epic |
When to Use
Use this plugin when:
- You have meeting transcripts, tickets/issues, or Slack threads to turn into specs
- You need to create implementation-ready documentation for a feature
- You want structured requirements, design, and task breakdown
- You're starting a new feature and need to go from discovery to implementation plan
- Breaking a large set of tickets into multiple focused specs (use epics)
- Tracking ticket-to-spec-to-requirement traceability across related specs
Pipeline Flow
Standalone: init → discover → research → requirements → design → tasks
Epic: epic → [init → discover → research → requirements → design → tasks] × N specs
Each phase produces artifacts that feed the next. Phases can be run individually or orchestrated via /spec:pipeline. For epics, /spec:epic-pipeline orchestrates multiple specs in dependency order.
