Requirements Specifications

The chatbot conducts a briefing session with you, gathering questions and ideas until complete. It then generates comprehensive product and technical specifications.

(Example: A project I initiated to explore WebRTC.)

Product requirements:

Technical requirements:

Specification Refinement

You fill in details, clarify the specification, and resolve any TODOs flagged by the chatbot during the interview.

Codebase Map and Project Files

You'll occasionally need to review the code, so it's best to know in advance where to look and how everything is organized. This prevents the AI from making decisions—allowing it to focus on writing higher-quality code with greater attention to the task.

The image displays a file map generated by Nautex AI, with files linked to specific requirements and sections.

Agent Tasks

With the code location clarified, tasks are planned: Coding, Testing, and Review.

Reviews are scheduled early to demonstrate progress and verify alignment with goals.

The plan is structured in small, self-contained layers, building your project incrementally like floors in a skyscraper.

Integration

Configure the MCP server for your coding agent: connect to the Nautex cloud platform, select the project, and choose the implementation plan. The setup command writes all configuration to your project root.

Coding with Coding Agents

In agent mode, instruct: "pull nautex rules, and proceed with the next scope."

At this stage, your specifications are synchronized in the .nautex directory and accessible to the Coding Agent. The MCP server continuously monitors their relevance.

That's it. You then review and accept substantial code segments that fully align with your expectations and requirements.

On macOS and Linux:

curl -LsSf https://astral.sh/uv/install.sh | sh

On Windows:

powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"

Check the latest instructions from the UV repo for details and updates.

• MCP: registered via claude mcp add nautex -s local -- uvx nautex mcp
• Rules: managed section added to CLAUDE.md
• Verify: run claude mcp list and check for nautex: uvx nautex mcp

• MCP config: .cursor/mcp.json
• Rules: .cursor/rules/nautex_workflow.mdc

Note: After setup, Cursor may ask via popup whether to enable the new MCP — answer yes. In any case, go to File -> Preferences -> Cursor Settings -> Tools & Integrations and make sure the Nautex MCP toggle is enabled (green).

• MCP config: .codex/config.toml (project-local, backup created as config.toml.bak before first write)
• Rules: managed section added to AGENTS.md
• Verify: use the /mcp command inside Codex to confirm nautex is listed

• MCP config: opencode.json (project root, preserves unrelated fields, backup as opencode.json.bak if unparsable)
• Rules: managed section added to AGENTS.md
• Verify: invoke the Nautex MCP tool from OpenCode and run status

• MCP config: .gemini/settings.json
• Rules: managed section added to GEMINI.md