By galando
Execute PIV methodology with Spec-Kit for structured TDD workflows in Java/Spring Boot backends and React/TypeScript frontends: analyze root causes of issues from GitHub/Jira, generate specs/plans/PRDs, implement fixes/features via RED-GREEN-REFACTOR on feature branches, validate with full test suites, perform code reviews, extract learning insights, and produce execution reports.
Root Cause Analysis for GitHub issues, Jira tickets, or direct bug descriptions
Implement fix from Root Cause Analysis
Manually refresh codebase context (optional — plan-feature auto-primes)
Create comprehensive feature plan with split spec artifacts (spec, plan, tasks)
Execute implementation from tasks.md or single plan file
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.
PIV (Prime-Implement-Validate) + Spec-Kit: Structured specs, strict TDD, for AI-assisted development.
Zero-setup workflow - just run /piv-speckit:plan-feature and context loads automatically!
A Claude Code plugin for structured AI-assisted development.
PIV = Prime → Implement → Validate
A development methodology for AI-assisted software development:
→ Interactive Visual Guide | → Full Methodology | → Changelog
This framework integrates best practices from GitHub's Spec-Kit, adding structured specification artifacts to the PIV methodology.
| Artifact | Purpose | Created By |
|---|---|---|
spec.md | Functional requirements (WHAT) | /piv-speckit:plan-feature |
plan.md | Technical approach (HOW) | /piv-speckit:plan-feature |
tasks.md | Implementation steps (DO) | /piv-speckit:plan-feature |
quickstart.md | TL;DR for humans | /piv-speckit:plan-feature |
prime-context.md | Codebase context (auto-generated) | Auto-prime in plan-feature |
All artifacts are structured Markdown - human-readable and version-controlled.
# Add marketplace
/plugin marketplace add galando/piv-speckit
# Install PIV + Spec-Kit
/plugin install piv-speckit
Commands: /piv-speckit:plan-feature (auto-primes), /piv-speckit:execute, /piv-speckit:prime (optional)
Features: Auto-activating skills (TDD, code-review, security), full reference docs, agent context system.
┌─────────────────────────────────────────────────────────────────────────────┐
│ PIV SPEC-KIT WORKFLOW │
├─────────────────────────────────────────────────────────────────────────────┤
│ │
│ 1. PLAN (Auto-Primes + Structured Specs) │
│ ┌─────────────────────────────────────────────────────────────────┐ │
│ │ /piv-speckit:plan-feature "Add user authentication" │ │
│ │ │ │
│ │ → Auto-prime: loads/refreshes context silently │ │
│ │ → Creates .claude/specs/{feature}/ │ │
│ │ ├─ spec.md (WHAT: requirements, user stories) │ │
│ │ ├─ plan.md (HOW: architecture, data model, APIs) │ │
│ │ ├─ tasks.md (DO: step-by-step implementation) │ │
│ │ └─ quickstart.md (TL;DR: quick reference) │ │
│ └─────────────────────────────────────────────────────────────────┘ │
│ ↓ │
│ 2. IMPLEMENT (Strict TDD) │
│ ┌─────────────────────────────────────────────────────────────────┐ │
│ │ /piv-speckit:execute .claude/specs/{feature}/tasks.md │ │
│ │ │ │
│ │ For each task: │ │
│ │ ├─ RED: Write failing test first │ │
│ │ ├─ GREEN: Write minimal code to pass │ │
│ │ └─ REFACTOR: Improve while tests stay green │ │
│ │ │ │
│ │ Skills auto-activate: TDD, code-review, security │ │
│ └─────────────────────────────────────────────────────────────────┘ │
│ ↓ │
npx claudepluginhub galando/piv-speckit --plugin pivTemper: Quality gates, blast radius analysis, and intent-driven development for AI-generated code
Spectacular skills/commands library for spec-anchored development and parallel task execution
Spec Driven Development toolkit - structured specification, planning, and implementation workflows for systematic feature development
Specification-Driven Development with Process Discipline for Claude Code
Specification-driven development workflow: specify → plan → tasks → implement
GitHub specification integration and verification
Spec-driven development pipeline for Claude Code: interview-to-spec, spec-approach, tdd, verify, diagnose, and a feature orchestrator.