Skip to content

vt-c-speckit-integration

Bridges GitHub Spec-Kit specification workflow with quality toolkit. Activates when SpecKit artifacts are detected (.specify/ directory, specs/, constitution.md) or when spec-kit commands are used.

Plugin: core-standards
Category: SpecKit
Command: /vt-c-speckit-integration

SpecKit Integration

This skill bridges GitHub Spec-Kit with our quality toolkit, enabling a combined workflow for spec-driven development with built-in quality enforcement.

When This Skill Activates

  • SpecKit project detected (.specify/ directory exists)
  • Working with specification files in specs/[N]-feature/ directories
  • Using SpecKit commands (/speckit.*)
  • Discussing requirements or specifications

Combined Workflow Overview

SpecKit (What to Build)          Quality Toolkit (Build Safely)
───────────────────────          ──────────────────────────────
/speckit.constitution
        │
        ▼
/speckit.specify  ─────────────▶ /vt-c-wf-plan (validate + research)
        │
        ▼
/speckit.plan
        │
        ▼
/speckit.tasks
        │
        ▼
/speckit.implement ────────────▶ Skills auto-activate
        │                        • defense-in-depth
        │                        • multi-tenancy
        │                        • test-driven-development
        ▼
   Code complete ──────────────▶ /vt-c-wf-review (quality gate)
        │
        ▼
   Ready to ship ──────────────▶ /vt-c-finalize-check (finalization gate)

Integration Points

After /speckit.specify

When requirements are specified, recommend running /vt-c-wf-plan to: - Validate specifications against best practices - Research implementation patterns - Identify multi-tenancy considerations - Flag compliance requirements (GDPR, SOC2)

Prompt:

"Requirements look good. Run /vt-c-wf-plan to validate against best practices and research implementation patterns."

During /speckit.implement

While implementing tasks, these skills should be active: - defense-in-depth - Input validation at all layers - multi-tenancy - Tenant isolation in queries - test-driven-development - Tests alongside code

Prompt:

"As you implement, ensure tenant isolation in database queries and add input validation at API boundaries."

After Implementation

When code is complete, recommend: 1. /vt-c-wf-review - Quality gate (security, performance, complexity) 2. /vt-c-finalize-check - Finalization gate (dependencies, compliance)

Prompt:

"Implementation complete. Run /vt-c-wf-review for quality checks, then /vt-c-finalize-check before deploying."

SpecKit Project Detection

Detect SpecKit projects by looking for:

project/
├── .specify/
│   ├── memory/
│   │   └── constitution.md    # Project principles
│   ├── templates/             # Spec/plan/tasks templates
│   └── scripts/bash/          # Helper scripts
├── specs/
│   └── [N]-feature/
│       ├── spec.md            # Requirements (from specs via /vt-c-activate)
│       ├── plan.md            # Technical plan (from /speckit.plan)
│       ├── tasks.md           # Task breakdown (from /speckit.tasks)
│       ├── research.md        # Research findings
│       └── data-model.md      # Entity definitions
└── .claude/
    └── commands/              # SpecKit slash commands

Enhancing Specifications

When reviewing SpecKit specifications, ensure they include:

Multi-Tenancy Considerations

## Tenant Isolation Requirements

- [ ] All database queries include tenantId filter
- [ ] API endpoints validate tenant from JWT
- [ ] Error messages don't leak tenant information
- [ ] Caching keys include tenant scope

Security Requirements

## Security Considerations

- [ ] Input validation at API boundaries
- [ ] Authentication required for protected routes
- [ ] Authorization checks for data access
- [ ] No secrets in code or configuration

Compliance Requirements

## Compliance Checklist

- [ ] GDPR: Data export capability
- [ ] GDPR: Data deletion capability
- [ ] SOC2: Audit logging enabled
- [ ] SOC2: Access controls documented

Full Product Development (Unified Workflow)

# PRODUCT DESIGN PHASE
/vt-c-pd-2-prd                              # Create PRD
/vt-c-pd-3-prototype                        # Build prototype
/vt-c-pd-4-validate                         # Usability testing
/vt-c-pd-6-handoff                          # Transition to development
/vt-c-activate --from-prd                   # Generate specs from PRD

# DEVELOPMENT PHASE (per feature)
/vt-c-activate SPEC-001                     # Select next feature brief
/vt-c-2-plan                                # Orchestrates: specify → research → plan → tasks
/vt-c-3-build                               # Implement from tasks.md
/vt-c-4-review                              # Quality gate
/vt-c-complete                              # Mark done, advance to next

Standalone Feature (No PD Workflow)

For features without a full Product Design cycle:

# 1. Define project principles (once)
/speckit.constitution

# 2. Specify + plan + tasks
/vt-c-2-plan "Add user notification preferences"

# 3. Build and review
/vt-c-3-build
/vt-c-4-review
/vt-c-5-finalize

Quality Gates at Each Phase

Phase Quality Check Tool
Activate Feature brief selected /vt-c-activate sequences by dependency
Plan Spec formalized, tech approach sound /vt-c-2-plan orchestrates full pipeline
Build Code quality Skills + /vt-c-3-build
Review Quality gate /vt-c-4-review (security, performance, patterns)
Deploy Safe to release /vt-c-5-finalize

Troubleshooting

"SpecKit commands not found"

Ensure SpecKit is installed: 

uv tool install specify-cli --from git+https://github.com/github/spec-kit.git

Then initialize your project: 

specify init . --ai claude

"Skills not activating during implement"

Ensure the toolkit is installed: 

~/.claude/plugins/company-claude-toolkit/scripts/install.sh

"Specifications incomplete"

Run /vt-c-wf-plan after /speckit.specify to identify gaps: - Missing tenant isolation - Unclear error handling - No compliance considerations

Best Practices

  1. Use /vt-c-2-plan as the orchestrator - It chains specify → plan → tasks automatically
  2. Let skills guide implementation - They catch issues in real-time
  3. Run /vt-c-4-review before PR - Catches quality issues
  4. Run /vt-c-5-finalize before release - Ensures safe deployment
  5. Document decisions in constitution - Reduces future debates (.specify/memory/constitution.md)

SpecKit Resources