By jsegov
Replace vague planning with structured PRDs, technical designs, and ordered tasks that keep Claude grounded during large feature implementation. Generates TASKS.json/md files with phased tasks, dependencies, and acceptance criteria, then automates end-to-end implementation and review against those artifacts.
Cancel active feature implementation retry loop
Cancel active task implementation loop
Start planning a new feature with AI-assisted PRD generation
Implement all tasks for a feature end-to-end automatically
Implement a specific task or the next available task from TASKS.json
You are a senior software architect creating technical design documents. Your designs should be detailed enough that another developer (or coding agent) can implement without needing clarification.
You are a planning alignment validator who verifies that task implementations align with the Software Design Document (SDD) and Product Requirements Document (PRD).
You are a senior product manager specializing in requirements elicitation. Your goal is to help the user define a clear, comprehensive PRD through structured conversation.
You are a task lifecycle manager that parses TASKS.json files, tracks task states, manages dependencies, and provides structured task information for implementation commands.
You are a technical project manager specializing in breaking down features into well-defined, implementable tasks. Your task lists should be immediately usable by coding agents.
This skill should be used when the user asks to "generate tasks", "create implementation plan", "break down feature", "write agent prompts", "decompose into tasks", "create work items", or when creating agent-ready task descriptions from PRD and SDD documents.
This skill should be used when the user asks to "analyze the codebase", "understand the tech stack", "extract project patterns", "get codebase context", "what technologies are used", or when preparing context for planning documents, PRDs, or design documentation.
This skill should be used when the user asks to "create a PRD", "write requirements", "document a feature", "generate product spec", "define requirements", "write feature specifications", or when creating PRD documents from gathered requirements.
This skill should be used when the user asks to "research documentation", "find framework docs", "search for best practices", "look up API documentation", "find implementation patterns", "research how to implement", or when gathering external technical knowledge to inform planning or design decisions.
This skill should be used when the user asks to "create a design document", "write technical specs", "document architecture", "generate SDD", "design the system", "API design", or when creating technical design documents from approved PRDs.
Uses power tools
Uses Bash, Write, or Edit tools
Has parse errors
Some configuration could not be fully parsed
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.
Runs pre-commands
Runs pre-commands
Contains inline bash commands via ! syntax
Contains inline bash commands via ! syntax
Spec-driven development meets the Ralph Wiggum loop.
Two problems plague AI-assisted coding:
Vibe coding — Throwing prompts at Claude without structure. It makes plausible-sounding but wrong assumptions. The bigger the feature, the more it drifts.
Giving up too early — Claude does its best attempt, exits, and you're left debugging half-finished work.
ShipSpec solves both. Specs keep Claude grounded. Ralph loops keep Claude iterating until it's actually done.
┌─────────────────────────────────────────────────────────────┐
│ THE SPEC SIDE │
│ │
│ Feature Idea │
│ ↓ │
│ PRD (what to build + numbered requirements) │
│ ↓ │
│ SDD (how to build it + architecture decisions) │
│ ↓ │
│ TASKS.json (ordered work + acceptance criteria) │
└─────────────────────────────────────────────────────────────┘
┌─────────────────────────────────────────────────────────────┐
│ THE RALPH SIDE │
│ │
│ while task_not_verified: │
│ implement(task) │
│ verify(acceptance_criteria) │
│ if failed: retry with feedback │
└─────────────────────────────────────────────────────────────┘
Together: Each task carries its requirements, design context, and verification criteria. The Ralph loop keeps running until those criteria pass. Claude can't drift because the spec is always there. It can't give up because the loop keeps it going.
| Problem | Solution |
|---|---|
| Vibe coding makes Claude drift | Structured PRD with numbered requirements |
| Claude forgets original intent | Requirements linked to every task |
| Architecture decisions get contradicted | SDD documents design choices upfront |
| Claude gives up on first attempt | Ralph loops retry until verified |
/plugin marketplace add jsegov/shipspec-claude-code-plugin
/plugin install shipspec@shipspec-marketplace
# Start planning a new feature with a description (or run interactively)
/feature-planning "Add user authentication with OAuth2 and session management"
/feature-planning # prompts for description interactively
# Implement tasks one by one (or specify a task ID)
/implement-task user-auth-oauth2
/implement-task user-auth-oauth2 3 # implement specific task
Run /feature-planning with a description to go through the complete planning workflow:
/feature-planning "Add user authentication with OAuth2 and session management"
The command auto-generates a directory name (e.g., user-auth-oauth2) and guides you through 7 phases:
Feature Description - Gather or confirm the feature description, auto-generate directory name
Setup - Creates .shipspec/planning/<generated-name>/ and extracts codebase context
Requirements Gathering - Interactive Q&A with the PRD Gatherer agent about:
PRD Generation - Creates structured PRD with numbered requirements
Technical Decisions - Interactive Q&A about:
SDD Generation - Creates technical design document with:
Task Generation - Automatically creates implementation tasks with:
After completing the feature planning workflow:
.shipspec/planning/your-feature/
├── PRD.md # Product Requirements Document
├── SDD.md # Software Design Document
└── TASKS.md # Implementation tasks with agent prompts
npx claudepluginhub jsegov/shipspec-claude-code-plugin --plugin shipspecSpecification-driven development workflow: specify → plan → tasks → implement
Spec-driven development using GitHub spec-kit methodology. Constitution-first approach with specify, plan, tasks, and implement phases.
AI Coding Agent - PRD to tasks to implementation loop
AI-powered cascading development framework with design document system and multi-agent collaboration. Breaks down projects into Features (Mega Plan), Features into Stories (Hybrid Ralph), with auto-generated technical design docs, dependency-driven batch execution, Git Worktree isolation, and support for multiple AI agents (Codex, Amp, Aider, etc.).
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Provider-agnostic skills for autonomous product development: spec, task, implement, test, review, and summarize changes.