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.