architecture-researcher-skill

To research enterprise capabilities, you provide your initiative context to the agent, which queries configured sources like Confluence and the Application Registry to surface owners, documentation, and roadmaps. This process avoids redundant work by mapping existing capabilities and contacts.

The best way to discover existing application capabilities is running a deep-dive query across your API Marketplace, Application Registry, and Confluence. This surfaces capability descriptions, roadmaps, gaps, and design authorities to shape your architecture approach.

You find capability owners and documentation by initiating a research query with your initiative context. The agent searches configured Confluence spaces and the Application Registry to link contacts, design authorities, and relevant docs to the discovered enterprise capabilities.

Yes, you can use this research process to identify roadmap gaps and deprecations. It surfaces plans, owners, and potential deprecations by scanning configured sources and the web, ensuring your architecture decisions account for future capability changes.

No, this enterprise capability research tool does not require external dependencies to function. However, you must configure access to your internal sources like Confluence, the API Marketplace, and the Application Registry before starting the research process.

You should avoid using automated research when your internal sources like Confluence or the Application Registry are not configured or accessible. The research relies on these defined sources to map contacts, gather contextual intelligence, and surface accurate capability documentation.