Official DinCoder plugin marketplace for spec-driven development workflows
npx claudepluginhub flight505/dincoder-pluginSpec-driven development workflow with DinCoder MCP server. Transform ideas into implementation through structured specifications, technical plans, and actionable tasks.
Claude Code marketplace entries for the plugin-safe Antigravity Awesome Skills library and its compatible editorial bundles.
Production-ready workflow orchestration with 79 focused plugins, 184 specialized agents, and 150 skills - optimized for granular installation and minimal token usage
Curated collection of 141 specialized Claude Code subagents organized into 10 focused categories
Transform your development workflow with spec-driven methodology. This plugin integrates the DinCoder MCP server with Claude Code, providing slash commands, specialized agents, and workflow automation.
✨ Slash Commands - Quick access to spec-driven workflows 🤖 Specialized Agents - Expert assistance for specifications, planning, and task management 📊 Progress Tracking - Real-time analytics and dependency visualization 🔧 MCP Server Integration - Automatic installation and configuration 📝 Quality Gates - Validation to ensure high-quality specifications
Before installing, ensure you have:
Check your versions:
claude --version # Should show >= 2.0.13
node --version # Should show >= 18
npm --version
Step 1: Add the DinCoder marketplace
# In Claude Code
/plugin marketplace add flight505/dincoder-plugin
Step 2: Install the plugin
/plugin install dincoder
Step 3: Restart Claude Code
Cmd+Q) and reopen, or press Cmd+Shift+P → "Developer: Reload Window"Alt+F4) and reopen, or press Ctrl+Shift+P → "Developer: Reload Window"After restarting, verify the plugin is active:
1. Check slash commands:
# Type / in Claude Code
# You should see: /spec, /plan, /tasks, /progress, /validate, /next
2. Check specialized agents:
# Type @ in Claude Code
# You should see: @spec-writer, @plan-architect, @task-manager
3. Check MCP server:
Troubleshooting: If commands don't appear:
Help → Toggle Developer Tools/plugin uninstall dincoder then /plugin install dincoder/spec
Follow the guided workflow to create a detailed specification.
/plan
Transform your specification into a technical implementation plan.
/tasks
Generate an actionable task list with dependencies and metadata.
/progress
View comprehensive progress report with statistics and charts.
| Command | Description |
|---|---|
/spec | Create or refine project specification |
/plan | Generate technical implementation plan |
/tasks | Break down plan into actionable tasks |
/progress | View progress report with analytics |
/validate | Check specification quality |
/next | Show next actionable tasks |
Access specialized agents by typing @:
| Agent | Expertise |
|---|---|
@spec-writer | Creating validated specifications |
@plan-architect | Designing technical implementation plans |
@task-manager | Managing tasks and tracking progress |
The plugin implements a proven spec-driven methodology:
1. Specify → Define WHAT to build
├── /spec - Create specification
└── /validate - Check quality
2. Plan → Design HOW to build it
└── /plan - Generate implementation plan
3. Execute → Build following tasks
├── /tasks - Create task list
└── /next - Show actionable tasks
4. Track → Monitor progress
└── /progress - View analytics
The plugin creates a .dincoder/ directory in your project:
.dincoder/
├── spec.md # Project specification (WHAT)
├── plan.md # Implementation plan (HOW)
├── tasks.md # Actionable task list
├── research.md # Technical decisions log
└── constitution.json # Project principles
The plugin automatically installs and configures the DinCoder MCP server, providing 26 tools:
Project Setup: specify_start, prereqs_check, constitution_create
Specification: specify_describe, spec_validate, spec_refine, clarify_add/resolve/list
Planning: plan_create, artifacts_analyze
Task Management: tasks_generate, tasks_visualize, tasks_filter, tasks_search, tasks_stats, tasks_tick, tasks_tick_range
Quality: quality_format, quality_lint, quality_test
Research: research_append, artifacts_read
# Use the spec command
/spec
# Claude guides you through:
# - Problem definition
# - User requirements
# - Acceptance criteria
# - Edge cases
# - Out of scope items