PM Task Classification
Visibility
This is an internal analysis micro-skill.
Prefer invoking moonshot-orchestrator or moonshot-phase-runner, not this skill directly.
Inputs
analysisContext.request.userMessage
context.md (path: analysisContext.artifacts.contextDocPath, if exists)
Procedure
- Identify intent keywords from the user message.
- Select one taskType:
feature | modification | bugfix | refactor.
- Detect whether the request is still in product-definition mode.
- Set confidence:
high | medium | low.
Heuristics
- feature: "new", "add", "implement", "create", "build"
- modification: "change", "modify", "improve", "adjust", "remove"
- bugfix: "bug", "error", "broken", "fails"
- refactor: "refactor", "clean up", "restructure", "remove duplication"
Product Definition Detection
Set signals.productDefinitionRequest: true when the request is primarily about:
- idea shaping
- product intent
- PRD
- solution modeling
- architecture definition before implementation
- execution planning before code changes
Example keywords:
- "idea", "intent", "prd", "solution", "spec", "scope", "out of scope", "plan", "task slice"
Technology Stack Detection
React/Next.js 키워드 감지 시 시그널 설정:
- Keywords: "react", "next", "next.js", "nextjs", "jsx", "tsx", "useState", "useEffect"
- Output:
signals.reactProject: true
Output (patch)
request.taskType: feature
request.keywords:
- implement
- react
signals:
productDefinitionRequest: false
reactProject: true # Set when React/Next.js keywords detected
notes:
- "taskType=feature, confidence=high"
- "product-definition-request=false"
- "tech-stack: react/next.js detected" # Add when reactProject=true
1---2name: moonshot-classify-task3description: Classifies a user request into task types (feature, modification, bugfix, refactor) and extracts intent keywords. Use at the start of PM analysis.4surfaceStatus: internal_stage_owner5---67# PM Task Classification89## Visibility1011This is an internal analysis micro-skill.12Prefer invoking `moonshot-orchestrator` or `moonshot-phase-runner`, not this skill directly.1314## Inputs15- `analysisContext.request.userMessage`16- `context.md` (path: `analysisContext.artifacts.contextDocPath`, if exists)1718## Procedure191. Identify intent keywords from the user message.202. Select one taskType: `feature | modification | bugfix | refactor`.213. Detect whether the request is still in product-definition mode.224. Set confidence: `high | medium | low`.2324## Heuristics25- feature: "new", "add", "implement", "create", "build"26- modification: "change", "modify", "improve", "adjust", "remove"27- bugfix: "bug", "error", "broken", "fails"28- refactor: "refactor", "clean up", "restructure", "remove duplication"2930## Product Definition Detection3132Set `signals.productDefinitionRequest: true` when the request is primarily about:33- idea shaping34- product intent35- PRD36- solution modeling37- architecture definition before implementation38- execution planning before code changes3940Example keywords:41- "idea", "intent", "prd", "solution", "spec", "scope", "out of scope", "plan", "task slice"4243## Technology Stack Detection4445React/Next.js 키워드 감지 시 시그널 설정:46- Keywords: "react", "next", "next.js", "nextjs", "jsx", "tsx", "useState", "useEffect"47- Output: `signals.reactProject: true`4849## Output (patch)50```yaml51request.taskType: feature52request.keywords:53 - implement54 - react55signals:56 productDefinitionRequest: false57 reactProject: true # Set when React/Next.js keywords detected58notes:59 - "taskType=feature, confidence=high"60 - "product-definition-request=false"61 - "tech-stack: react/next.js detected" # Add when reactProject=true62```