メニュー
Solution architect for event-driven systems, distributed processes, and Event Sourcing patterns. Helps structure components using Saga, Process Manager, Choreography, and Outbox patterns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Implement a feature fully autonomously in the background as a Workflow — decompose, then run each task through test-design → implement → refactor → review → verify, closing on executed evidence instead of human approval gates. Use when you want unattended end-to-end implementation on a branch and will review the result as a diff/PR afterward.
Deliver a large user story as multiple parallel PRs. On first run it decomposes the story into PR-sized slices with a dependency DAG (decompose-to-prs) and, after you review the plan, scaffolds a git worktree per slice and launches implement-flow in each via workmux. Re-run it to deliver later waves — it adopts the existing plan instead of re-planning. Use when a story is too big for one PR.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, pausing only for plan approval and pre-commit approval.
Implement a feature autonomously through the full test-design → test-write → implement → refactor → review loop, running independent tasks in parallel (isolated git worktrees) and pausing only for plan approval and pre-commit approval.
Post-run verification of an autonomous implementation run (implement-flow / implement-auto / implement). Runs the run-verifier agent to catch the failure modes the evidence gate can't see — staged tails, dead code, vacuous receipts, collapsed commits — and, with --fix, remediates them. Use after an unattended run, before trusting its "done".
Write or edit an article or note. Follows writing style guidelines for clarity and consistency.
| name | solution-architect |
| description | Solution architect for event-driven systems, distributed processes, and Event Sourcing patterns. Helps structure components using Saga, Process Manager, Choreography, and Outbox patterns. |
Guidance for implementing distributed processes without distributed transactions.
| Pattern | Best For | State |
|---|---|---|
| Saga | Simple workflows, most cases | Stateless |
| Process Manager | Complex, multi-step decisions | Stateful |
| Choreography | Decentralized, no coordinator | Distributed |
Before implementing:
See: ~/.config/ai/guidelines/architecture/implementation/event-driven-patterns.md
