AynOps Roadmap – Next Major Update

[gaoharimran29-glitch]

Hi everyone!

First of all, thank you to everyone who has been contributing to AynOps. The project has been evolving quickly, and I've been thinking about the direction for the next major update.

The current plan is to focus on three phases before introducing any major new functionality.

Phase 1 – Tool Refinements

The immediate priority is to refine and stabilize the existing reconnaissance tools. This includes:

• Improving output consistency and metadata.
• Enhancing reconnaissance capabilities where appropriate.
• Improving error handling and maintainability.
• Expanding and improving test coverage.

The goal is to ensure that each individual tool provides reliable and useful results before moving on to larger architectural changes.

Phase 2 – Full Recon Improvements

Once the tools are in a good state, I plan to improve the full_recon workflow.

The idea is to make full_recon more than just a collection of tool outputs by:

• Better orchestrating the available tools.
• Aggregating and presenting reconnaissance findings more effectively.
• Providing more meaningful and actionable results.

Phase 3 – Native MCP Client

The final phase for the next major update is building a native MCP client within the AynOps repository.

The motivation behind this is to provide a more consistent user experience and reduce dependence on the capabilities and behavior of third-party MCP clients. Having our own client will also give us more flexibility in how reconnaissance workflows are executed and presented.

Contributor Guidance

If you're interested in contributing, tool refinements are currently the highest priority. Future issues and PRs will generally follow the roadmap outlined above.

This roadmap may evolve as the project grows, and I'm always open to feedback and suggestions from contributors.

Thanks again for being a part of AynOps!

[gaoharimran29-glitch]

Update

To clarify the current contribution priorities:

The focus right now is on refining and improving the existing toolset ( except full reconn tool ) rather than introducing new reconnaissance tools.

Areas that would benefit from contributions include:

• Improving detection accuracy and reconnaissance capabilities.
• Standardizing output schemas and metadata.
• Improving error handling and edge-case handling.
• Expanding test coverage.
• Improving documentation and maintainability.

I will be reviewing each tool individually and opening dedicated refinement issues so contributors have clear areas to work on.

For now, if you're interested in contributing, please prioritize improvements to existing tools over adding new ones and open an issue if you find any improvement in existing tools

[gaoharimran29-glitch]

@SemTiOne Hii ,

Since we're currently in the tool refinement phase, it would be great if you could help review some of the existing tools.

The goal is to evaluate the current tools and identify any opportunities for improvement in areas such as:

• Output quality and consistency
• Detection accuracy
• Missing metadata
• Error handling and edge cases
• Test coverage
• Documentation

If you find something that genuinely needs improvement, feel free to open a detailed issue describing the problem and any proposed enhancements.

If a tool looks good and doesn't need changes, that's completely fine as well. The objective is to understand the current state of the toolset and identify where refinement is actually needed before we move on to larger features.

[gaoharimran29-glitch]

Documentation Initiative for AynOps Tools

As part of our ongoing effort in Phase 1 to make AynOps tool more stable and easier to use, we're starting a documentation initiative for all reconn tools.

Our recent focus has been on improving the stability and reliability of the existing tools. Alongside that work, we'll now be adding dedicated documentation for every tool to make the project more accessible for both users and contributors.

The plan is to:

• Create a dedicated documentation page for each MCP tool.
• Include an overview, parameters, examples, response format, notes, and limitations where applicable.
• Add a documentation index under docs/tools/.
• Update the main README so every tool listed in the tool tables links directly to its documentation page.

If you'd like to contribute, check issue #143 . Partial contributions are absolutely welcome. Follow the issue description and contributing.md clearly

While documenting a tool, if you discover any bugs, inconsistencies, or undocumented behavior, please open a separate issue so we can track and address it independently.

Thanks to everyone who has been helping improve AynOps—we appreciate every contribution, whether it's code, documentation, bug reports, or reviews!

[gaoharimran29-glitch]

Documentation Initiative for AynOps Tools

As part of our ongoing effort in Phase 1 to make AynOps more stable and easier to use, we're starting a documentation initiative for all reconn tools.

Our recent focus has been on improving the stability and reliability of the existing tools. Alongside that work, we'll now be adding dedicated documentation for every tool to make the project more accessible for both users and contributors.

The plan is to:

• Create a dedicated documentation page for each MCP tool.
• Include an overview, parameters, examples, response format, notes, and limitations where applicable.
• Add a documentation index under docs/tools/.
• Update the main README so every tool listed in the tool tables links directly to its documentation page.

If you'd like to contribute, check issue #143 . Partial contributions are absolutely welcome. Follow the issue description and contributing.md clearly

While documenting a tool, if you discover any bugs, inconsistencies, or undocumented behavior, please open a separate issue so we can track and address it independently.

Thanks to everyone who has been helping improve AynOps—we appreciate every contribution, whether it's code, documentation, bug reports, or reviews!