pm-workflow-trigger
Type: WRITE-CAPABLE
DAIC Modes: IMPLEMENT only
Priority: High
Trigger Reference
This skill activates on:
- Keywords: "start epic", "start issue", "work on epic", "begin issue", "parse PRD", "create PRD", "begin epic", "launch epic", "launch issue", "start working on epic", "start working on issue", "convert PRD"
- Intent Patterns:
(start|begin|launch|work on).*(epic|issue), (parse|convert).*?PRD, create.*(PRD|product requirements), work.*?on.*(epic|issue)
From: skill-rules.json - pm-workflow-trigger configuration
Purpose
Automatically trigger PM workflow commands (/pm:epic-start, /pm:issue-start, /pm:prd-parse, /pm:prd-new) when users express intent to start work on epics/issues or manage PRDs using natural language. This skill requires IMPLEMENT mode as it creates branches, modifies files, and updates project state.
Core Behavior
When activated in IMPLEMENT mode with an active cc-sessions task:
Workflow Detection
- Detect epic/issue/PRD workflow intent from natural language
- Examples: "Start working on epic auth-system", "Parse PRD for dashboard"
- Route to appropriate PM command based on intent
Command Routing
- Epic workflows: "start epic X" →
/pm:epic-start X
- Issue workflows: "start issue #123" →
/pm:issue-start 123
- PRD parsing: "parse PRD X" →
/pm:prd-parse X
- PRD creation: "create PRD" →
/pm:prd-new
Execution
- Invoke appropriate PM command with extracted arguments
- Commands create git branches, modify task files, sync with GitHub
- Return status and next steps to user
Natural Language Examples
Triggers this skill:
- ✓ "Start working on epic auth-system"
- ✓ "Begin issue #456"
- ✓ "Launch epic dashboard-redesign"
- ✓ "Work on issue 789"
- ✓ "Parse PRD for user-profiles"
- ✓ "Convert PRD to epic"
- ✓ "Create new PRD"
- ✓ "Start epic X"
Does NOT trigger:
- ✗ "What's the status of epic X?" (status query, not workflow start)
- ✗ "Show issue #123" (info display, not workflow start)
- ✗ "List epics" (listing, not starting work)
Safety Guardrails
WRITE-CAPABLE RULES:
- ✓ Only execute in IMPLEMENT mode
- ✓ Verify active cc-sessions task exists
- ✓ Follow approved manifest/todos
- ✓ Never weaken write-gating or DAIC discipline
- ✓ Confirm git working directory is clean before creating branches
Workflow Safety:
- Verify epic/issue exists before starting work
- Check for GitHub sync status before proceeding
- Confirm no uncommitted changes exist
- Create branches from main (unless resuming work)
- Log workflow actions for traceability
PM Commands Invoked
This skill routes to these PM commands:
| Intent |
Command |
Purpose |
| Start epic |
/pm:epic-start <name> |
Create branch, launch parallel agents for epic tasks |
| Start issue |
/pm:issue-start <number> |
Begin work on GitHub issue |
| Parse PRD |
/pm:prd-parse <name> |
Convert PRD into epic with tasks |
| Create PRD |
/pm:prd-new |
Generate new product requirements document |
Implementation Notes
This skill acts as a natural language wrapper around PM workflow commands. The actual PM logic lives in .claude/commands/pm/* files, which:
- Manage epic/issue lifecycle
- Sync with GitHub issues
- Create and manage git branches
- Coordinate parallel work streams
- Track task status and progress
This skill simply detects the intent, extracts arguments, and routes to the appropriate PM command with write-gating enforcement.
1---2name: pm-workflow-trigger3description: Natural language wrapper for PM workflow commands - automatically triggers /pm:epic-start, /pm:issue-start, /pm:prd-parse when users express PM workflow intent4---5
6# pm-workflow-trigger
7
8**Type:** WRITE-CAPABLE
9**DAIC Modes:** IMPLEMENT only
10**Priority:** High
11
12## Trigger Reference
13
14This skill activates on:
15- **Keywords:** "start epic", "start issue", "work on epic", "begin issue", "parse PRD", "create PRD", "begin epic", "launch epic", "launch issue", "start working on epic", "start working on issue", "convert PRD"
16- **Intent Patterns:** `(start|begin|launch|work on).*(epic|issue)`, `(parse|convert).*?PRD`, `create.*(PRD|product requirements)`, `work.*?on.*(epic|issue)`
17
18From: `skill-rules.json` - pm-workflow-trigger configuration
19
20## Purpose
21
22Automatically trigger PM workflow commands (`/pm:epic-start`, `/pm:issue-start`, `/pm:prd-parse`, `/pm:prd-new`) when users express intent to start work on epics/issues or manage PRDs using natural language. This skill requires IMPLEMENT mode as it creates branches, modifies files, and updates project state.
23
24## Core Behavior
25
26When activated in IMPLEMENT mode with an active cc-sessions task:
27
281. **Workflow Detection**
29 - Detect epic/issue/PRD workflow intent from natural language
30 - Examples: "Start working on epic auth-system", "Parse PRD for dashboard"
31 - Route to appropriate PM command based on intent
32
332. **Command Routing**
34 - **Epic workflows:** "start epic X" → `/pm:epic-start X`
35 - **Issue workflows:** "start issue #123" → `/pm:issue-start 123`
36 - **PRD parsing:** "parse PRD X" → `/pm:prd-parse X`
37 - **PRD creation:** "create PRD" → `/pm:prd-new`
38
393. **Execution**
40 - Invoke appropriate PM command with extracted arguments
41 - Commands create git branches, modify task files, sync with GitHub
42 - Return status and next steps to user
43
44## Natural Language Examples
45
46**Triggers this skill:**
47- ✓ "Start working on epic auth-system"
48- ✓ "Begin issue #456"
49- ✓ "Launch epic dashboard-redesign"
50- ✓ "Work on issue 789"
51- ✓ "Parse PRD for user-profiles"
52- ✓ "Convert PRD to epic"
53- ✓ "Create new PRD"
54- ✓ "Start epic X"
55
56**Does NOT trigger:**
57- ✗ "What's the status of epic X?" (status query, not workflow start)
58- ✗ "Show issue #123" (info display, not workflow start)
59- ✗ "List epics" (listing, not starting work)
60
61## Safety Guardrails
62
63**WRITE-CAPABLE RULES:**
64- ✓ Only execute in IMPLEMENT mode
65- ✓ Verify active cc-sessions task exists
66- ✓ Follow approved manifest/todos
67- ✓ Never weaken write-gating or DAIC discipline
68- ✓ Confirm git working directory is clean before creating branches
69
70**Workflow Safety:**
71- Verify epic/issue exists before starting work
72- Check for GitHub sync status before proceeding
73- Confirm no uncommitted changes exist
74- Create branches from main (unless resuming work)
75- Log workflow actions for traceability
76
77## PM Commands Invoked
78
79This skill routes to these PM commands:
80
81| Intent | Command | Purpose |
82|--------|---------|---------|
83| Start epic | `/pm:epic-start <name>` | Create branch, launch parallel agents for epic tasks |
84| Start issue | `/pm:issue-start <number>` | Begin work on GitHub issue |
85| Parse PRD | `/pm:prd-parse <name>` | Convert PRD into epic with tasks |
86| Create PRD | `/pm:prd-new` | Generate new product requirements document |
87
88## Implementation Notes
89
90This skill acts as a natural language wrapper around PM workflow commands. The actual PM logic lives in `.claude/commands/pm/*` files, which:
91- Manage epic/issue lifecycle
92- Sync with GitHub issues
93- Create and manage git branches
94- Coordinate parallel work streams
95- Track task status and progress
96
97This skill simply detects the intent, extracts arguments, and routes to the appropriate PM command with write-gating enforcement.
majiayu000