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 — 25 workflows spanning stage-based, methodology-based (AWS one-way/two-way door, Google, Stripe, Lean Startup, Design Thinking, JTBD, Shape Up, Continuous Discovery), Big Tech syntheses, V2MOM, and pbhq-lite — is embedded directly in this repo (pkg/workflows) and built into 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	mrd, prd, uxd, trd, tpd, spec

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-one-way-door  Amazon Working Backwards methodology for new product lines. ... [default]
  ...

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

All 25 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. MRD includes embedded Business Model Canvas.

Required specs:
  - mrd (source)
  - prd (source)
  - spec (output)
  - tpd (technical)
  - trd (technical)
  - uxd (source)

Custom templates:
  - bmc
  - ird
  - mrd
  - narrative-1p
  - opportunity-spec
  - plan
  - prd
  - roadmap
  - spec
  - tpd
  - trd
  - uxd

Custom rubrics:
  - bmc
  - ird
  - mrd
  - narrative-1p
  - opportunity-spec
  - prd
  - spec
  - tpd
  - trd
  - uxd

press, faq, and narrative-6p are not owned by enterprise — their canonical home is aws-one-way-door; families that use them source {from: aws-one-way-door}.

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/bmc.md
Created ./my-profile/templates/ird.md
Created ./my-profile/templates/mrd.md
Created ./my-profile/templates/narrative-1p.md
Created ./my-profile/templates/opportunity-spec.md
Created ./my-profile/templates/plan.md
Created ./my-profile/templates/prd.md
Created ./my-profile/templates/roadmap.md
Created ./my-profile/templates/spec.md
Created ./my-profile/templates/tpd.md
Created ./my-profile/templates/trd.md
Created ./my-profile/templates/uxd.md
Created ./my-profile/rubrics/bmc.rubric.yaml
Created ./my-profile/rubrics/ird.rubric.yaml
Created ./my-profile/rubrics/mrd.rubric.yaml
Created ./my-profile/rubrics/narrative-1p.rubric.yaml
Created ./my-profile/rubrics/opportunity-spec.rubric.yaml
Created ./my-profile/rubrics/prd.rubric.yaml
Created ./my-profile/rubrics/spec.rubric.yaml
Created ./my-profile/rubrics/tpd.rubric.yaml
Created ./my-profile/rubrics/trd.rubric.yaml
Created ./my-profile/rubrics/uxd.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

• Custom Profiles Guide - Complete guide to creating custom profiles
• init - Initialize projects with profiles