Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
After-Action Review—structured debrief asking what was expected, what happened, why the difference, and what next. Use after projects, launches, presentations, or any significant event.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
Conduct a structured debrief to extract learning from any significant event or experience.
Work through the four core questions honestly and specifically. Focus on events and systems, not blaming individuals.
Event: What are we reviewing? Date: When did it happen? Participants: Who was involved?
Before the event, what did we think would happen?
Goals/Objectives
Plan
Success Criteria
Assumptions
Facts only—what occurred, not why
Timeline
| Time | Event |
|---|---|
| [When] | [What happened] |
Outcomes
Compared to Expected
| Expected | Actual | Gap |
|---|---|---|
| [expectation] | [reality] | [+/-] |
Analysis of the gap between expected and actual
What Went Well (sustain these)
| Success | Contributing Factors |
|---|---|
| [what worked] | [why it worked] |
What Didn't Go Well (improve these)
| Problem | Root Cause |
|---|---|
| [what failed] | [why it failed] |
Surprises
Specific actions to sustain or improve
Sustain (keep doing these)
| Action | Owner | How to Protect It |
|---|---|---|
| [what to continue] | [who] | [mechanism] |
Improve (change these)
| Action | Owner | By When |
|---|---|---|
| [what to change] | [who] | [deadline] |
Key Takeaways Top 3 lessons from this review:
Follow-up When will we check if improvements are working?
$ARGUMENTS
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Master backend architectures, REST API design, microservices, and server-side development across multiple languages. Use this as a central index to access specialized sub-skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
在每次回复中使用固定前缀并列出本次实际参考的指令/文件,便于校验是否遵循上下文与规则。
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 21risk tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate 2chat tasks via Rube MCP (Composio). Always search tools first for current schemas.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Arquitecto de Soluciones Principal y Consultor Tecnológico de Andru.ia. Diagnostica y traza la hoja de ruta óptima para proyectos de IA en español.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
[00] META. Orchestrate skills into dynamic chains for complex tasks. Analyzes the task, discovers available skills, builds an optimal chain, explains why each skill is needed, and executes step-by-step with user confirmation. Use for any complex task requiring multiple thinking/research/analysis steps. Triggers on "plan this", "how to approach", "what's the strategy", "build a plan", or any multi-step problem requiring skill orchestration.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.