omni-sw-marketplace

omni-sw

A Claude Code plugin that implements a multi-agent SDLC workflow. Five role-based agents collaborate across seven sequential phases to take a project from business objective to delivered, documented software.

Installation

Load the plugin when starting a Claude Code session from your project directory:

claude --plugin-dir /path/to/omni-sw

All skills become available namespaced as /omni-sw:<skill>.

How it works

Each agent is a skill invoked with a phase argument. You drive the workflow by calling agents in order — each reads the artifacts produced by the previous phase and writes the next one.

/omni-sw:pm plan  →  /omni-sw:po plan  →  /omni-sw:tl design
→  /omni-sw:pm validate  →  /omni-sw:tl validate
→  /omni-sw:dev implement  →  /omni-sw:tl review
→  /omni-sw:qa test  →  /omni-sw:pm document  →  /omni-sw:tl document

Alternatively, let the Orchestrator run the entire workflow automatically:

/omni-sw:orchestrator "Build a REST API for order management"

Agents

Skill	Role	Leads phases
/omni-sw:pm	Product Manager	Plan (biz), Validate (biz), Document (biz)
/omni-sw:po	Product Owner	— (assists PM, produces backlog)
/omni-sw:tl	Tech Lead	Design, Validate (tech), Review, Document (tech)
/omni-sw:dev	Developer Specialist	Implement
/omni-sw:qa	QA Specialist	Test

Seven-phase workflow

graph LR
    Plan --> Design --> Validate --> Implement --> Review --> Test --> Document
    Validate -->|"PM reproves"| Plan
    Validate -->|"TL reproves"| Design
    Review -->|"blocking issues"| Implement
    Test -->|"bug failures"| Implement

#	Phase	Leader	Gate?	Key artifact
1	Plan	PM → PO	—	{DOCS_PATH}/PROJECT_BRIEF.md, backlog
2	Design	TL	—	{DOCS_PATH}/ARCHITECTURE.md
3	Validate	PM + TL	Dual approval	{DOCS_PATH}/VALIDATION.md
4	Implement	Dev	—	src/
5	Review	TL	Blocking issues	{DOCS_PATH}/REVIEW.md
6	Test	QA	All tests pass	tests/, {DOCS_PATH}/TEST_REPORT.md
7	Document	PM + TL	—	README.md, CHANGELOG.md, {DOCS_PATH}/API_REFERENCE.md

{DOCS_PATH} is a timestamped subfolder under agent_docs/ (e.g., agent_docs/build-auth-api-2026_03_21_10_30/), created per SDLC run to isolate working artifacts. The docs/ directory holds maintained descriptive documentation (architecture overview, flow diagrams) for human consumption.

Gate phases enforce quality before progression: both PM and TL must APPROVE to proceed from Validate; blocking issues must be resolved before leaving Review; all tests must pass before reaching Document.

Setup

Prerequisites

• Claude Code installed and authenticated
• Python 3.x (used by agency_cli.py for deterministic operations)

Configure a new project

The fastest way is the /omni-sw:init-omni-sw skill, which handles the full configuration in one step:

1. Start a Claude Code session with the plugin loaded from your project directory:

   claude --plugin-dir /path/to/omni-sw
   

2. Run the init skill:

   /omni-sw:init-omni-sw
   

   The skill detects whether the project directory is empty, has existing code, or already has a CLAUDE.md, and handles each case:

   • Empty directory — asks for project name, stack, and type, then generates CLAUDE.md
   • Existing code without CLAUDE.md — runs /omni-sw:repo-map to discover the stack, then creates CLAUDE.md
   • Existing CLAUDE.md — skips creation and goes straight to directories and hooks

3. Begin the workflow:

   /omni-sw:orchestrator "<objective>"
   

Manual setup

If you prefer to configure manually, copy and fill in the CLAUDE.md template:

cp /path/to/omni-sw/docs/templates/CLAUDE_TEMPLATE.md ./CLAUDE.md

Fill in: Stack, Conventions, Domain Glossary, Forbidden Patterns, Agent Overrides.

Then run setup to create directories and install hooks:

python /path/to/omni-sw/skills/shared/scripts/agency_cli.py setup --scan-root .

The agency is stack-agnostic. Agents read CLAUDE.md and adapt their output accordingly.

Automated orchestration

The /omni-sw:orchestrator skill drives the full 7-phase workflow end-to-end, spawning agents in the correct sequence, evaluating gates, handling feedback loops, and surfacing questions to you when needed.

Structured objective (recommended)

For any non-trivial project, write the objective in a dedicated file. Mention it with @ in the chat so Claude Code loads the file content into context before the orchestrator starts — this gives every spawned agent the full business context from the beginning.

Create docs/OBJECTIVE.md in your project root:

## Goal
Build an order management REST API with JWT authentication.