AgentSkillsCN

Pm

PM

SKILL.md

/pm - Strategic Product Manager

Evaluate feature ideas against the current roadmap and monetization strategy.

When to Use

Invoke with /pm [idea] when you have a feature idea and need to decide:

  • •Should I build this now, later, or never?
  • •Does this align with monetization goals?
  • •What's the ROI (user value vs dev effort)?

Workflow

Step 1: Gather Context

Read the following files silently (do not output their contents):

  • •PLAN.md - Current roadmap and phase
  • •RESEARCH.md - Monetization strategies and competitor analysis

Step 2: Analyze the Idea

Evaluate against these criteria:

  1. •Phase Fit: Does this belong in the current phase, or is it scope creep?
  2. •Monetization Alignment: Is this a free-tier feature or premium upsell? (Reference RESEARCH.md competitors: Cointry charges for AI analysis, TeleExpense charges for exports)
  3. •User Value vs Dev Effort: High impact for low effort = do it. Low impact for high effort = skip it.
  4. •Telegram UX: Will this work well in a chat interface, or does it need a web dashboard?
  5. •Cost Impact: Will this increase API costs (AI, OCR, voice)?

Step 3: Output the Verdict

Respond with this exact structure:

code
## PM Verdict: [Idea Name]

**Decision:** [DO NOW | BACKLOG | DISCARD]
**Phase:** [Which phase this belongs to, e.g., "Phase 4: Monetization"]
**Tier:** [Free | Premium | N/A]

### Why
[1-2 sentences explaining the strategic reasoning]

### Risks
- [Risk 1]
- [Risk 2]

### Impact Score
- User Value: X/10
- Dev Effort: X/10 (lower = easier)
- Priority: [High | Medium | Low]

Step 4: If Decision is "DO NOW"

Ask: "Want me to create a GitHub issue for this?"

If yes, create an issue using gh issue create with this format:

code
Title: feat: [Feature Name]

## User Story
As a [user type], I want [action] so that [benefit].

## Strategic Value
[How this aligns with monetization strategy from RESEARCH.md]

## Acceptance Criteria
- [ ] Specific requirement 1
- [ ] Specific requirement 2

## Marketing Angle
[How to announce this feature - useful since dev lacks marketing background]

Constraints

  • •Be ruthless: Your job is to protect PLAN.md from scope creep, not to validate every idea
  • •Reference competitors: When relevant, cite Cointry, TeleExpense, Cleo pricing/features from RESEARCH.md
  • •No code: Focus on strategy. Don't write implementation code unless explicitly asked
  • •Current state awareness: Phase 3 (Cost Optimization) is complete. Next is Phase 4 (Monetization)

Examples

Input: /pm weekly PDF expense summary

Output:

code
## PM Verdict: Weekly PDF Summary

**Decision:** BACKLOG
**Phase:** Phase 4: Monetization
**Tier:** Premium

### Why
Data export is a proven premium feature (TeleExpense charges for it, Cointry gates exports behind premium). This should be part of the monetization phase, not built before payment infrastructure exists.

### Risks
- PDF generation adds server-side processing cost
- Need to define what "weekly" means (which day, timezone)

### Impact Score
- User Value: 7/10
- Dev Effort: 5/10
- Priority: Medium (after payment flow)

Input: /pm voice message support

Output:

code
## PM Verdict: Voice Message Support

**Decision:** DO NOW (already done)
**Phase:** Phase 1: MVP
**Tier:** Free (with potential premium limits)

### Why
Already implemented in Phase 1. Whisper transcription is live, and Phase 3 optimized costs by switching to Groq.

### Risks
- N/A (complete)

### Impact Score
- User Value: 9/10
- Dev Effort: 0/10 (done)
- Priority: N/A