gov-capability-gap-detection

To perform a capability gap assessment, provide brief project context to the system. It will analyze the catalog, identify missing capabilities blocking workflows, and produce a structured proposal with recommended local or external package options and an implementation plan.

Choose between local and external package integration based on policy, maintenance, and security criteria. The assessment proposes either strategy with rationale and trade-offs, ensuring the selected package cleanly matches project needs while adhering to governance standards.

A capability gap proposal is a structured document outlining missing catalog capabilities. It includes recommended local or external package options, rationale for the decision, trade-offs, and an implementation plan to extend the catalog and prevent future gaps.

To stop repeated improvisation, use capability gap detection when no existing local package cleanly matches your project need. It updates the catalog with a durable extension recommendation, establishing a permanent package for recurring workflows.

Yes, you can assess external package trade-offs before integration. The capability gap analysis evaluates policy, maintenance, and security criteria to determine if an external package is suitable, providing a structured rationale for or against its adoption.