create-request

name	Create Request
description	Create a V3 Request from a user message that the orchestrator has determined to be actionable work.
version	1.0.0
category	task-management
skillType	claude-skill
assignableRoles	["orchestrator","team-leader","developer","qa","tpm","designer","frontend-developer","backend-developer","fullstack-dev","qa-engineer","product-manager","architect","generalist"]
triggers	["create request","log request","new request","track request"]
tags	["v3","request","tracking"]
execution	{"type":"script","script":{"file":"execute.sh","interpreter":"bash","timeoutMs":15000}}

Create Request

Create a V3 Request entity to track actionable user work. This skill is called by the orchestrator (or any agent with semantic understanding) after determining that a user message represents real, actionable work.

WHEN to use this skill

Only call this skill when you determine a user message represents actionable work. Use your judgment as an LLM to classify intent.

DO create a Request for:

• "Build a login page with OAuth2" (code_change, L2)
• "Fix the broken test in auth.service.test.ts" (debugging, L1)
• "Deploy the staging environment" (deployment, L1)
• "Create a QA team with 3 members" (team_management, L2)
• "What endpoints does the auth service expose?" (query, L1)
• "Plan the migration to PostgreSQL" (planning, L2)

DO NOT create a Request for:

• "Hello" / "Hi team" (greeting)
• "Thanks!" / "Got it" / "OK" (acknowledgment)
• "How are you?" (small talk)
• "." / "k" / "yes" (filler)
• "Sounds good, let's proceed" (confirmation of prior work -- no new work)

Intent Levels

Use these to classify the complexity of the request:

Level	Meaning	Example
L0	Not actionable -- should NOT call this skill	"Thanks!", "Hello"
L1	Simple, single-step task	"Fix the typo in README.md"
L2	Multi-step, needs coordination or decomposition	"Build a new auth system with OAuth2 and tests"
L3	Large project, should trigger Mission creation	"Rewrite the entire backend in Go with full test coverage"

Intent Categories

Category	When to use
communication	Sending messages, notifications, status updates
query	Questions, lookups, information retrieval
code_change	Writing, modifying, or refactoring code
planning	Architecture decisions, roadmap work, design
debugging	Bug fixes, investigation, troubleshooting
deployment	Deploy, release, environment management