SDLC Plugin for Claude Code

A comprehensive Claude Code plugin that enhances your software development lifecycle with specialized agents, commands, and integrations.

Features

🤖 Specialized Agents

• codebase-analyzer - Deep implementation analysis with precise file:line references
• codebase-locator - Fast component location and discovery across your codebase
• codebase-pattern-finder - Pattern detection and architectural understanding
• web-search-researcher - Real-time research capabilities via web search
• implementer - Fresh-context task implementer for subagent workflow (TDD-aware, self-reviews)
• spec-reviewer - Verifies implementation matches spec exactly (nothing missing, nothing extra)
• code-quality-reviewer - Quick sanity check for obvious bugs and code smells
• research-synthesizer - Merges multiple research reports into comprehensive document with consensus tracking

⚡ Commands

• /plan - Generate detailed implementation plans with phases, complexity analysis, and validation steps
• /research - AI-powered research with project context
• /research-deep - Parallel research with 3 instances and synthesis for comprehensive coverage
• /implement - Execute implementation based on generated plans
• /review - Parallel code review with GPT-5.3-Codex and Gemini 3 Pro, consolidated findings
• /submit - Prepare and submit work for review
• /verify - Validate implementation against acceptance criteria

🎯 Skills

• codex - OpenAI Codex integration (GPT-5.3) for code analysis, review, refactoring, and automated editing
• gemini - Google Gemini 3 Pro integration for code review, plan analysis, and big context (>200k) processing
• interview - Deep interviews about any topic with iterative questioning (uses Opus)
• tdd - TDD enforcement during implementation (strict/soft/off modes via CLAUDE.md)
• finish-branch - Post-merge cleanup: switches to main, pulls, runs tests, removes worktree

🔌 Integrations

• Context7 - Up-to-date library documentation and code examples
• Perplexity Sonar (via OpenRouter) - Advanced web search and research capabilities

Installation

Prerequisites

• Claude Code CLI
• Node.js 18+ (for MCP servers)
• Bun (recommended) or npm

Install Plugin

# Clone or download the plugin
git clone <repository-url> sdlc-plugin

# Navigate to your Claude Code plugins directory
cd ~/.claude/plugins

# Copy or symlink the plugin
ln -s /path/to/sdlc-plugin sdlc-plugin

# Verify installation
claude --debug

Environment Setup

Create a .env file or set environment variables:

# Required for Perplexity Sonar integration (via OpenRouter)
export OPENROUTER_API_KEY="your-api-key"
export OPENROUTER_MODEL="perplexity/sonar-pro"  # or any OpenRouter model

Usage

Complete Workflow: Research → Plan → Issue → Implementation → PR

This plugin implements a comprehensive SDLC workflow with proper separation of concerns:

