Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs.
npx skills add https://github.com/JohannWilfridCalixte/agentic --skill agentic-skill-product-manager이 명령을 Claude Code에 복사하여 붙여넣어 스킬을 설치하세요
| name | agentic:skill:product-manager |
| description | Use when producing product artifacts - epics, user stories, acceptance criteria, or analytics specs. |
Produce product-only artifacts. No technical implementation details.
.claude/_agentic_output/product/prd/{epicNumber}-EPIC-{epicName}/epic.md.claude/_agentic_output/product/prd/{epicNumber}-EPIC-{epicName}/US-{usName}-{usNumber}.mdEpic ID: EPIC-{epicNumber}
Epic Name:
Status: Draft | Ready | In Progress | Done
Owner: PM Agent
Last Updated: (ISO timestamp)
Links: Vision doc path(s)
Sections: Problem Statement, Target Users, Goals & Non-Goals, Scope (In/Out), Success Metrics, Product Tracking, Risks & Mitigations, Dependencies, Release Strategy (Now/Next/Later), User Stories Index.
Epic ID: EPIC-{epicNumber}
User Story ID: US-{usNumber}
Title:
Status: Draft | Ready | In Progress | Done
Owner: PM Agent
Last Updated: (ISO timestamp)
| Section | Content |
|---|---|
| Narrative | As a / I want / So that |
| Business Rules | Product-level |
| Acceptance Criteria | Gherkin with AC-01, AC-02... |
| Input Format Specification | MANDATORY for calculations - all valid raw formats |
| Reference Validation Scenarios | MANDATORY when existing solution exists |
| Edge Cases | Product-level |
| Analytics & Telemetry | Business terms |
| Privacy / Compliance | GDPR/SOC2 non-technical |
| Open Questions | |
| Out of Scope | Explicit |
For calculation/transformation stories:
When existing solution exists:
/sync-issue on each output fileUse when defining product direction, vision document sections, or roadmap. Triggers on strategic product planning, vision creation, or vision document quality review.
Use when designing UI, choosing colors, typography, spacing, creating visual hierarchy, or making design decisions. Based on Refactoring UI by Wathan & Schoger.
Use when someone needs a plain-language explanation of how an existing feature or edge case behaves in the codebase. Triggers - non-technical stakeholder asks how something works, need code-informed functional explanation, need to understand rules or edge cases without implementation planning.
Use when a developer wants to go from rough idea to working code autonomously. Triggers - imperfect prompt, solo dev wants full pipeline, "just build it", idea to implementation without manual steps.
Use when creating a new agentic workflow skill. Triggers - need new multi-step orchestrated process, want to add workflow to agentic framework, building spec-driven pipeline.
Use when building frontend features from idea to implementation. Triggers on new UI components, pages, or features needing design and code.