Weeks

Docs

Coverage

See which product interactions are backed by API endpoints and CLI commands.

Purpose

Weeks should keep one shared action model across every surface:

interaction -> API endpoint -> CLI command

Coverage starts with a product interaction. The API reference explains the endpoint contract, and the CLI reference explains how the same action can be run from a shell.

Coverage model

Each row answers three questions:

InteractionThe matching product workflow in the gallery.
APIThe OpenAPI path and operation that owns the action.
CLIThe `weeks` command that calls that endpoint and returns the standard envelope.

Coverage matrix

Workflow Interaction API reference CLI coverage
Create a space create-space Spaces create endpoint Planned
Create a plan create-plan Staffing plans create endpoint Planned
Add a slot add-slot-factory-mode Staffing slots create endpoint Planned
Assign a person to a slot assign-person-to-slot Assigned people create endpoint Planned
Authenticate the CLI cli-auth-login-device OAuth device flow Covered `weeks auth login`
List accessible teams cli-list-teams Teams collection endpoint Covered `weeks teams list`
List spaces in a team cli-list-spaces Spaces collection endpoint Covered `weeks spaces list`
View a space overview cli-view-space Space show endpoint with `overview` Covered `weeks spaces view --include overview`
List and view people in a space Planned cli-list-people / cli-view-person Staffing people collection and show endpoints Covered `weeks people list` / `view`
List and view planning contexts Planned cli-list-planning-contexts / cli-view-planning-context Planning contexts collection and show endpoints Covered `weeks planning-contexts list` / `view`
List plans in a space cli-list-plans Staffing plans collection endpoint Covered `weeks plans list`
View a plan snapshot cli-view-plan Staffing plan show endpoint with `snapshot` Covered `weeks plans view --include snapshot`

The write workflows remain planned until their commands ship in the CLI. Their gallery interactions and API docs already exist, so each CLI command can be added against a known workflow instead of a vague feature name.