CLI Reference

Availability: fit-pathway, fit-map, and fit-basecamp are published to npm and can be installed standalone. fit-guide, fit-summit, fit-rc, fit-doc, and fit-universe are monorepo-only tools that require a full checkout of the monorepo.

fit-map

Data validation and index generation.

bunx fit-map validate                    # Validate all data (JSON Schema + referential integrity)
bunx fit-map validate --shacl            # Validate RDF/SHACL syntax
bunx fit-map validate --data=PATH        # Validate a specific data directory
bunx fit-map generate-index              # Generate _index.yaml files for browser loading
bunx fit-map people import <file>        # Import people from CSV/YAML
bunx fit-map people import <f> --data=P  # Import with custom data directory

Option	Description
`--shacl`	Include RDF/SHACL syntax checks
`--data=<path>`	Use a specific data directory

fit-pathway

Data Directory Resolution

By default, fit-pathway walks upward from the current working directory looking for a data/ folder, then appends /pathway. Framework data must be in ./data/pathway/ (not ./data/ directly).

Use --data to override, pointing to the pathway subdirectory directly:

bunx fit-pathway discipline --list --data=./data/pathway
bunx fit-pathway job software_engineering L3 --data=./custom-path/pathway

Entity Browsing

All entity commands support three output modes:

Mode	Pattern	Description
Summary	`bunx fit-pathway <command>`	Concise overview with stats
List	`bunx fit-pathway <cmd> --list`	IDs for piping
Detail	`bunx fit-pathway <cmd> <id>`	Full entity details

Entity commands: discipline, level, track, behaviour, driver, stage, skill, tool.

Global options (apply to all fit-pathway commands):

Option	Description
`--data=<path>`	Path to data directory
`--json`	Output as JSON
`--list`	Output IDs only (for piping)
`--version`	Show version number
`--help`	Show help message

bunx fit-pathway skill --list          # List all skill IDs
bunx fit-pathway skill <id>            # Show skill details
bunx fit-pathway skill <id> --agent    # Output as agent SKILL.md format
bunx fit-pathway tool --list           # List tools derived from skill toolReferences

Job Generation

bunx fit-pathway job                                       # Summary with stats
bunx fit-pathway job --track=<track>                       # Summary filtered by track
bunx fit-pathway job --list                                # Valid combinations
bunx fit-pathway job --list --track=<track>                # Combinations for a track
bunx fit-pathway job <discipline> <level>                  # Trackless job
bunx fit-pathway job <discipline> <level> --track=<track>  # With track
bunx fit-pathway job <discipline> <level> --checklist=code # With checklist
bunx fit-pathway job <discipline> <level> --skills         # Skill IDs only
bunx fit-pathway job <discipline> <level> --tools          # Tool names only

Arguments:

<discipline> -- Discipline ID (e.g. software_engineering)
<level> -- Level ID (e.g. L3)

Options:

Option	Description
`--track=<id>`	Track ID (e.g. `platform`)
`--list`	List valid discipline/level combinations
`--checklist=<stage>`	Include stage checklist
`--skills`	Output skill IDs only
`--tools`	Output tool names only

Agent Generation

bunx fit-pathway agent --list                                         # Valid combinations
bunx fit-pathway agent <discipline> --track=<track>                   # Preview
bunx fit-pathway agent <discipline> --track=<track> --output=./agents # Write files
bunx fit-pathway agent <discipline> --track=<track> --stage=plan      # Single stage
bunx fit-pathway agent <discipline> --track=<track> --skills          # Skill IDs only
bunx fit-pathway agent <discipline> --track=<track> --tools           # Tool names only

Arguments:

<discipline> -- Discipline ID

Options:

Option	Description
`--track=<id>`	Track ID
`--output=<dir>`	Write agent files to directory
`--stage=<stage>`	Generate for a single lifecycle stage
`--list`	List valid combinations
`--skills`	Output skill IDs only
`--tools`	Output tool names only

Interview, Progress, and Questions

bunx fit-pathway interview <discipline> <level>
bunx fit-pathway interview <d> <l> --track=<t> --type=mission

bunx fit-pathway progress <discipline> <level>
bunx fit-pathway progress <d> <l> --compare=<to_level>

bunx fit-pathway questions
bunx fit-pathway questions --level=practitioner
bunx fit-pathway questions --maturity=practicing
bunx fit-pathway questions --skill=<id>
bunx fit-pathway questions --behaviour=<id>
bunx fit-pathway questions --capability=<id>
bunx fit-pathway questions --stats
bunx fit-pathway questions --format=yaml

