Skip to content

profiles

Manage configuration profiles that bundle spec requirements, templates, and rubrics.

Synopsis

visionspec profiles <subcommand>

Description

Configuration profiles allow you to customize which specs are required and how they're evaluated. The default profile library — 24 workflows spanning stage-based, methodology-based (AWS, Google, Stripe, Lean Startup, Design Thinking, JTBD, Shape Up, Continuous Discovery), Big Tech syntheses, V2MOM, and pbhq-lite — is defined in specification-workflow-spec and embedded in the visionspec binary. The stage-based profiles:

Profile Description Required Specs
0-1 Minimal for idea validation hypothesis
startup Lightweight for pre-PMF prd
growth Metrics-driven for 1-N scaling prd, uxd, faq
enterprise Comprehensive for post-PMF prd, mrd, uxd, trd, press, faq

Subcommands

list

List all available profiles.

visionspec profiles list

Output (abbreviated):

Available profiles:

  0-1          Minimal configuration for 0-1 product development. Focus on hypothesis validation. [default]
  startup      Lightweight configuration for pre-PMF startups. Only PRD required. [default]
  growth       Metrics-driven configuration for 1-N scaling. [default]
  enterprise   Comprehensive configuration for post-PMF enterprises. Full specs with security and compliance. [default]
  aws-product  Amazon Working Backwards methodology for new product lines. ... [default]
  ...

Use with: visionspec init <project> --profile <name>

All 24 embedded workflows carry the [default] marker; custom profiles loaded from a directory appear without it.

show

Show detailed information about a profile.

visionspec profiles show <profile-name>

Example:

visionspec profiles show enterprise

Output:

Profile: enterprise
Description: Comprehensive configuration for post-PMF enterprises. Full specs with security and compliance.

Required specs:
  - prd (source)
  - mrd (source)
  - uxd (source)
  - press (gtm)
  - faq (gtm)
  - trd (technical)

Custom templates:
  - prd
  - mrd
  - uxd
  - trd
  - press
  - faq

Custom rubrics:
  - prd
  - mrd
  - uxd
  - trd
  - press
  - faq

export

Export a profile to a directory for customization.

visionspec profiles export <profile-name> <output-dir>

This creates a complete profile directory with:

  • profile.yaml - Configuration file, fully resolved (inheritance applied; includes methodology and synthesis sections)
  • templates/ - Template files (.md)
  • rubrics/ - Rubric files (.rubric.yaml)

Example:

visionspec profiles export enterprise ./my-profile

Output:

Created ./my-profile/profile.yaml
Created ./my-profile/templates/prd.md
Created ./my-profile/templates/mrd.md
Created ./my-profile/templates/uxd.md
Created ./my-profile/templates/trd.md
Created ./my-profile/templates/press.md
Created ./my-profile/templates/faq.md
Created ./my-profile/rubrics/prd.rubric.yaml
Created ./my-profile/rubrics/mrd.rubric.yaml
Created ./my-profile/rubrics/uxd.rubric.yaml
Created ./my-profile/rubrics/trd.rubric.yaml
Created ./my-profile/rubrics/press.rubric.yaml
Created ./my-profile/rubrics/faq.rubric.yaml

Profile exported to ./my-profile

To use this profile:
  visionspec init my-project --profile-dir ./my-profile

Using Profiles

With init command

# Use a built-in profile
visionspec init my-project --profile startup

# Use a custom profile directory
visionspec init my-project --profile-dir ./my-profile

Profile inheritance

Profiles can extend other profiles using the extends field:

# my-profile/profile.yaml
name: my-enterprise
description: "Custom enterprise profile with additional requirements"
extends: enterprise

spec_config:
  # Add a custom spec type
  security-review:
    required: true
    category: technical

See Also