ottonomous

agent
Guvenlik Denetimi
Gecti
Health Gecti
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 13 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested

Bu listing icin henuz AI raporu yok.

SUMMARY

Set of Claude Code skills for product development

README.md

Ottonomous 🚌💨

Claude Code skills for every stage of product development: spec writing, task prioritization, testing, code review, and documentation.

image 1 (1)

Add marketplace

/plugin marketplace add brsbl/ottonomous

Install plugin

/plugin install ottonomous@brsbl-ottonomous

Dependencies

Philosophy

Subagents for Context Isolation

Use subagents to isolate concerns and prevent context pollution:

  • Context isolation: Each subagent gets only what it needs, nothing more. Orchestrator agent delegates to and manages subagent
  • Specialization: Different expertise per agent (frontend-developer vs backend-architect, senior-code-reviewer vs architect-reviewer, test-writer, etc)

Skill/Subagent Separation

Skills and subagents have distinct responsibilities:

  • Skills define what to hand off (file list, diff command, scope, context) and are instructions for the Orchestrator agent
  • Subagents define how to process what's handed off (criteria, detection rules, output format)

This keeps subagents self-contained and reusable while skills orchestrate the workflow.

Swarm Orchestration

Skills coordinate multiple subagents working in parallel using run_in_background: true:

Coordination patterns:

  • Fan-out/Fan-in — Spawn N agents, wait for all, synthesize results. Used by /review.
  • Batches — Complete batch N before starting N+1 (for dependent work). Used by /review fix.
  • Pipeline — Sequential handoff between specialists. Used by /otto.

Scaling: 1-4 items = 1 agent, 5-10 = 2-3 agents, 11+ = 3-5 agents. Group by directory or component type.

Iterative Review for Verification

Every phase has explicit verification:

  • Planning: spec → spec review → user approval
  • Implementation: code → code review → fix → commit
  • Verification criteria: Each step defines "Done when..."
  • Prioritized findings: P0-P2 across all skills (P0 = critical, P1 = important, P2 = minor)

Recommended Workflow

/spec                     # define requirements via interview
  │
  ▼
/task                     # break spec into sessions & tasks
  │
  ▼
┌───────────────────┐
│                   │
▼                   │
/next batch         │     # implement sessions of tasks in parallel then stage results
│                   │
▼                   │
/test write staged  │     # generate tests, then lint/typecheck/run all
│                   │
▼                   │
/review staged      │     # multi-agent code review
│                   │
▼                   │
/review fix staged  │     # fix P0-P2 issues
│                   │
▼                   │
commit ─────────────┘     # loop if more sessions/tasks
  │
  ▼
/summary                  # generate semantic overview of changes, opened in browser
  │
  ▼
 PR

Use /clear between steps to reset context.

Skills

Specification & Planning

Skill Description
/spec [idea] Researches best practices, interviews you to define requirements and design. technical-product-manager validates completeness, consistency, feasibility, and technical correctness.
/spec revise {spec} Saves a comprehensive spec and goes straight to review with codebase exploration, skipping the interview.
/spec list Lists all specs with id, name, status, and created date.
/task <spec-id> Creates atomic tasks grouped into agent sessions. principal-engineer reviews work breakdown, dependencies, and completeness.
/task list Lists all tasks and their spec, sessions, status etc.

Implementation

Skill Description
/next Returns next task id.
/next session Returns next session id.
/next <id> Launches subagent to implement task or session. Plans first, then implements.
/next batch Implements all highest-priority unblocked sessions in parallel.

Testing

Skill Description
/test run Lint, type check, run tests.
/test write test-writer generates tests for pure functions with edge cases, then runs pipeline.
/test browser Visual verification with browser automation.
/test all Run + browser combined.

Scope: staged, branch (default)

Code Review

Skill Description
/review Multi-agent code review. architect-reviewer checks system structure and boundaries; senior-code-reviewer checks correctness, security, performance; false-positive-validator filters out invalid findings.
/review fix Implements all fixes from plan in parallel batches.
/review fix P0 Implements only P0 (critical) fixes.
/review fix P0-P1 Implements P0 and P1 fixes.

Scope: staged, branch (default)

Documentation

Skill Description
/summary Synthesizes code docs into semantic HTML summary explaining what changed and why. Primarily a resource to complement or replace code review.

Scope: staged, branch (default)

Automation

Skill Description
/otto <idea> Autonomous spec → tasks → [next/test/review] per session → summary. Best for greenfield explorations, prototyping, scoped migrations, and simple applications. Not recommended for building complex apps end-to-end.
/reset [targets] Resets workflow data. Targets: tasks, specs, sessions, all (default). Docs are preserved.

Utilities

For browser or UI automation, use /test browser, /test electron, or the host environment's available browser automation tool directly.

Architecture

.otto/                       # Workflow artifacts (git-ignored)
├── specs/                   # Specification documents (.md)
├── tasks/                   # Sessions and tasks (.json)
├── reviews/                 # Review fix plans (.json)
├── summaries/               # Generated HTML summaries
└── otto/
    └── sessions/            # Otto session state (state.json)

skills/                      # Skill implementations (SKILL.md + support files)
├── spec/
│   └── agents/
│       └── technical-product-manager.md  # Spec validation (completeness, feasibility)
├── task/
│   └── agents/
│       └── principal-engineer.md         # Task decomposition review
├── next/
│   └── agents/                    # Implementation agents
│       ├── frontend-developer.md
│       └── backend-architect.md
├── review/
│   └── agents/                    # Code review agents
│       ├── architect-reviewer.md         # Architectural issues
│       ├── senior-code-reviewer.md       # Implementation issues
│       └── false-positive-validator.md   # Validates and filters review findings
├── test/
│   └── agents/
│       └── test-writer.md         # Test generation
├── summary/
│   └── scripts/md-to-html.js
└── ...

Feedback

Found a bug or have a feature request? Open an issue.

License

MIT

Yorumlar (0)

Sonuc bulunamadi