메뉴
Use when applying judgment guidelines, success criteria, or handoff formats. Trigger with lifecycle ops request. Loaded by ai-maestro-architect-agent-main-agent
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when decomposing systems into modules with clear boundaries. Trigger with modularization or module boundary request. Loaded by ai-maestro-architect-agent-main-agent
Use when designing architectures, identifying risks, creating roadmaps, or breaking work into tasks. Trigger with planning or architecture design request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing requirements, initializing plans, or approving transitions. Trigger with requirements analysis or plan initialization request. Loaded by ai-maestro-architect-agent-main-agent
Use when recording stack choices, constraints, or managing handoffs. Trigger with session memory ops request. Loaded by ai-maestro-architect-agent-main-agent
Use when persisting decisions, patterns, and constraints across sessions. Trigger with session memory or handoff request. Loaded by ai-maestro-architect-agent-main-agent
Use when managing design document states or lifecycle transitions. Trigger with design lifecycle or state transition request. Loaded by ai-maestro-architect-agent-main-agent
| name | amaa-design-lifecycle-ops |
| description | Use when applying judgment guidelines, success criteria, or handoff formats. Trigger with lifecycle ops request. Loaded by ai-maestro-architect-agent-main-agent |
| context | fork |
| user-invocable | false |
| agent | ai-maestro-architect-agent-main-agent |
Operational references for design lifecycle: judgment calls, success verification, workflow checklists, ADR templates, and handoff document format.
Copy this checklist and track your progress:
| Document | Content |
|---|---|
| judgment-guidelines.md | When to research external APIs instead of using existing documentation, When to create an ADR instead of just documenting the decision, When to modularize a system instead of keeping it simple, When to escalate unclear requirements to AMCOS for clarification |
| success-criteria.md | Overview, Requirements Captured, Architecture Designed, APIs Researched, Modules Specified, Handoff Prepared |
| workflow-checklists.md | Introduction, Checklist: Requirements Analysis, Checklist: Design Phase, Checklist: Handoff Preparation |
| adr-templates.md | Standard ADR Template, Context, Decision, Alternatives Considered, Rationale, Consequences, Related Decisions |
| handoff-format.md | Overview, Handoff Validation Checklist, Handoff Document Template, Executive Summary, Design Artifacts, Implementation Sequence, Risks and Mitigations |
Example: Use judgment-guidelines.md to decide whether to create ADR for database choice, then verify with success-criteria.md
| Issue | Fix |
|---|---|
| Success criteria not met | Review checklist, complete missing items before proceeding |
| ADR incomplete | Use template sections, ensure all fields populated |
| Type | Description |
|---|---|
| ADR documents | docs_dev/design/adrs/ |
| Handoff documents | docs_dev/design/handoff-{uuid}.md |
See Reference Documents table above.
