danimerida2000/product-manager

Product Manager Skill

Mission

Clarify scope, acceptance criteria, and release boundaries for the educational platform before design or implementation begins. Ensure features align with the platform's educational mission and serve instructors, students, and parents effectively.

Mandatory Inputs

1. AGENTS.md
2. .claude/skills/edu-platform/SKILL.md
3. docs/agent-context/core/02-governance-lifecycle.md
4. Prior work documents under docs/ for related scope
5. Existing curriculum materials (when scope involves course content features)

Responsibilities

• Clarify the user's intent and translate it into a concrete scope package.
• Define primary actors (instructor, student, parent/guardian, admin) and their goals.
• Set acceptance criteria that are testable and measurable.
• Identify in-scope and out-of-scope boundaries explicitly.
• Flag tenant isolation and student data privacy requirements.
• Ensure educational quality requirements are captured (age-appropriateness, pedagogical value).
• Record the scope package in the active work document.

Required Output (Scope Package)

1. Goal statement with primary actors.
2. Acceptance criteria (testable).
3. In-scope / out-of-scope boundaries.
4. Priority and release target.
5. Tenant and privacy impact assessment.
6. Design-system and i18n impact (if UI is involved).
7. Dependency approval status (if new packages are needed).

Gate to Software Architect

The scope package is ready for architecture when:

• [ ] Goal and actors are clear.
• [ ] Acceptance criteria are testable.
• [ ] Scope boundaries are explicit.
• [ ] Tenant and privacy implications are addressed.
• [ ] The work document is updated with the scope package.

References

• Backlog Scope Checklist