Skip to content
ContractSpec
Start here

Area guide · 30 packages · Find the owner of a command

CLI, authoring and agent tooling

Navigate the command host, source analysis, documentation generators and native agent-pack delivery used to work on ContractSpec projects.

What are you trying to do?

  • Which package owns a CLI command?
  • How are optional command packs discovered?
  • Where do docs, skills and editor integrations get their context?

Why start with these packages

Suggested entry point

@lssm-tech/lib.cli-runtime

Use deterministic command-pack discovery, host ports and canonical workspace analysis/rendering leaves.

Read package manual →

Suggested entry point

@lssm-tech/app.cli-contractspec

Inspect the actual CLI application that composes commands for users.

Read package manual →

Suggested entry point

@lssm-tech/agentpacks

Explore pack loading, target-specific configuration, skills and plugin export.

Read package manual →

Suggested entry point

@lssm-tech/tool.docs-generator

Inspect the Markdown/registry-to-reference-index generation stage.

Read package manual →

Practical steps

Step 01

Trace one CLI action

Open the application entry and its command-pack declaration, then locate the owning implementation. Check whether the action reads, writes generated artifacts or requests a governed mutation before putting it into an automated workflow.

Step 02

Follow a generated document

Identify the authored spec/DocBlock or README, the producer, its output path and the loader that consumes it. Record which stage is stale and which dependencies should invalidate it.

Step 03

Prepare a coding-agent context path

Choose the installed host target and a focused skill. Link its required package/version references and example sources; keep retrieved evidence separate from trusted instructions and inspect the generated diff before applying configuration changes.

Find the command’s owner

CliRuntime supplies host construction and command-pack discovery. The documented discovery scope is the consumer’s direct dependencies and optionalDependencies whose package metadata declares a command pack. Include/exclude configuration selects packs, exclusion wins, and package-name ordering is deterministic. Selected packs are loaded before registration; conflicts are rejected before a pack changes the Commander program. Use this model to locate an optional AI, builder, design or examples command rather than assuming every command lives in the main CLI application.

Distinguish the generation stages

Workspace analysis owns source scanning, static diagnostics, semantic diff and Markdown/DocBlock rendering. The docs-generator tool is a separate stage that combines existing generated Markdown with the seeded registry to make a reference index. README-to-LLMS generation is another projection in web-landing. When documentation looks inconsistent, trace the particular producer and its inputs instead of rerunning an unrelated build. Preserve source paths and versions so diagnostics can lead an editor or agent to the real owner.

Choose the coding-tool target explicitly

Agentpacks merges configuration into host-specific rules, hooks, skills and other outputs for supported coding tools. Skills can include references and scripts; they should stay focused on a task and fetch version-appropriate context. The documented generate --diff path uses a non-writing overlay and reports drift. Successful writing generation has an additional RTK refresh behavior, so select the intended mode deliberately. Editor bridges and native plugin exports remain separate delivery surfaces whose supported features and versions need inspection.

Follow a practical path.

Trace one CLI action

Open the application entry and its command-pack declaration, then locate the owning implementation. Check whether the action reads, writes generated artifacts or requests a governed mutation before putting it into an automated workflow.

Follow a generated document

Identify the authored spec/DocBlock or README, the producer, its output path and the loader that consumes it. Record which stage is stale and which dependencies should invalidate it.

Prepare a coding-agent context path

Choose the installed host target and a focused skill. Link its required package/version references and example sources; keep retrieved evidence separate from trusted instructions and inspect the generated diff before applying configuration changes.

Packages in this area (30)

30 of 30 shown

Curated but no longer in the workspace: app.cursor-marketplace, contractspec, jetbrains-contractspec-bridge, repo-scripts, spec-driven-development, vscode-contractspec