메뉴
Analyze trade-offs between competing architectural concerns
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | aget-assess-tradeoffs |
| description | Analyze trade-offs between competing architectural concerns |
| archetype | architect |
| allowed-tools | ["Read","Glob","Grep"] |
Analyze trade-offs between competing concerns and quality attributes. Provides structured decision support for architectural choices.
When this skill is invoked:
Identify Competing Concerns
Evaluate Options
Assess Reversibility
Formulate Recommendation
## Trade-off Analysis: [Decision Topic]
### Context
[What decision needs to be made and why]
### Competing Concerns
| Quality Attribute | Option A | Option B | Option C |
|-------------------|:--------:|:--------:|:--------:|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐ |
| Maintainability | ⭐ | ⭐⭐⭐ | ⭐⭐ |
| Cost | ⭐⭐ | ⭐ | ⭐⭐⭐ |
| Time to Market | ⭐ | ⭐⭐ | ⭐⭐⭐ |
### Reversibility Assessment
| Option | Reversibility | Cost to Change | Lock-in Risk |
|--------|---------------|----------------|--------------|
| A | Low | High | Significant |
| B | High | Low | Minimal |
| C | Medium | Medium | Moderate |
### Recommendation
**Choose**: [Option X]
**Rationale**: [Why this trade-off resolution is appropriate given context]
**What We're Trading**: [Quality we're deprioritizing] for [Quality we're prioritizing]
### Rejected Alternatives
| Option | Why Rejected |
|--------|--------------|
| [Option Y] | [Specific reason] |
### Conditions for Revisiting
- Revisit if: [Condition that would change the analysis]
Close a PROJECT_PLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECT_PLAN lifecycle.
Commit a selected candidate goal into a durable, governed Goal artifact. The D71-Strict singular committer of the propose-goals→create-goal verb pair (L1067/L1085). Two-tier (REQ-3): committed goals = a structured section in governance/GOALS.md; aspirational = agent-internal .aget/goals/aspirational.jsonl. Direct authoring of a committed-Goal section is PROHIBITED once this skill is invoked. Implements AGET_GOAL_SPEC v0.2.0 (CAP-GOAL-001..011).
Scaffold approved initiative manifests at planning/initiatives/INIT-*.md. Mirrors /aget-create-project STRICT (D71 Layer 2) — direct Write/Edit to planning/initiatives/ is PROHIBITED once this skill is invoked. Implements SOP_initiative.md (graduated procedure) + future AGET_INITIATIVE_SPEC. Consumes PROPOSAL_init_*.md substrate produced by /aget-propose-initiative.
Create lightweight initiative proposals (PROPOSAL_init_*.md) before full INIT-*.md scaffolding. Follows 'propose -> review -> approve -> create' governance pattern. Advisory enforcement. Implements AGET_INITIATIVE_SPEC v1.0.1 CAP-INIT-PROP-001..012.
Record principal authorization (GO) with Healthy Friction enforcement of the principle-triad (spec+verify-first, coherence-next, evidence-driven); release agent execution within authorized scope. Authorization-only — does not execute the authorized work.
Generate standalone narrative documents from session artifacts, optimized for a target consumption medium (NotebookLM, slides, memo, share-draft). Use when the user says "create briefing", "create a briefing for NotebookLM", "make this listenable", "summarize session for [medium]", "prepare a listen", "brief me on [topic]", or "create a summary I can share".