dagster: Command for Claude Code

/erk:objective-create-plan

Create an implementation plan for a specific step in an objective's roadmap.

Usage

/erk:objective-create-plan 3679
/erk:objective-create-plan https://github.com/owner/repo/issues/3679
/erk:objective-create-plan  # prompts for issue reference

---

Agent Instructions

Step 1: Parse Issue Reference

Parse $ARGUMENTS to extract the issue reference:

• If argument is a URL: extract issue number from path
• If argument is a number: use directly
• If no argument provided: try to get the default from pool.json (see below), then prompt if no default

Getting default objective from pool.json:

If no argument is provided, check if we're in a pool slot worktree with a last objective:

erk exec slot-objective

This returns JSON like:

{ "objective_issue": 123, "slot_name": "erk-slot-01" }

Or if not in a slot or no objective:

{ "objective_issue": null, "slot_name": null }

If objective_issue is not null, use it as the default and inform the user: "Using objective # from slot's last objective. Run with explicit argument to override."

If no default found or not in a pool slot, prompt user using AskUserQuestion with "What objective issue should I work from?"

Step 2: Fetch and Validate Issue

erk exec get-issue-body <issue-number>

This returns JSON with {success, issue_number, title, body, labels, url}.

Validate this is an objective:

1. Check for erk-objective label in the labels array
2. If label is erk-plan instead: report error "This is an erk-plan issue, not an objective. Use /erk:plan-implement instead."
3. If neither label: warn but proceed

Step 2.5: Create Objective Context Marker

Create a marker to persist the objective issue number for the exit-plan-mode hook.

erk exec marker create --session-id "${CLAUDE_SESSION_ID}" \
  --associated-objective <objective-number> objective-context

Replace <objective-number> with the issue number from Step 2.