Command surface

Platform spec node

Command surface

Back to CLI ◎ Open in platform map

Spec standingStandard

Owner

Piotr Mikstacki pmikstacki@cybernomad.it

Submitter

Piotr Mikstacki pmikstacki@cybernomad.it

Current document

ADRs

No architecture decision records under adr/ for this feature yet. Standard features must publish at least one ADR or keep a ## Decisions summary on the hub.

Articles

• Command surface Normative command taxonomy for the Beskid CLI and behavior expectations per command family. article Standard Reviewed Thu Apr 30

History

0 revisions (git unavailable at build; counts may be empty)

Open full history on GitHub

No commits recorded for this path.

Completeness

OKarea · 2 SpecSection(s) · 0 H2 heading(s)

Section id	Required	Found
scope	yes	yes
features	yes	yes

Full tree: run pnpm verify:platform-spec-layout (writes src/generated/platform-spec-layout-report.json).

Related spec docs

• Area
  CLI

  Parent area

• Feature
  beskid new command

  Template scaffolding entrypoint

Normative platform contract

1. The CLI shall expose stable command families for run, build, test, analyze, parse, format, clif, doc, corelib, lock, fetch, tree, update, and new (project, workspace, and item templates).
2. Commands that invoke compilation shall route through shared frontend and analysis services to preserve diagnostic parity.
3. Manifest and dependency commands shall operate on the same project graph policy as compile flows.
4. CLI documentation generation (doc) shall remain aligned with corelib and platform-spec evolution.

Implementation anchors

• compiler/crates/beskid_cli/src/commands
• compiler/crates/beskid_cli/src/frontend.rs
• compiler/crates/beskid_cli/src/cli.rs