Trogon Stack
Official@trogonstack
Offers architectural governance for event-sourced systems, requirements engineering, and standardized technical documentation frameworks for enterprise software delivery.
Agent Skills by Trogon Stack
Showing 40 vetted skills indexed across 1 GitHub repositories.
TrogonStackotel-name-metric
Validate and standardize OpenTelemetry metric names and attribute structures.
TrogonStackotel-name-span
Validate OpenTelemetry span names for low cardinality and semantic conventions.
TrogonStackeventmodeling-validating-event-models
Validate event-sourced models for consistency, completeness, and event sourcing principles.
TrogonStackeventmodeling-optimizing-stream-design
Analyze event stream design to validate aggregate boundaries and determine snapshotting strategies.
TrogonStackeventmodeling-designing-event-models
Design event-sourced domain models mapping business processes to immutable events and command-specific projections.
TrogonStackeventmodeling-storyboarding-events
Create UI storyboards and mockups from event modeling sequences.
TrogonStackeventmodeling-brainstorming-events
Extract domain events and state changes from project requirements for event modeling.
TrogonStackeventmodeling-translating-external-events
Translate external webhook payloads into domain-specific events with idempotent processing.
TrogonStackeventmodeling-applying-conways-law
Organize event-driven architectures into team-aligned bounded contexts with swimlanes.
TrogonStackeventmodeling-identifying-inputs
Map UI actions and processor triggers to domain roles and events.
TrogonStackeventmodeling-integrating-legacy-systems
Apply the side-car pattern to extract domain events from legacy systems.
TrogonStackeventmodeling-slicing-event-models
Decompose event models into independently implementable feature slices for parallel team development.
TrogonStackeventmodeling-validating-event-models-checklist
Validate event-sourced CQRS models against 16 architectural checks.
TrogonStackeventmodeling-orchestrating-event-modeling
Orchestrate the 9-step Event Modeling workflow to translate business requirements into an architectural model.
TrogonStackeventmodeling-plotting-events
Structure brainstormed events into a chronological narrative with dependency mapping.
TrogonStackeventmodeling-checking-completeness
Validate event model completeness by tracing field origins and destinations.
TrogonStackeventmodeling-identifying-outputs
Identify read models and query patterns from domain events in event-sourced architectures.
TrogonStackeventmodeling-elaborating-scenarios
Define system behavior with Given-When-Then scenarios in Gherkin format.
TrogonStackdatadog-design-dashboard
Design and audit Datadog dashboard layouts for operational readiness.
TrogonStackgh-enrich-pr-description
Enrich GitHub pull request descriptions by analyzing git history and branch diffs.
TrogonStackprd-current-state
Document existing user workflows, manual workarounds, and operational costs.
TrogonStackrequirements-operating-model
Enforce structured boundaries between requirements, blueprints, and work orders.
TrogonStackfrd-review
Audit Feature Requirements Documents against templates, terminology, and acceptance criteria standards.
TrogonStackprd-custom-overview
Draft product-level overview documents from predefined templates within the .trogonai/project directory.
Frequently Asked Questions About Trogon Stack
FAQPage SchemaWhat specific architectural tasks does Trogon Stack support?▼
Trogon Stack enables the design of event-sourced domain models, validation of CQRS architectures against 16 architectural checks, and the creation of NATS subject hierarchies for robust pub/sub messaging patterns.
Which personas benefit most from these architectural capabilities?▼
System architects, product managers, and lead engineers benefit from these capabilities by enforcing consistency across requirements, event-driven design patterns, and technical documentation standards within complex enterprise environments.
What are the prerequisites for implementing these architectural standards?▼
Implementation requires a foundational understanding of event-driven architecture, CQRS principles, and the Diataxis documentation framework, alongside access to a project directory structured for standardized markdown requirements and documentation stubs.