/clientissue
Reads a client-facing GitLab issue, plans the solution, and creates a development issue.
Usage
/clientissue 123
Parameters
| Parameter | Required | Description |
|---|---|---|
| Issue IID | Yes | The client-facing issue ID (numeric, without #) |
What It Does
1. Fetch the Client Issue
Fetches the issue from the client-facing project (vinum/vinum) including all comments. Sets the client issue label to Stage::In Development.
2. Analyze and Plan
Analyzes the issue description and comments, then plans a technical solution in English.
3. Handle Insufficient Information
If there is not enough information to implement a solution:
- Drafts a non-technical follow-up question in German for the client
- Presents it for your review
- Posts the approved comment to the client issue
- Stops — no dev issue is created
4. Handle Sufficient Information
If there is enough information:
- Presents the planned solution for your confirmation
- Creates a development issue in the dev project with a cross-reference to the client issue (first line of description:
vinum/vinum#123) - Continues as /issue — creates a feature branch and implements the changes
What It Does NOT Do
- Does not commit or push — use /rollout for that
Prerequisites
glabmust be authenticated- Working tree must be clean
- The client issue must exist in the
vinum/vinumproject
Notes
- Client-facing comments are always in German, non-technical, and concise
- Development issues and internal communication are in English
- AI tools are never mentioned in GitLab comments or issues