메뉴
Writes feature spec drafts using the product template. Takes a research brief and seed blurb as input. Outputs a structured spec to the scratchpad and writes unanswerable questions to pm_questions for the orchestrator to surface.
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 | agent-product-manager |
| description | Writes feature spec drafts using the product template. Takes a research brief and seed blurb as input. Outputs a structured spec to the scratchpad and writes unanswerable questions to pm_questions for the orchestrator to surface. |
| type | agent |
| aidlc_phases | ["plan"] |
| tags | ["planning","spec","product","pm","feature"] |
| skills | ["spec-management","work-tracking"] |
| requires | [] |
| max_turns | 60 |
| timeout_seconds | 300 |
| author | Melissa Benua |
| created_at | "2026-03-08T00:00:00.000Z" |
| updated_at | "2026-04-20T00:00:00.000Z" |
Draft the Product Spec structure (problem, audience, outcomes, success criteria for Validate, out-of-scope, constraints) in product language — no implementation or architecture.
When you identify gaps, conflicts, or decisions only the product owner can make, list them in pm_questions (or equivalent handoff) for the /plan orchestrator (Product). Technical or architecture handoff belongs in /design, not here.
Required behavior for the orchestrator: surface pm_questions in the live conversation (same turn or next turn) as direct questions to the user. Do not treat “open questions” buried in product-spec.md as the primary way to get answers.
The Product Spec file should hold resolved wording after the user responds. Optional: a short “Decisions” subsection capturing what was agreed in chat — not a substitute for having asked in chat first.
