add-stack-context

Run the stack context audit, which inventories direct dependencies from manifests and config files, then discovers and installs vendor-controlled skills or official context like codemods and llms.txt references for each technology.

It verifies candidate ownership against the technology vendor's official documentation or organization, not search rank or install counts. Community skills are only installed after explicit user approval and never substitute for missing official context.

The gap is recorded as unavailable from an official source, and the audit continues with the remaining stack items. A community candidate may be listed separately but is never treated as a substitute for official context.

Yes. The missing helper is treated as a fallback condition, and the audit searches the current Skills ecosystem through the Skills CLI or an equivalent source, then continues to non-skill vendor context like installers and codemods.

No. User-authored content and existing links between instruction files are preserved. It only adds or updates a bounded managed instruction, and vendor-managed blocks are updated solely through the vendor's documented method.

No. A vendor llms.txt is treated as a live remote source. The audit adds an instruction telling later agents to retrieve the current document when relevant work begins and reconcile it with the installed version.