메뉴
AIDLC Design phase — Tech Spec under feature/<slug>/, review passes, human gate before /build. Requires an approved Product Spec (run /plan first or confirm approval in-thread).
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Onboards AIDLC issue-tracker choice for a consumer repo: fills AGENTS.md Issue tracker (AIDLC) table, checklists for GitHub vs Linear vs Jira paths, and links to ISSUE-TRACKER-PORTABILITY docs. Does not run external APIs; guides humans through wiring.
AIDLC Build + Test orchestrator (TDD). Delivers an open PR with green CI per Tech Spec; re-enters to triage /review PR comments — fix or reply+resolve. Not for spec-only work.
Modern web development patterns for React, Vue, and vanilla JS including component architecture, state management, and performance. Use when building web UIs, optimizing frontend performance, or implementing accessibility.
AIDLC Learn orchestrator. Run after Validate phase PASS — ADRs, docs, retrospective notes. Not combined with /ship in headless automation.
AIDLC Test gate + Review — five review passes (spec, tests, DevOps, UI via Chrome DevTools MCP, security); post PR comments; hand off to /build.
AIDLC Validate phase orchestrator (/ship). Scorecard vs Product Spec, deploy gates, UI validation when applicable. Learn is separate — run /learn after PASS.
| name | design |
| description | AIDLC Design phase — Tech Spec under feature/<slug>/, review passes, human gate before /build. Requires an approved Product Spec (run /plan first or confirm approval in-thread). |
| type | skill |
| aidlc_phases | ["design"] |
| tags | ["aidlc","orchestrator","design","tech-spec","specs"] |
| requires | [] |
| author | Melissa Benua |
| created_at | "2026-04-20T00:00:00.000Z" |
| updated_at | "2026-04-21T00:00:00.000Z" |
You are the phase orchestrator for AIDLC Design (Tech Spec). Ground truth is docs/AIDLC.md in the consumer workspace.
Plan (Product Spec) is /plan (skills/plan/SKILL.md). This skill assumes Product Spec is approved (or the user explicitly approves proceeding in the current thread).
Library skills — docs/SKILLS.md; resolve from your install or .claude/skills/<bundle>/.
$ARGUMENTS or from the same folder the team used for /plan.feature/<slug>/product-spec.md. If it is missing or clearly not approved, stop and ask the human to run /plan or confirm approval — do not invent product scope.feature/<slug>/ exists. If tech-spec.md is missing, create it from tech-spec-template.md./plan (per AGENTS.md → Issue tracker (AIDLC)). For GitHub-only automation, see GITHUB-AIDLC-PROJECT.md. Portability: ISSUE-TRACKER-PORTABILITY.md.tech-spec.md)tech-spec.md in this feature folder unless work is split across sub-issues (link related specs in the doc).docs/AIDLC.md.| Pass | Library skill |
|---|---|
| Architecture / boundaries | architecture (skills/architecture/SKILL.md) |
| Frontend | frontend-web (skills/frontend-web/SKILL.md) |
| Backend / API | backend-saas (skills/backend-saas/SKILL.md) |
| Testing strategy | testing (skills/testing/SKILL.md) |
| CI / Docker / deploy | architecture + read .github/workflows/, docker-compose, Dockerfiles |
/build.feature/<slug>/tech-spec.md (and linked ADR drafts under adr/ if your repo uses them per spec-management)docs/AIDLC.md orchestration model.