Menu
Product requirements to user stories pipeline stage (PM → Spec)
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Run a multi-agent code review on a GitHub pull request, with parallel security / performance / architecture / style passes, inline comments, and quality-gate enforcement. Use when asked to "github code review", "review github pr", "run code review on PR", "swarm review", "automated PR review", or "post inline review comments".
Manage GitHub issues, project boards, sprints, and milestones with swarm-coordinated automation — issue triage, decomposition into subtasks, board sync, sprint planning, KPI tracking. Use when asked to "github project management", "manage github projects", "github issue automation", "swarm project board", "automate sprint", "triage issues", or "set up project board".
Extract clean article content from a URL (blog post, news article, tutorial) and save it as readable text with ads, navigation, and other clutter removed. Use when asked to "extract article", "scrape text from URL", "download blog post", "parse HTML article", "save article as text", or "clean article content from a webpage".
Dispatch one focused agent per independent problem domain so investigations run concurrently. Use when facing 2+ independent tasks with no shared state — for example "spawn agents in parallel", "parallel debugging", "fan out tasks", "investigate multiple failures at once", or "distribute independent work across agents".
Create HTML dashboards with KPI cards, bar/pie/line charts, progress indicators, and data tables. Use when asked to "create dashboard", "build KPI dashboard", "generate metrics visualization", "make analytics dashboard", "show performance dashboard", or "render data visualization as HTML".
Guide for choosing the right AI coding tool for the task. Use when user asks "which AI should I use", "should I use Claude or Cursor", "what's the best tool for X", or when helping decide between Claude Code, Cursor, Windsurf, VSCode + Copilot, Gemini, Grok, Codex, Qwen, or this Claude interface.
| name | pipeline-pm-spec |
| description | Product requirements to user stories pipeline stage (PM → Spec) |
| trigger | When user provides high-level requirements or feature requests |
Pipeline Position: First stage (Requirements → User Stories)
Next Stage: pipeline-arch-review
Transform high-level requirements into actionable user stories following INVEST principles.
Requirements Gathering
User Story Creation
Acceptance Criteria
Prioritization
# Feature: [Feature Name]
## Overview
[Brief description of the feature and its purpose]
## User Stories
### Story 1: [Title]
**As a** [role]
**I want** [capability]
**So that** [benefit]
**Priority:** Must-have | Should-have | Nice-to-have
**Estimate:** S | M | L
**Acceptance Criteria:**
- Given [context]
When [action]
Then [outcome]
- Given [context]
When [action]
Then [outcome]
### Story 2: [Title]
[Repeat format]
## Success Metrics
- [How we'll measure success]
## Constraints
- [Technical or business constraints]
## Dependencies
- [External dependencies or prerequisites]
## Next Step
→ Use `pipeline-arch-review` to design architecture for these stories
After completing spec, suggest:
Use pipeline-arch-review to design the technical architecture for these user stories.
This ensures smooth transition to the next pipeline stage.