Interview options:

Option	Description
`--track=<id>`	Track ID
`--type=<type>`	Interview type (e.g. `mission`)

Progress options:

Option	Description
`--compare=<level>`	Compare with a target level

Questions options:

Option	Description
`--level=<level>`	Filter by proficiency level
`--maturity=<maturity>`	Filter by behaviour maturity
`--skill=<id>`	Filter by skill ID
`--behaviour=<id>`	Filter by behaviour ID
`--capability=<id>`	Filter by capability ID
`--stats`	Show question statistics
`--format=<format>`	Output format (e.g. `yaml`)

Build and Development

bunx fit-pathway init                          # Create ./data/ with example framework data
bunx fit-pathway dev                           # Run live development server
bunx fit-pathway dev --port=8080               # Dev server on custom port
bunx fit-pathway build --output=./public --url=https://example.com  # Static site
bunx fit-pathway update                        # Update local installation

Option	Description
`--port=<port>`	Dev server port (default: 3000)
`--output=<dir>`	Static site output directory
`--url=<url>`	Base URL for the built site

fit-basecamp

Personal operations center: calendar sync, meeting briefings, and background AI agents.

fit-basecamp                         # Wake due agents once and exit
fit-basecamp --daemon                # Run continuously (poll every 60s)
fit-basecamp --wake <agent>          # Wake a specific agent immediately
fit-basecamp --stop                  # Gracefully stop daemon and agents
fit-basecamp --status                # Show agent status and last decisions
fit-basecamp --validate              # Validate agent definitions exist
fit-basecamp --init <path>           # Initialize a new knowledge base
fit-basecamp --update [path]         # Update KB with latest templates

Option	Description
`--daemon`	Run continuously, polling every 60 seconds
`--wake <agent>`	Wake a specific agent by name
`--stop`	Graceful shutdown of daemon and agents
`--status`	Display agent status and last decisions
`--validate`	Check that agent definitions exist
`--init <path>`	Initialize a new knowledge base at path
`--update [path]`	Update existing KB with latest templates

fit-summit

Team capability analysis. Deterministic, no LLM calls.

fit-summit coverage <team>                                   # Capability coverage
fit-summit risks <team>                                      # Structural risks
fit-summit what-if <team> --add "{ discipline: se, level: L3, track: platform }" # Scenario

Command	Description
`coverage`	Show capability coverage for a team
`risks`	Identify structural risks in team composition
`what-if`	Model staffing scenarios with `--add`/`--remove`

Arguments:

<team> -- Team identifier

what-if options:

Option	Description
`--add`	Add a hypothetical team member (YAML object)
`--remove`	Remove a team member from the scenario

fit-universe

Synthetic data generation from a universe DSL file.

bunx fit-universe                     # Use cached prose (default)
bunx fit-universe --generate          # Generate prose via LLM
bunx fit-universe --no-prose          # Structural scaffolding only
bunx fit-universe --strict            # Fail on cache miss
bunx fit-universe --load              # Load raw docs to storage
bunx fit-universe --only=pathway      # Render only one content type
bunx fit-universe --dry-run           # Show what would be written
bunx fit-universe --story=path        # Custom story DSL file
bunx fit-universe --cache=path        # Custom prose cache file

Option	Description
`--generate`	Call LLM to produce new prose
`--no-prose`	Skip prose, structural output only
`--strict`	Fail if prose cache is missing keys
`--load`	Load generated docs into storage
`--only=<type>`	Render a single content type
`--dry-run`	Preview without writing files
`--story=<path>`	Path to custom story DSL file
`--cache=<path>`	Path to custom prose cache file

fit-doc

Documentation site builder.

bunx fit-doc build --src=website --out=dist    # Build static site
bunx fit-doc serve --src=website               # Development server
bunx fit-doc serve --src=website --port=8080   # Custom port
bunx fit-doc build --src=website --out=dist --base-url=https://example.com  # With base URL

Option	Description
`--src=<dir>`	Source directory
`--out=<dir>`	Output directory (build only)
`--base-url=<url>`	Base URL for absolute links
`--port=<port>`	Dev server port (default: 3000)
`--watch`, `-w`	Watch for changes (serve mode only)

Guides -- Task-oriented usage walkthroughs
Core Model -- Entity definitions and derivation
YAML Schema -- File format reference

CLI Reference

fit-map

fit-pathway

Data Directory Resolution

Entity Browsing

Job Generation

Agent Generation

Interview, Progress, and Questions

Build and Development

fit-basecamp

fit-summit

fit-universe

fit-doc

Related Documentation