Order Command

Takes a spec directory (e.g., docs/specs/pdf-export) or epic name via $ARGUMENTS and creates an Epic Issue on GitHub.

This is the PM's second step: pass the order to the engineering team.

Workflow

Step 1: Read the Spec

1. Read overview.md and scope.md under docs/specs/<epic>/
2. If spec not found, suggest running /kitchen:menu first

Step 2: Create Epic Issue

Compose the issue body:

• Summarize the spec (do not duplicate full content)
• Link to the spec files as the source of truth

Follow registry/git/templates/issue/epic.md template:

## 概要

<!-- 1-2 sentence summary from overview.md -->

## 背景・目的

<!-- Short summary of Why + hypothesis from overview.md -->

## スペック

> [overview.md](docs/specs/<epic>/overview.md) | [scope.md](docs/specs/<epic>/scope.md)

## 完了条件

- [ ] <!-- Key acceptance gates from scope.md -->

## 参考情報・補足

- Spec directory: `docs/specs/<epic>/`
- Success criteria: <!-- 1-line summary from scope.md KPI -->
- Out of scope: <!-- 1-line summary from scope.md -->

Publish:

gh issue create \
  --title "<epic title>" \
  --label "epic" \
  --body-file -

Open in browser:

gh issue view --web

Step 3: User Confirmation

Present the created issue. Handle modifications if needed.

Rules

• Always respond in the user's language

Title Rules

• Written in Japanese (following git plugin convention)
• 72 characters or fewer
• No prefixes like [WIP], [BUG], [FEATURE]
• Convey the overall initiative clearly

What This Command Does NOT Do

• Does not create child task issues (engineer does this via chef -> prep)
• Does not decompose requirements into technical tasks
• Does not prescribe implementation approach

Next Step

After order, the engineer runs /kitchen:recipe #<issue-number> to start implementation.