OttoNet for .NET

Ship .NET tasks to production-ready code.

OttoNet is a set of AI skills for .NET teams. It safely turns raw requirements from your Business Analysts and Team Leaders into production-ready code.

bash
# Quick Start
npx skills add quocbahuynh/OttoNet-Skills \
  --skill '*'
Setup

How to Install

Install directly from GitHub. You don't need npm packages or extra dependencies in your .NET project.

Local Install

Install all skills directly into your current .NET workspace.

npx skills add quocbahuynh/OttoNet-Skills \   --skill '*'

Global Install

Install all skills at once for your AI agent with a single command.

npx skills add quocbahuynh/OttoNet-Skills \   --skill '*' \   --agent claude-code \   --global

Start the Agent

Use this prompt to start the orchestrator safely.

Use dotnet-company-task-orchestrator for this GitLab task, but stop at every required developer-controlled gate.
CODEX
CLAUDE CODE
CURSOR
CLINE
GEMINI CLI
GITHUB COPILOT
KIRO CLI
OPENCODE
OPENHANDS
ROO CODE
WINDSURF
CODEX
CLAUDE CODE
CURSOR
CLINE
GEMINI CLI
GITHUB COPILOT
KIRO CLI
OPENCODE
OPENHANDS
ROO CODE
WINDSURF
How It Works

Safe & Clear Workflow

OttoNet never acts without your permission. It won't clone, commit, or push code on its own. You are always in control.

01 // PREPARATION

OttoNet starts by deeply understanding your project conventions, existing architecture, and team patterns before writing a single line of code.

02 // CLARIFICATION

Ambiguous requirements are caught early. The orchestrator explicitly stops and asks the BA or Lead if the task lacks necessary detail.

01

Knowledge Acquisition

Inspect workspace [SAFE]
Read project documentation
Explore .NET repository
Learn team patterns
02

Task Analysis

Analyze task
Investigate task context
Resolve requirement gaps
? Blocking questions detected
YES ➔ Ask BA or Team Leader (Loop to Analyze task)
NO ➔ Proceed to Planning
03

Execution & Review

Create HTML implementation plan
Developer approves plan?
NO ➔ Create HTML implementation plan (Loop)
YES ➔ Proceed to Execution
Execute ONE requested step
Review completed step
Developer commits?
YES ➔ More steps? (Loop to Execute ONE step)
01. PREPARE

Reads your code and learns your team's style.

PHASE 1: INSPECTION
[INFO] Checking workspace...
[WARN] Reading missing docs from code...
PHASE 2: EXECUTION
[SUCCESS] Ready. Starting work.
[DECISION] Ask developer before editing Program.cs
PHASE 3: VERIFICATION
[SUCCESS] Code review passed.
02. EXECUTE

Follows the plan strictly. Makes small, safe changes.

03. REVIEW

Checks the final code before you push.

Our Rule

Built for Safety

OttoNet works safely inside your .NET projects using strict rules to protect your code.

ottonet/safety_guard.json
"rules": [
  "Developer must approve architectural changes",
  "Always create a small-step plan first",
  "Do not execute unknown shell commands",
  "Stop if tests fail"
]
HOW_IT_RUNS

SPEED_LEVELS

Choose how deep the AI searches based on the task size.

FAST STANDARD STRICT
STRICT_RULES

NO_AUTO_PUSH

No automatic commits or pushes. You always review and approve the code.

Features

Agent Skills

Small, powerful skills you can use one by one or combine together.