Research (Documentation)      → Plan (Specification)     → Issue (Execution)     → Code (Implementation)
research/*.md (committed)       plans/*.md (committed)     #123 (GitHub)          Branch + PR

1. Research Phase

/research "How does Next.js handle server-side rendering?"

Creates: research/[topic].md (committed to git)

• Gathers current state knowledge
• Documents existing patterns and architecture
• Becomes permanent knowledge base for the project
• Referenced from plans when relevant

2. Planning Phase

/plan "Add user authentication with OAuth2"

Creates: plans/[feature].md with YAML frontmatter

Generates comprehensive PRD including:

• Problem statement and goals
• User stories with acceptance criteria
• Functional and non-functional requirements
• 5 Implementation phases with complexity ratings
• Testing strategy and validation commands
• Risk assessment and rollback plan
• Links to related research files (in frontmatter)

What happens next:

/github:create-issue-from-plan plans/oauth-authentication.md

Creates: GitHub Issue #123 with implementation checklist Updates: Plan frontmatter with issue: 123

3. Implementation Phase

/implement #123          # Using Issue number
# OR
/implement plans/oauth-authentication.md  # Using plan file

Key differences from old workflow:

• Plan file is immutable spec (never modified during implementation)
• Issue tracks progress via checkboxes updated during work
• Use gh issue edit to update Issue body with progress
• Reference plan for requirements, reference Issue for progress

4. Submission Phase

/submit plans/oauth-authentication.md

• Verifies implementation against plan requirements
• Extracts Issue number from plan frontmatter
• Commits changes with conventional commits
• Creates PR via:

/github:create-pr #123 plans/oauth-authentication.md

PR automatically includes:

• Title: feat: #123 - Add OAuth2 authentication
• Summary from plan Overview
• Link to plan file + research files
• Review focus highlighting key decisions
• Closes #123 reference

Commands

Planning

/plan "Add user authentication with OAuth2"

Generates a comprehensive PRD with phases, complexity analysis, and validation steps.

Research

/research "How does authentication work in our API?"

Performs AI-powered research using project context and web search.

Deep Research (Parallel with Synthesis)

/research-deep "How does the authentication system work?"

Runs 3 independent research instances in parallel, then merges findings:

• Instance 1 (Breadth): Casts wide net, finds all relevant files and entry points
• Instance 2 (Depth): Deep analysis of core components, traces data flow
• Instance 3 (Patterns): Finds similar patterns elsewhere, discovers edge cases

The synthesis identifies:

• Consensus findings (discovered by multiple instances = high confidence)
• Unique discoveries (found by only one instance = valuable additions)
• Any conflicts between research reports

Use when a single research run might miss important aspects of complex codebases.

Implementation

/implement #123

OR

/implement plans/oauth-authentication.md

Executes the implementation plan with guided steps. Updates GitHub Issue checkboxes during work.

Code Review

/review                      # Review current changes (staged + unstaged)
/review origin/main...HEAD   # Review all commits on branch

Runs parallel code reviews with GPT-5.3-Codex (xhigh reasoning) and Gemini 3 Pro:

• Analyzes git diff for correctness, performance, security, maintainability
• Deduplicates findings when both reviewers flag the same issue
• Prioritizes by severity (P0-P3)
• Consolidates into unified markdown report with overall verdict

Verification

/verify plans/oauth-authentication.md

Comprehensive validation before submission:

• Compares implementation to plan requirements
• Runs production build
• Runs bun run validate (if exists) - Catches plugin schema errors, missing README docs, etc.
• Launches app and runs health checks
• Executes code review with Codex and Gemini
• Reports all issues that need fixing before submission

Submission

/submit plans/oauth-authentication.md

Prepares and submits PR:

• Automatically runs /verify if not already done - Quality gate before PR
• Validates Issue exists and is linked
• Creates commits and PR
• Returns PR URL

Recommended Workflow

/research          # Understand current implementation
    ↓
/plan              # Create comprehensive plan
    ↓
/implement #123    # Execute the plan
    ↓
/verify            # Validate before submission (build, tests, validation, code review)
    ↓
/submit            # Create PR (auto-runs /verify if needed)
    ↓
GitHub             # Review and merge

Key feature: /submit automatically runs /verify if you haven't already, ensuring no PRs are created with validation errors.

Validation Examples

Plugin Validation

When working on plugins, /verify will catch issues like:

$ /verify plans/add-new-command.md

✅ Production build passed
🔍 Running plugin validation...
❌ Validation failed:
   - Commands exist but not documented in README.md:
     - /my-new-command

Fix: Add command documentation to README.md

[Verification stops here - fix issues before running /submit]

Build Validation

For regular projects:

$ /verify plans/refactor-auth.md

✅ Production build passed
✅ Plugin validation skipped (not a plugin)
✅ App launched successfully
✅ Health checks passed
✅ Code review passed

All validations passed! Ready for submission.

Plan Frontmatter Reference

Every plan file includes YAML frontmatter for metadata and linking:

---
title: "Add OAuth2 Authentication"
type: Feature
issue: null              # Set to Issue #123 after creating Issue
research:               # Links to research files
  - research/auth-flow.md
  - research/api-architecture.md
status: Draft           # Draft | In Progress | Implemented
created: 2024-11-16
---

Fields:

• title: Plan title (matches document heading)
• type: Bug | Feature | Chore | Refactor | Enhancement | Documentation
• issue: GitHub Issue number (populated by /github:create-issue-from-plan)
• research: List of related research file paths
• status: Current status of the plan
• created: ISO date when plan was created

GitHub Integration Commands

Create Issue from Plan

/github:create-issue-from-plan plans/oauth-authentication.md

Converts plan into GitHub Issue:

• Creates Issue with plan Overview as summary
• Extracts Implementation Phases as checklist items
• Adds Validation Commands section
• Links related research files
• Updates plan frontmatter with Issue number
• Returns Issue URL

Create PR with Plan Reference

/github:create-pr #123 plans/oauth-authentication.md

Creates PR with proper documentation:

• Extracts plan type for PR label
• Links issue with Closes #123
• Includes plan file + research links
• Summarizes key decisions from Implementation Plan
• References testing and validation criteria

Agents

Agents are automatically invoked by Claude based on context, but you can also call them explicitly:

# Analyze specific implementation
"Use codebase-analyzer to understand how authentication works"

# Find components
"Use codebase-locator to find all API route handlers"

# Discover patterns
"Use codebase-pattern-finder to identify data validation patterns"

Skills

Skills are invoked when you reference their capabilities:

# Codex
"Use codex to refactor this module with high reasoning effort"

# Gemini
"Use gemini to analyze this architecture"

# Interview
/interview plans/my-feature.md           # Interview about a plan file
/interview "authentication system"       # Interview about a concept
/interview src/auth/login.ts             # Interview about existing code

Configuration

Plugin Manifest

Located at .claude-plugin/plugin.json:

{
  "name": "sdlc-plugin",
  "description": "Contains tools for software development lifecycle",
  "version": "1.0.0",
  "author": {
    "name": "Ladislav Martincik",
    "url": "https://github.com/iamladi"
  },
  "license": "MIT"
}

MCP Servers

Configure in .mcp.json:

{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": ["-y", "@upstash/context7-mcp@latest"]
    },
    "perplexity": {
      "command": "bun",
      "args": ["${CLAUDE_PLUGIN_ROOT}/utils/perplexity-mcp/index.ts"],
      "env": {
        "OPENROUTER_API_KEY": "${OPENROUTER_API_KEY}",
        "OPENROUTER_MODEL": "${OPENROUTER_MODEL:-perplexity/sonar-pro}"
      }
    }
  }
}

Structure

sdlc-plugin/
├── .claude-plugin/
│   └── plugin.json          # Plugin manifest
├── agents/
│   ├── codebase-analyzer.md
│   ├── codebase-locator.md
│   ├── codebase-pattern-finder.md
│   ├── code-quality-reviewer.md  # Quick quality sanity check
│   ├── implementer.md            # Fresh-context task implementer
│   ├── spec-reviewer.md          # Spec compliance reviewer
│   ├── test-writer.md
│   └── web-search-researcher.md
├── commands/
│   ├── plan.md
│   ├── research.md
│   ├── implement.md         # Subagent-driven workflow
│   ├── review.md
│   ├── submit.md
│   └── verify.md
├── skills/
│   ├── codex/SKILL.md
│   ├── finish-branch/SKILL.md   # Post-merge cleanup
│   ├── gemini/SKILL.md
│   ├── interview/SKILL.md
│   ├── tdd/SKILL.md             # TDD enforcement
│   └── test/SKILL.md
├── utils/
│   └── perplexity-mcp/
│       └── index.ts         # Perplexity Sonar MCP server (via OpenRouter)
├── logs/                    # Hook execution logs
├── .mcp.json               # MCP server configuration
├── README.md
└── CHANGELOG.md

Agent Details

codebase-analyzer

Analyzes implementation details with surgical precision:

• Traces data flow and control flow
• Documents key logic with file:line references
• Identifies architectural patterns
• Maps API contracts between components

Example:

Use codebase-analyzer to understand how webhook validation works

codebase-locator

Fast component discovery:

• Finds files, functions, and classes
• Searches by name patterns
• Locates configuration and dependencies

Example:

Use codebase-locator to find all authentication middleware

codebase-pattern-finder

Pattern and architecture analysis:

• Identifies design patterns in use
• Discovers architectural decisions
• Finds common conventions
• Maps integration points

Example:

Use codebase-pattern-finder to identify repository patterns

implementer

Subagent for implementing individual tasks from a plan:

• Operates with fresh context per task
• TDD-aware (respects project's tdd: setting)
• Self-reviews before handoff
• Commits atomic changes
• Can ask questions when unclear

Invoked by: /implement controller, not directly

spec-reviewer

Verifies implementation matches specification exactly:

• Nothing missing from spec
• Nothing extra beyond spec
• Returns PASS or list of issues
• Binary verdict for clean feedback

Invoked by: /implement controller after implementer completes

code-quality-reviewer

Quick sanity check for obvious issues:

• Clear bugs (null access, off-by-one)
• Code smells (massive functions, deep nesting)
• Security red flags (hardcoded secrets, injection)
• Anti-patterns

Not exhaustive - use /review for thorough analysis.

Invoked by: /implement controller after spec review passes

Development

Adding Custom Agents

Create agents/your-agent.md:

---
name: your-agent
description: What this agent does
tools: Read, Grep, Glob
model: sonnet
---

Your agent prompt and instructions here...

Adding Custom Commands

Create commands/your-command.md:

# Your Command Title

Command description and instructions...

## Arguments
$ARGUMENTS

## Instructions
...

Debugging

# Enable debug mode
claude --debug

# Check plugin loading
grep "sdlc-plugin" ~/.claude/logs/debug.log

# Verify component registration
claude --list-plugins

Troubleshooting

Plugin Not Loading

1. Verify .claude-plugin/plugin.json exists and has valid JSON
2. Check file permissions are readable
3. Run claude --debug to see loading errors
4. Verify directory structure matches expected layout

MCP Servers Not Working

1. Check Node.js is installed and accessible
2. Verify environment variables are set (OPENROUTER_API_KEY)
3. Test MCP servers independently:

   npx -y @upstash/context7-mcp@latest

Commands Not Appearing

1. Ensure command files are in commands/ directory
2. Check markdown files have proper frontmatter (if required)
3. Restart Claude Code session
4. Use claude --debug to verify command registration

Contributing

Contributions welcome! Please:

1. Fork the repository
2. Create a feature branch
3. Make your changes
4. Add tests if applicable
5. Submit a pull request

License

MIT License - see LICENSE file for details

Support

• Documentation: Claude Code Plugin Reference
• Issues: GitHub Issues
• Author: Ladislav Martincik

Changelog

See CHANGELOG.md for version history and updates.