/vt-c-specify-and-validate

Combined SpecKit specification with toolkit validation

Plugin: core-standards
Usage: /vt-c-specify-and-validate <feature description>

---

Specify and Validate Command

Combines SpecKit's /speckit.specify with our toolkit's /vt-c-wf-plan for a complete specification + validation workflow.

Usage

/vt-c-specify-and-validate "Add user notification preferences API"

What This Command Does

1. Runs /speckit.specify to create detailed requirements
2. Automatically runs /vt-c-wf-plan to validate and enhance the spec
3. Outputs combined report with requirements + research + recommendations

Workflow

/vt-c-specify-and-validate "feature description"
                │
                ▼
    ┌─────────────────────────┐
    │   /speckit.specify      │
    │   Creates spec.md with: │
    │   • User stories        │
    │   • Acceptance criteria │
    │   • Edge cases          │
    └─────────────────────────┘
                │
                ▼
    ┌─────────────────────────┐
    │   /vt-c-wf-plan         │
    │   Validates spec with:  │
    │   • Best practices      │
    │   • Multi-tenancy check │
    │   • Security review     │
    │   • Compliance check    │
    └─────────────────────────┘
                │
                ▼
    Combined Specification Report

Output Format

## Feature Specification: [Feature Name]

### Requirements (from SpecKit)
[SpecKit-generated requirements]

### Validation (from Toolkit)

#### Best Practices Review
- [Patterns researched]
- [Recommendations]

#### Multi-Tenancy Considerations
- [Tenant isolation requirements]
- [Data access patterns]

#### Security Review
- [Authentication requirements]
- [Authorization patterns]
- [Input validation needs]

#### Compliance Check
- [GDPR requirements]
- [SOC2 requirements]

### Recommended Next Steps
1. Run `/speckit.plan` for technical planning
2. Run `/speckit.tasks` for task breakdown
3. Begin implementation with `/speckit.implement`

When to Use

• Starting any new feature
• When you want both specification AND validation
• For features touching user data (compliance review)
• For features with multi-tenant implications

Benefits Over Separate Commands

Separate	Combined
/speckit.specify then remember to /vt-c-wf-plan	Single command does both
Manual gap identification	Automatic validation
Easy to skip validation	Validation built-in

Example

# Combined approach
/vt-c-specify-and-validate "Add user preference settings with email notification controls"

# Equivalent to (but easier than):
# /speckit.specify "Add user preference settings with email notification controls"
# /vt-c-wf-plan  # Remember to run this!

Next Steps After This Command

1. Review the combined output - Check for any gaps or concerns
2. Run /speckit.plan - Technical planning for implementation
3. Run /speckit.tasks - Break into implementable tasks
4. Run /speckit.implement - Build with quality skills active
5. Run /vt-c-wf-review - Quality gate
6. Run /vt-c-finalize-check - Finalization gate

Requirements

• SpecKit CLI installed (uv tool install specify-cli)
• SpecKit initialized in project (specify init . --ai claude)
• Toolkit installed (./scripts/install.sh)