By spec2ship
Facilitate AI-driven roundtable discussions that guide the entire software development lifecycle—from requirement specification and architecture decisions to implementation planning and code quality validation—using structured templates, multi-perspective agents, and session management.
Show current roundtable session status. Use subcommands for more options.
- Current directory: !`pwd`
Close a session and mark it as closed. Works with any workflow type (specs, design, brainstorm, roundtable).
- Current directory: !`pwd`
Show detailed status of a specific session or the current session.
Use this agent for quality perspective in roundtable discussions. Focuses on testability, edge cases, acceptance criteria. Receives YAML input, returns YAML output.
Use this agent for security perspective in roundtable discussions. Focuses on threat modeling, secure design, OWASP compliance. Receives YAML input, returns YAML output.
Use this agent for architecture perspective in roundtable discussions. Evaluates system structure, patterns, scalability. Receives YAML input, returns YAML output.
Use this agent for implementation perspective in roundtable discussions. Assesses feasibility, code quality, effort. Receives YAML input, returns YAML output.
Use this agent for user experience perspective in roundtable discussions. Focuses on user needs, usability, accessibility, user journeys. Receives YAML input, returns YAML output.
This skill should be used when the user asks to 'add to backlog', 'update backlog', 'check backlog', 'list backlog items', 'prioritize backlog'. Provides conventions for managing the project backlog in .s2s/BACKLOG.md.
This skill should be used when the user asks to 'write commit message', 'create conventional commit', 'format git commit', 'follow commit conventions', 'structure commit message'. Provides Conventional Commits patterns for consistent, machine-readable commit messages.
This skill should be used when the user asks to 'model the domain', 'identify bounded contexts', 'map domain relationships', 'run event storming', 'define ubiquitous language', 'analyze domain complexity'. Provides DDD strategic patterns for requirements and design.
This skill should be used when developing or maintaining s2s plugin code. Provides check definitions for instruction quality, consistency, resume capability, and edge cases. NOT SHIPPED with plugin.
This skill should be used when the user asks to 'define quality requirements', 'write non-functional requirements', 'structure NFRs', 'apply ISO 25010', 'specify quality characteristics'. Provides ISO 25010 quality model patterns for comprehensive requirements coverage.
Uses power tools
Uses Bash, Write, or Edit tools
Runs pre-commands
Contains inline bash commands via ! syntax
Bash prerequisite issue
Uses bash pre-commands but Bash not in allowed tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Spec2Ship is a Claude Code plugin that adds structured orchestration for requirements, architecture, and implementation planning.
The core idea: instead of prompting Claude Code directly, you run roundtable discussions where multiple agents, each representing a real role, debate and refine decisions collaboratively.
It is:
It is not:
[!NOTE] Spec2Ship requires Claude Code to run. It extends Claude Code with structured workflows, not replaces it.
When you prompt Claude Code directly for requirements or architecture decisions:
| What happens | The problem |
|---|---|
| Single perspective | Optimized for agreement rather than rigorous challenge |
| No adversarial review | Security gaps, edge cases, feasibility issues missed |
| Freeform output | Hard to review, audit, or hand off to team |
| Ephemeral sessions | Context lost between conversations |
| No structure | Each session starts from scratch |
Spec2Ship solves this by:
| Aspect | Spec2Ship | Claude-Flow | Spec-Kit | OpenSpec |
|---|---|---|---|---|
| Approach | Multi-agent deliberation | Swarm task execution | Document checkpoints | Lightweight diffs |
| Agents | 12 specialized roles debating | 54+ task workers | Single agent | Single agent |
| Quality mechanism | Adversarial review built-in | Speed optimization | Human review points | Minimal overhead |
| Strategies | 5 facilitation methods | Hierarchical/mesh | Linear | Linear |
| Output | arc42, ISO 25010, MADR | Custom | Markdown | Diff-based |
| Best for | Decisions needing debate | Parallel task execution | Greenfield features | Brownfield changes |
Choose Spec2Ship when:
Choose alternatives when:
# 1. Add the plugin
/plugin marketplace add spec2ship/spec2ship
# 2. Install it
/plugin install s2s
# 3. Initialize your project
/s2s:init
# 4. Run your first roundtable
/s2s:specs
After /s2s:specs completes, you'll have:
.s2s/sessions/YYYYMMDD-specs-*.yaml: full discussion transcript.s2s/requirements.md: structured requirements with IDs (REQ-001, REQ-002...)[!TIP] For your first run, use
/s2s:specs --interactiveto pause after each round and see how the discussion unfolds.
Roundtable is the fundamental abstraction of Spec2Ship.
Every major decision flows through a structured discussion:
npx claudepluginhub spec2ship/spec2ship --plugin s2sAn agent-routed harness for end-to-end software product development
Ship software systematically: project lifecycle, TDD, parallel agents, code review, security auditing, and infrastructure validation
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Spec-driven development for big features. When features get too big, plan mode gets too vague—leading to hallucinations during implementation. ShipSpec replaces vague plans with structured PRDs, technical designs, and ordered tasks that keep Claude grounded.
Spec-Driven Development (SDD) plugin for Claude Code providing a comprehensive workflow for building features with requirements, design, tasks, and implementation phases.
Specification-driven development workflow: specify → plan → tasks → implement