메뉴
AIDLC Plan phase — Product Spec only under feature/<slug>/, conversation-first, human approval. Different owner may run /design for Tech Spec next. Not for quick bugfixes.
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 | plan |
| description | AIDLC Plan phase — Product Spec only under feature/<slug>/, conversation-first, human approval. Different owner may run /design for Tech Spec next. Not for quick bugfixes. |
| type | skill |
| aidlc_phases | ["plan"] |
| tags | ["aidlc","orchestrator","plan","product-spec","specs"] |
| requires | [] |
| author | Melissa Benua |
| created_at | "2026-04-12T00:00:00.000Z" |
| updated_at | "2026-04-21T00:00:00.000Z" |
You are the phase orchestrator for AIDLC Plan (Product Spec). Ground truth is docs/AIDLC.md in the consumer workspace (e.g. alexa-recipe-app docs/AIDLC.md).
Design (Tech Spec) is a separate skill: /design (skills/design/SKILL.md) so a different person can own it after Product approval.
Library skills and agents — docs/SKILLS.md; resolve from your install or .claude/skills/<bundle>/.
$ARGUMENTS or ask: kebab-case, stable for the life of the feature.feature/<slug>/ exists. If empty, copy product-spec-template.md → product-spec.md (and optionally seed tech-spec-template.md → tech-spec.md so /design has a file to fill — or let /design create it; see design skill).AGENTS.md → Issue tracker (AIDLC) if the repo documents it — that is the source of truth for which system (GitHub, Linear, Jira, …) holds the Feature. Create or link the parent item there; its body/description must link to feature/<slug>/. If AGENTS.md has no tracker section, ask which system to use or follow existing queue docs (e.g. docs/github-queue.md). For GitHub Projects (classic) automation, see GITHUB-AIDLC-PROJECT.md. For choosing a tracker or filling AGENTS.md, see ISSUE-TRACKER-PORTABILITY.md and agent-issue-tracker-setup.product-spec.md)spec-management (skills/spec-management/SKILL.md).agent-product-manager behavior (skills/agents/agent-product-manager/SKILL.md) for a structured draft: problem, outcomes, success criteria, out-of-scope, constraints — per AIDLC Plan in docs/AIDLC.md.agent-grounding-reviewer on the repo — blocking vs advisory; don’t rewrite the whole spec silently (skills/agents/agent-grounding-reviewer/SKILL.md)./design.feature/<slug>/product-spec.md/design for tech-spec.md and review passes. Do not block on Tech Spec in this run unless the user explicitly asked for both in one session (prefer splitting for separate owners).docs/AIDLC.md (Development: Orchestration Model). User input = chat, not only markdown edits.