Skip to content

v0.6.0 Release Notes

Release Date: 2026-06-01

Overview

VisionSpec v0.6.0 adds AI workflow orchestration with the new rules system, AWS AI-DLC Workflows export target, and Test Plan Document (TPD) spec type. This release enables tighter integration with AI coding assistants (Claude Code, Kiro, Cursor) through methodology-aware workflow rules.

Highlights

  • Test Plan Document (TPD) spec type for comprehensive test planning
  • AWS AI-DLC Workflows export target for AI Development Lifecycle integration
  • Workflow rules for AI assistant orchestration (Claude Code, Kiro, Cursor)
  • Framework selection with flows for all 6 methodologies

New Features

Test Plan Document (TPD)

A new spec type for comprehensive test planning, synthesized from PRD + TRD + UXD:

# Synthesize TPD from source specs
visionspec synthesize tpd -p myproject

# With evaluation
visionspec synthesize tpd -p myproject --eval

TPD Template Sections:

  1. Test Objectives and Scope
  2. Test Strategy
  3. Entry and Exit Criteria
  4. Test Environment
  5. Test Data Requirements
  6. Test Cases by Category (Unit, Integration, E2E, Performance, Security, Accessibility)
  7. Test Automation Strategy
  8. CI/CD Integration
  9. Risk-Based Testing
  10. Regression Test Suite
  11. Test Metrics and Reporting
  12. Schedule and Resources
  13. Defect Management
  14. Sign-off Criteria

AWS AI-DLC Workflows Export Target

Export specs to AWS AI-DLC (AI Development Lifecycle) format for integration with AI agent execution workflows:

# Export to AI-DLC format
visionspec export aidlc -p myproject

Generated Files:

File Description
vision-document.md Problem/opportunity, vision statement, goals from MRD + Press
technical-environment.md Existing systems, infrastructure from TRD + IRD + context
imported-requirements.md Requirements derived from spec.md with AI-DLC integration notes

Workflow Rules for AI Assistants

New .visionspec-rules/ directory with methodology-aware workflow guidance for AI assistants:

# Export workflow rules to your project
visionspec rules export

# Export to custom directory
visionspec rules export ./my-rules

# List available rules
visionspec rules list

Rules Structure:

.visionspec-rules/
├── core-workflow.md           # Main orchestration workflow
├── phases/
│   ├── 01-discovery.md        # MRD authoring phase
│   ├── 02-vision.md           # Press + FAQ phase
│   ├── 03-experience.md       # PRD + UXD phase
│   ├── 04-technical.md        # TRD + TPD + IRD phase
│   └── 05-reconciliation.md   # spec.md generation
├── gates/
│   ├── eval-gate.md           # Evaluation approval gate
│   └── approval-gate.md       # Human approval gate
└── frameworks/
    ├── lean-startup/          # Build-Measure-Learn phases
    ├── design-thinking/       # Stanford d.school phases
    ├── jtbd/                   # Jobs to be Done phases
    ├── google/                 # Design Doc + RFC phases
    └── stripe/                 # API-first phases

Framework Selection

The workflow rules support runtime methodology selection with 6 frameworks:

  1. AWS Working Backwards (default) - PR/FAQ → PRD → Technical
  2. Lean Startup - Hypothesis → Experiment → Pivot/Persevere
  3. Design Thinking - Empathize → Define → Ideate → Prototype → Test
  4. Jobs to be Done - Job Statement → Outcome → Solution
  5. Google - OKR → Design Doc → RFC → Experiment
  6. Stripe - API Contract → DX Spec → Implementation

Using Workflow Rules

With Claude Code

  1. Export rules to your project:

    visionspec rules export
    

  2. Add to .claude/settings.yaml:

    project_memory:
      - path: .visionspec-rules/core-workflow.md
        type: workflow
    

  3. Claude Code will recognize spec authoring intents and follow the methodology-aware workflow.

With AWS Kiro

  1. Export rules to your project
  2. Reference in Kiro steering files
  3. Kiro will use the rules for spec-related tasks

CLI Commands

Rules Commands

Command Description
rules list List available workflow rules
rules export [dir] Export rules to directory (default: .visionspec-rules)

Updated Synthesis Flow

The Working Backwards flow now includes TPD:

MRD (human-authored)
Press (synthesized from MRD)
FAQ (synthesized from MRD + Press)
PRD (synthesized from MRD + Press + FAQ)
UXD (human-authored)
TRD (synthesized from MRD + PRD + UXD)
TPD (synthesized from PRD + TRD + UXD)  ← NEW
IRD (synthesized from TRD)

Installation

go install github.com/ProductBuildersHQ/visionspec/cmd/visionspec@v0.6.0

Migration Guide

From v0.5.0

No breaking changes. New features are additive:

  1. TPD support: Available immediately via synthesize tpd
  2. AIDLC export: New target available via export aidlc
  3. Rules: Export with rules export when needed

Adopting Workflow Rules

To adopt workflow rules for AI assistant integration:

# Export rules to project
visionspec rules export

# Add to .gitignore if you want to customize locally
# Or commit to share with team

# Reference in AI assistant configuration
# Claude Code: .claude/settings.yaml
# Kiro: steering files

What's Next

See ROADMAP.md for v0.7.0 planned features:

  • Bidirectional status sync with execution systems
  • Spec drift detection
  • Executable test generation from TPD
  • GitHub/Jira issue export
  • MCP execution tracking

Full Changelog

See CHANGELOG.md for the complete list of changes.