claude-context: Skill for Claude Code

Issue Management

All issue operations route through Plane MCP. Read the project config first.

Step 0 — Read project config

Use the Read tool on .claude/project.json (relative to the repo root).

Extract:

• name — display name
• issuePrefix — e.g. HOME, DEVS, STRK
• plane.workspace — e.g. "lbruton"
• plane.projectId — uuid (used below as {plane_project_id})

If there is no plane block, stop and tell the user the project isn't wired to Plane.

---

Operations

Create

1. Resolve state and label IDs once per session:

   mcp__plane__state   action: "list", project_id: {plane_project_id}
   mcp__plane__label   action: "list", project_id: {plane_project_id}
   

   Map names → uuids. Cache for the rest of the session.

2. Pick state and label from user intent:

   Intent	State	Label
   New backlog item	Backlog	based on type
   Ready to work	Todo	based on type
   Active work	In Progress	based on type

   Type → label map (matches conventional commits):

   Type	Label
   feature, feat	Feature
   bug, fix	Bug
   chore	Chore
   docs, documentation	Documentation
   patch, hotfix	Patch

3. Create the issue:

   mcp__plane__workitem
     action: "create"
     project_id: {plane_project_id}
     name: "{title}"
     description_html: "{html-rendered description}"
     state: {state_uuid}
     labels: [{label_uuid}]
     priority: "urgent"|"high"|"medium"|"low"|"none"
   

   Fields are flat — there is no issue_data wrapper on the current server (DEVS-77).

   Plane assigns sequence_id automatically — capture from the response. The full issue ID is {issue_prefix}-{sequence_id} (e.g. SFLW-8).

4. Assign: follow "Assign after create" below. Do not pass assignees in step 3.

5. Confirm:

   Created {issue_prefix}-{sequence_id}: {title}
     URL: https://plane.lbruton.cc/lbruton/browse/{issue_prefix}-{sequence_id}/
     State: {state}
     Labels: {labels}
     Priority: {priority}