Domain-driven design for the parts of a product that follow it: subdomains, bounded contexts and their map, event storming (events, commands, reactions, read models, external systems) and the tactical model (aggregates, entities, value objects, business rules, domain services), traced to the requirements and components of the architecture.
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin ddd in Cynergis/oto-packs. Commands read from the repo's manifest — 28 days ago.
model-domainModel a part of a product with domain-driven design, in an OTO project that composes `ddd`: strategic design (subdomains, bounded contexts, the context map), event storming (events, commands, reactions, read models, external systems) and the tactical model (aggregates, entities, value objects, busin
startStart or extend an OTO knowledge project in this domain: Domain-driven design for the parts of a product that follow it: subdomains, bounded contexts and their map, event storming (events, commands, reactions, read models, external systems) and the tactical model (aggregates, entities, value objects
Problems found in this repo's manifests
A product's specification and its playbook: Atlas, who carries a product from an idea to a published knowledge base, the PRD captured section by section through the curate gates, and the specification page of the product's studio, read from the graph.
3 skills
The agent pattern for the parts of a product that people give work to through an agent rather than a screen: the jobs they hand it, its tools and what each changes, what it reads, its guardrails and who confirms, how it talks, its hand-offs and the test conversations that prove each job, traced to the requirements and components of the architecture.
2 skills
Where a product's parts run and what they are built with: the cloud and its accounts or projects, each environment's region, console, logs and infrastructure code, the service under each part, the stack with versions, secrets by where they are kept, the pipelines, and who decides each choice (a named person, or the builder within limits). Its briefs stop an implementing agent on any missing detail.
2 skills
A product's architecture, pattern-neutral: its context and drivers, decisions with their alternatives, systems, components, interfaces, data stores and environments, each traced to the requirement it satisfies; each part handed to the design-pattern pack it follows, found among the project's packs.
2 skills
What is planned, by whom, blocked by what: work items and milestones over the product's requirements, features and components; what slips when a component is late, what is overdue, what waits on a decision.
2 skills
Motor vehicle claims: policy, coverage, claim, incident, handling, money in and out.
1 skill
Production-grade engineering skills covering every phase of software development: spec, plan, build, verify, review, and ship.
25 skills · 4 agents
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
AI-powered codebase understanding — analyze, visualize, and explain any project
9 skills · 10 agents · hooks
Knowledge graph construction — entity extraction, relation mapping, and pathfinder graph traversal
2 skills · 1 command · 1 agent
Code intelligence powered by a knowledge graph. Provides execution flow tracing, blast radius analysis, and augmented search across your codebase.
12 skills · 1 MCP server · hooks
Set up endorctl and use Endor Labs to scan, prioritize, and fix security risks across your software supply chain
12 skills · 11 agents · hooks
This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.