mirror of
https://github.com/magnus919/agent-skills.git
synced 2026-09-15 13:36:35 +03:00
Add outbox/inbox implementation, idempotent message handling, migration coexistence seams, evals, and exact specialist routing.\n\nAI-assisted: Jasper orchestrated implementation and verification with OpenCode. Signed-off-by: Magnus Hedemark <magnus919@pm.me>
30 lines
1.9 KiB
Markdown
30 lines
1.9 KiB
Markdown
# Source Index
|
|
|
|
This skill is an original, task-centered synthesis. Sources inform concepts and
|
|
terminology; the repository does not reproduce protected prose, tables, diagrams,
|
|
examples, taxonomies, or chapter structures.
|
|
|
|
| Source | Use in this skill | URL |
|
|
|---|---|---|
|
|
| Agent Skills specification | Progressive disclosure, relative references, and skill structure | https://agentskills.io/specification |
|
|
| CloudEvents | Event identity and envelope boundary considerations | https://cloudevents.io/ |
|
|
| Martin Fowler, Event Sourcing | Distinguishing event history from ordinary event publication | https://martinfowler.com/eaaDev/EventSourcing.html |
|
|
| Martin Fowler, Strangler Fig Application | Incremental coexistence vocabulary | https://martinfowler.com/bliki/StranglerFigApplication.html |
|
|
| Martin Fowler, Parallel Change | Compatibility-first change sequencing | https://martinfowler.com/bliki/ParallelChange.html |
|
|
| PostgreSQL documentation | Transaction isolation and failure behavior | https://www.postgresql.org/docs/current/transaction-iso.html |
|
|
| OpenTelemetry documentation | Trace and metric instrumentation concepts | https://opentelemetry.io/docs/ |
|
|
|
|
## Ownership Notes
|
|
|
|
- DDD concepts and anti-corruption boundaries route to `programming-principles`.
|
|
- Event contract and delivery semantics route to `api-design-and-evolution`.
|
|
- Cross-system transition and recovery route to `migration-engineering`.
|
|
- Schema and pipeline operations route to `data-engineering`.
|
|
- Security controls and sensitive logging route to `secure-software-engineering`.
|
|
- Release promotion and rollback mechanics route to `release-engineering`.
|
|
|
|
The private architecture comparison report supplied for this task was used only as
|
|
safe synthesized research input. Purchased ebooks were not read or quoted. Future
|
|
edits should be rewritten from user tasks and public sources if wording or structure
|
|
resembles a source too closely.
|